technical-seo

I took a look at your technical-seo skill and wanted to share some thoughts.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 60/100, D grade territory — this is based on Anthropic's skill best practices. The good news: your spec compliance is solid (12/15). The tough news: Progressive Disclosure Architecture and Utility are dragging you down hard (12/30 and 10/20 respectively). You've got the foundation right, but the skill needs more depth and structure to really shine.

What's Working Well

• Spec compliance is tight — Your frontmatter is valid YAML with all required fields, name convention is correct hyphen-case. That's the baseline done right.
• Readable structure — The skill has decent navigation signals with clear headers and what looks like a logical TOC, which helps discoverability.
• Concise writing — Your content isn't bloated. You're saying what needs to be said without fluff (that's worth points in the Writing Style category).

The Big One: Reference Files Are Missing

Here's what's holding you back: you have zero reference files supporting your main SKILL.md. The grading report shows "0 reference files with 0 words" — that's a killer for Progressive Disclosure Architecture (which you need for the full 30 points).

Why this matters: A skill with only one 387-word SKILL.md file can't progressively disclose its complexity. Users get dumped the whole thing at once instead of layered discovery. This is a token efficiency problem AND a usability problem.

The fix: Create reference files. Think:

• guides/getting-started.md — onboarding steps
• examples/common-audits.md — real-world use cases
• reference/tools-explained.md — detailed tool explanations
• templates/audit-checklist.md — templates users can reuse

Even 2-3 well-structured reference files would bump your PDA score from 12 to 20+. That alone gets you to 68-70.

Other Things Worth Fixing

1. Flesh out your description triggers — You're only at 3/4 on description quality. Add 2-3 more trigger phrases beyond what you have. Think: "SEO audit", "search ranking", "crawl errors". This improves discoverability and helps the right people find your skill.

2. Add examples and templates — You scored 1/3 here. Include at least one code block or template showing how to use this skill in context. A simple JSON schema of expected output or a before/after example would get you the remaining points.

3. Strengthen feedback loops — You're at 1/4. Add validation sections that help users know if they're using the skill correctly. Something like "If you see X output, it means Y" or "Common mistakes to avoid".

Quick Wins

• Create 2-3 reference files (biggest bang for your buck — +8-10 points PDA)
• Add 2 more trigger phrases to your description (+1 point, easy win)
• Include 1-2 templates or examples (+2 points Utility)
• Add a "How to Know It Worked" section for feedback loops (+2-3 points)

These moves get you from 60 to 72-75, solidly into C territory. The reference files are the key unlock.

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.