on-page

I checked out the on-page skill and noticed your approach to progressive disclosure feels solid, but I'm curious why you opted for the current information architecture instead of a hierarchical expand/collapse pattern—seems like there might be some token efficiency gains on the table there.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 76/100, solid C-grade territory. This is based on Anthropic's skill best practices framework. Your Spec Compliance (12/15) is the strongest pillar—the YAML frontmatter is clean and the naming conventions are tight. But Utility (14/20) and PDA (22/30) are dragging the score down because you're describing templates instead of providing them, and there's no real validation loop to help users confirm their work.

What's Working Well

• Clean metadata structure – Your frontmatter is valid YAML with all required fields, and the hyphen-case naming follows conventions perfectly
• Clear actionable framework – The 8-step progression from Meta Data through Internal Linking gives users a logical roadmap without getting lost in the weeds
• Good technical focus – Zero marketing language here; you're staying purely instructional, which keeps things grounded and credible
• Trigger terms help discoverability – "Crafting or refreshing pages" combined with "conversion goals" and "target keywords" gives search/discovery a decent chance of surfacing this

The Big One: Missing Template Files

This is the heavyweight issue holding you back. You mention three templates—optimization diff table, CTA matrix, and internal link planner—but they're just described, not provided. Users hit step 4 and think, "Okay, but what does this actually look like?"

Here's the fix: Create three reference files: -...