BF skill-creator
Guide for creating effective skills that extend agent capabilities with specialized knowledge, workflows, or tool integrations. Use this skill when the user asks to: (1) create a new skill, (2) make a skill, (3) build a skill, (4) set up a skill, (5) initialize a skill, (6) scaffold a skill, (7) update or modify an existing skill, (8) validate a skill, (9) learn about skill structure, (10) understand how skills work, or (11) get guidance on skill design patterns. Trigger on phrases like "create a skill", "new skill", "make a skill", "skill for X", "how do I create a skill", or "help me build a skill".
As a process F 39/100 · Will not run — References files that are not bundled: FORMS.md, REFERENCE.md, EXAMPLES.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Dangerous commands
cmd-autorun-instructionSKILL.md:274Instructs the agent to auto-run a script on every sessionWhen creating a new skill from scratch, always run the `init_skill.py` script. The script conveniently generates a new template skill directory that automatically includes everything a skill requires,
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: FORMS.md - warning
missing-refreference to a missing file: REFERENCE.md - warning
missing-refreference to a missing file: EXAMPLES.md - warning
missing-refreference to a missing file: DOCX-JS.md - warning
missing-refreference to a missing file: REDLINING.md - warning
missing-refreference to a missing file: OOXML.md - warning
missing-refreference to a missing file: scripts/rotate_pdf.py - warning
missing-refreference to a missing file: references/finance.md - warning
missing-refreference to a missing file: references/mnda.md - warning
missing-refreference to a missing file: references/policies.md - warning
missing-refreference to a missing file: references/api_docs.md - warning
missing-refreference to a missing file: assets/logo.png - warning
missing-refreference to a missing file: assets/slides.pptx - warning
missing-refreference to a missing file: assets/frontend-template/ - warning
missing-refreference to a missing file: assets/font.ttf - warning
missing-refreference to a missing file: assets/hello-world/ - warning
missing-refreference to a missing file: references/schema.md
Process rating: all ten parameters 39/100
- 0Tools and files. 17 referenced file(s) missing: FORMS.md, REFERENCE.md, EXAMPLES.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (skill-creator) differs from the folder (skills-ttt)
- 60Steps. 68 steps, 4 vague phrases
- 65Failures and branches. 3 branches
- 70Execution cost. Instruction body is 4345 tokens
- 100When it triggers. States when to use and when not to
- 100Running it twice. Mutating operations check current state
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)
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 608: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 68 items
- +4Has examples (9 code blocks)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.