CC eiirp
Everything In Its Right Place. The universal post-work organizer. After any significant work session, EIIRP runs a 7-phase audit: (1) inventory every output, (2) walk taxonomy to decide where each lands, (3) check schema-pack consistency against the brain's actual shape, (4) file enriched brain pages, (5) audit the skill graph for DRY+MECE, (6) verify resolvability, (7) report. Named after the Radiohead song. Nothing produced during significant work lives only in chat — knowledge becomes permanent, patterns become reusable. Also carries the always-on auto-fire gate: when >=500 words of structured analysis on a user-shared document is about to be delivered, file the brain page first, then deliver the analysis with the link in that same reply.
Everything In Its Right Place.
As a process C 57/100 · Has gaps — References files that are not bundled: ../conventions/brain-first.md, ../conventions/agent-operator-protocol.md, scripts/skill-dry-check.mjs
The same skill appears in 1 more place: gbrain
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: ../conventions/brain-first.md - warning
missing-refreference to a missing file: ../conventions/agent-operator-protocol.md - warning
missing-refreference to a missing file: scripts/skill-dry-check.mjs - note
frontmatter-keyunknown frontmatter key "prompt_version" - note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "mutating" - note
frontmatter-keyunknown frontmatter key "writes_pages" - note
frontmatter-keyunknown frontmatter key "writes_to" - note
frontmatter-keyunknown frontmatter key "filing_exempt" - note
frontmatter-keyunknown frontmatter key "upstream" - note
frontmatter-keyunknown frontmatter key "distinct_from"
Process rating: all ten parameters 57/100
- 0Tools and files. 3 referenced file(s) missing: ../conventions/brain-first.md, ../conventions/agent-operator-protocol.md, scripts/skill-dry-check.mjs
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 4709 tokens
- 100Steps. 92 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 15 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (5 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 751: enough signal without eating the budget
- +4Structure: 35 headings
- +3Step-by-step instructions: 92 items
- +3Output format is stated explicitly
- +4Has examples (12 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.