Feedback on your -claude__skills__route-tester skill

Hey! Took a look at your route-tester skill — here's the rundown.

Score: 57/100

View on SkillzWave

The Honest Truth

You're at 57, which puts you in the tons of room for improvement. But don't sweat it too much; this is fixable, and the core idea here is actually useful. You've got real, practical testing patterns that developers actually need. The problem is more about structure and presentation than substance.

What's Actually Good Here

• Real-world utility — cookie-based JWT auth testing is a genuine pain point, and you address it
• Those bash examples are solid — concrete, copy-pasteable commands that actually work
• The debugging section is helpful — 401/403/404/500 breakdown with actual solutions is chef's kiss
• Service ports table — exactly the kind of quick-reference stuff people need

The Big Problems

1. "your project" everywhere

This is the elephant in the room. You've got "your project" as placeholder text throughout the skill, which makes it confusing. Is this a template? A real skill? Claude's going to be confused too.

Fix: Either make it generic (remove project-specific stuff) OR commit to the actual project name. Pick a lane.

2. Everything's in one giant file

You've got 300+ lines covering authentication overview, three testing methods, common patterns, debugging, database verification, config files... that's a lot. This is screaming for a references/ folder.

Suggested split:

• SKILL.md — quick start + method overview (~100 lines)
• references/debugging.md — all the 401/403/404/500 stuff
• references/patterns.md — common testing patterns
• references/config.md — config files and ports

3. No navigation

At 300+ lines with no TOC, people are just scrolling and hoping. Add a table of contents right after your intro. To really enable PDA and let the coding agent find, things you need to add the TOC so it can do its agentic search.

4. The description could be stronger

Your current description mentions "your project" which doesn't help Claude figure out when to use this. Try something like:

description: Test authenticated API routes using cookie-based JWT authentication. Use when testing endpoints, debugging auth issues (401/403 errors), or validating route functionality with test-auth-route.js or mock authentication.

Quick Wins

1. Fix the placeholder text — decide if this is generic or project-specific
2. Add a TOC — takes 5 minutes, huge usability improvement
3. Extract that debugging section — it's valuable but makes the main file too long
4. Punch up the description — add trigger words like "401", "403", "JWT", "cookie", "curl"

Do those four things and you're probably looking at a 70+ score.

Check out your skill: SkillzWave.ai | SpillWave Route Tester Agentic Skill

We have an agentic skill installer that installs skills across 14+ coding agent platforms. And if you want to go deeper on improving this, check out this guide on mastering agentic skills.