advocate-sourcing

I've been digging through the skill grading results and noticed your advocate-sourcing skill landed at 62/100 — the scoring suggests some solid foundational thinking around sourcing strategies, but there's clearly room to tighten up the documentation and make the use cases more concrete for developers actually trying to implement this.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 62/100, which puts you in D territory. This is based on Anthropic's 5-pillar rubric for skill quality. Your strongest area is Spec Compliance (11/15) — the frontmatter is solid and naming is correct. The weak spot is Progressive Disclosure Architecture (16/30) — everything's crammed into one file with no reference structure to organize the complexity.

What's Working Well

• Valid frontmatter structure — Your YAML is clean and follows conventions properly
• Clear framework thinking — The 5-step workflow (Signal Collection → Scoring → Tiering → Backlog Management → Consent Tracking) is logically sound
• Hyphen-case naming — advocate-sourcing follows the right conventions

The Big One: Missing PDA Structure (High Priority)

Right now, you've got everything in a single SKILL.md file. The report notes you have zero reference files, which kills your PDA score (-6 points potential gain). Here's the fix:

Create a references/ directory with three files:

• references/scoring-model.md — Externalize that "weight value delivered, relationship strength" thinking with actual examples and formulas
• references/templates.md — Provide the advocate roster spreadsheet template you mention but don't actually show
• references/consent-tracking.md — Detail the compliance workflow separately

This alone gets you ...