delegation-prompt-crafter

I've been reading through how you structured the prompt delegation flow—the way you layer context and scaffolding to guide users through complex decisions is genuinely clever. At 99/100, that one missing point is probably telling you something worth fixing.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 99/100, solid A grade. This is based on Anthropic's skill best practices. Your strongest areas are Writing Style (10/10—no fluff, pure instruction) and Progressive Disclosure Architecture (28/30—excellent file layering). The weakness is Spec Compliance (11/15)—mostly because your frontmatter description lacks trigger phrases, which actually costs you discoverability.

What's Working Well

• Copy-paste checklists are gold. The validation checklist at lines 251–263 gives users actual gates to pass before delegating. That's the kind of thing people bookmark.
• Three specialist templates (Architecture, Mentor, ML-Architect) show real flexibility without bloat. Each one is complete but brief enough to customize.
• The CONTEXT/TASK/REQUIREMENTS structure is clean. You're teaching a mental model, not just listing steps. That's why the Writing Style score is maxed out.
• File organization hits the mark—270 lines in the main SKILL.md, templates tucked into /references/. Token-efficient without hiding anything.

The Big One: Frontmatter Description Needs Trigger Phrases

Your description currently reads: "Transform clarified user requests into structured delegation prompts optimized for specialist agents..."

This doesn't have trigger phrases. According to the spec, it should look like:

description: Performs delegation prompt crafter operations. Use when asked to "delegati...