CC Development
Builds, tests, modifies and checks up on software against its ISA, from a one-file change to a giant system. Build turns intent into ISA criteria and makes them pass; Test proves the ISA is well formed, matches the code, and every criterion's Assay eval passes; Modify changes criteria first, then code; Checkup joins the ISA with production, Vigil, Errata and Achilles, says why each red criterion is red, and repairs the ISA. Each run is sized to the ask: small work inline, wide work a workflow. USE WHEN build an app, site, game, tool, CLI or pipeline, start a new project, implement or change a feature, fix a bug in an app, test the app, is the code in sync with the ISA, run the app evals, catch up an old repo into an ISA, health check, checkup, why are these ISCs red, audit the ISA, sync the ISA with production. NOT FOR editing an ISA's articulation alone (ISA), eval or judge design (Assay), new skills (CreateSkill), workflow definitions (Workflows), slides, images, Visualize, deploying (the project deploy command).
Builds, tests, modifies and checks up on software against its ISA, from a one-file change to a giant system.
As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- Shorten the description to 1024 characters.
- 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: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1030 chars, limit 1024 - warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 5, column 14: description: Builds, tests, modifies and checks up on software against its ISA,… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - note
edit-residuethe text marks something as outdated (lines 106): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 55/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 24 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
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 31 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3371 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (9 tags): a typed call is more reliable
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
- +3Description length 1030: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 11 headings
- +3Step-by-step instructions: 31 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 49.