Why descriptions fail
Weak descriptions are usually too broad, too short, or missing the words a user would actually type. "Helps with docs" can match almost anything and nothing. A better description names the action, the artifact, and the trigger: "Drafts board-ready quarterly report PDFs from the finance template. Use when preparing board packets or updating quarterly reporting."
If the linter says the workflow belongs in a protocol integration instead of only a skill, run the Skill vs MCP Decider. If the description is ready, use it in the Skill Scaffold Generator.