CC skill-authoring-workflow
Turn raw PM content into a compliant, publish-ready skill. Use when creating or updating a repo skill without breaking standards.
Turn raw PM content into a compliant, publish-ready skill.
As a process C 56/100 · Has gaps — References files that are not bundled: ../workshop-facilitation/SKILL.md, scripts/find-a-skill.sh, scripts/add-a-skill.sh
ProcedureSoftware developmentAI and agentsWriting and documentstype and topics are labelled automatically from the skill text
How to improve
- The text references files that are not there: add them or drop the references.
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../workshop-facilitation/SKILL.md - warning
missing-refreference to a missing file: scripts/find-a-skill.sh - warning
missing-refreference to a missing file: scripts/add-a-skill.sh - warning
missing-refreference to a missing file: scripts/build-a-skill.sh - warning
missing-refreference to a missing file: scripts/test-a-skill.sh - warning
missing-refreference to a missing file: scripts/check-skill-metadata.py - warning
missing-refreference to a missing file: scripts/check-skill-triggers.py - warning
missing-refreference to a missing file: scripts/zip-a-skill.sh - note
frontmatter-keyunknown frontmatter key "intent" - note
frontmatter-keyunknown frontmatter key "type" - note
frontmatter-keyunknown frontmatter key "best_for" - note
frontmatter-keyunknown frontmatter key "scenarios" - note
frontmatter-keyunknown frontmatter key "theme" - note
frontmatter-keyunknown frontmatter key "estimated_time"
Process rating: all ten parameters 56/100
Will not run. References files that are not bundled: ../workshop-facilitation/SKILL.md, scripts/find-a-skill.sh, scripts/add-a-skill.sh
- 0Tools and files. 8 referenced file(s) missing: ../workshop-facilitation/SKILL.md, scripts/find-a-skill.sh, scripts/add-a-skill.sh
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 64 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1736 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 129: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 64 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.