CC brain-link-discipline
When you report a brain page to the user — created, edited, committed, or relayed from a subagent — a working link is part of the deliverable, in the SAME message. Derive the path mechanically (git ls-files --full-name), push BEFORE linking, verify the link resolves when a hosted remote exists, and degrade through a defined fallback chain when it doesn't. Inside brain pages the rule inverts: relative links preserve the link graph; absolute URLs are for chat deliverables only.
When you report a brain page to the user — created, edited, committed, or relayed from a subagent — a working link is part of the deliverable, in the SAME…
As a process C 54/100 · Has gaps — References files that are not bundled: ../_output-rules.md, ../conventions/brain-first.md, ../people/alice-example.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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../_output-rules.md - warning
missing-refreference to a missing file: ../conventions/brain-first.md - warning
missing-refreference to a missing file: ../people/alice-example.md - warning
missing-refreference to a missing file: ../conventions/agent-operator-protocol.md - note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "mutating" - note
frontmatter-keyunknown frontmatter key "writes_pages" - note
frontmatter-keyunknown frontmatter key "upstream" - note
frontmatter-keyunknown frontmatter key "brain_first"
Process rating: all ten parameters 54/100
- 0Tools and files. 4 referenced file(s) missing: ../_output-rules.md, ../conventions/brain-first.md, ../people/alice-example.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 52 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 40 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2969 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 14 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (13 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
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 480: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 40 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.