AF skill-builder
Helps non-technical users create their own Skills through natural conversation. Triggers when users say "I want to create a Skill", "turn this workflow into a Skill", "I want you to remember how I work", "I want to customize your behavior", or "help me make a template". No technical knowledge required — fully guided through conversation, ending with a ready-to-use SKILL.md file.
As a process F 51/100 · Will not run — References files that are not bundled: references/quality_checklist.md, references/preview_test.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/quality_checklist.md - warning
missing-refreference to a missing file: references/preview_test.md
Process rating: all ten parameters 51/100
- 0Tools and files. 2 referenced file(s) missing: references/quality_checklist.md, references/preview_test.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (skill-builder) differs from the folder (skills-builder)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 6 branches
- 100Steps. 11 steps
- 100Execution cost. Instruction body is 1591 tokens
- 100Progress reporting. Reports progress
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
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 381: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 11 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.