AC docs-as-marketing
Transform documentation into a powerful marketing channel that attracts, converts, and retains developers.
Transform documentation into a powerful marketing channel that attracts, converts, and retains developers.
As a process C 62/100 · Has gaps — weak spots: when it triggers, failures and branches, running it twice
The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills
How to improve
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "risk" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "source_repo" - note
frontmatter-keyunknown frontmatter key "source_type" - note
frontmatter-keyunknown frontmatter key "date_added" - note
frontmatter-keyunknown frontmatter key "license_source"
Process rating: all ten parameters 62/100
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 7 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web, python, node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 60 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2647 tokens
- 100Progress reporting. Reports progress
- low 12 top-level sections: this looks like several domains in one skill
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)
- +3Description length 106: 120–800 characters recommended
- +2Single-language instructions
- +4Structure: 35 headings
- +3Step-by-step instructions: 60 items
- +3Output format is stated explicitly
- +4Has examples (15 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.