CD writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when creating new skills, editing existing skills, or verifying skills work before deployment
As a process D 40/100 · Unfinished process — References files that are not bundled: ../using-superpowers/references/codex-tools.md, ../using-superpowers/references/gemini-tools.md, scripts/tool.sh
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: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../using-superpowers/references/codex-tools.md - warning
missing-refreference to a missing file: ../using-superpowers/references/gemini-tools.md - warning
missing-refreference to a missing file: scripts/tool.sh
Process rating: all ten parameters 40/100
- 0Tools and files. 3 referenced file(s) missing: ../using-superpowers/references/codex-tools.md, ../using-superpowers/references/gemini-tools.md, scripts/tool.sh
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 22 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 70Execution cost. Instruction body is 4140 tokens
- 100Steps. 93 steps
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 20 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 97: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +4Structure: 39 headings
- +3Step-by-step instructions: 93 items
- +4Has examples (6 code blocks)
- +4Reference files are cited in the instructions (5 of 7)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.
In the sandbox The scripts kept to themselves
The skill's scripts were run in a throwaway machine: no network, fake keys in the home directory, a tracer watching. We wrote down what they did. Reaching for the network or for secrets caps the technical grade at C; a quiet run adds no points.
Запущено 1 скрипт; каждому дали двадцать секунд, поддельный домашний каталог с ключами и сеть, в которой ничего нет.
render-graphs.js | ничего за пределами своей папки |
20 Sept 2026