SKILLEMALL.ai
GitHub ↗ RU Sign in

CD correction-pipeline

When the user corrects a factual error, root-cause it immediately. Don't just note the correction — trace the error to its source, fix the source, and prevent recurrence. Every factual error is either a data error (bad brain page, bad memory file, bad rendered SOUL/USER identity, bad facts row) or a hallucination (LLM confabulated from partial signals).

garrytan/gbrain Agent Skills author: garrytan MIT 1 file body ≈ 3 190 tokens Open the sourcegithub.com↗ analyzed 6 d ago

When the user corrects a factual error, root-cause it immediately.

As a process D 47/100 · Unfinished process — References files that are not bundled: ../conventions/brain-first.md, ../_brain-filing-rules.md, ../conventions/agent-operator-protocol.md

ProcedureInfrastructureData and analyticsAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
D
47/100
Unfinished process
References files that are not bundled: ../conventions/brain-first.md, ../_brain-filing-rules.md, ../conventions/agent-operator-protocol.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: correction-pipeline (garrytan/gbrain)

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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-ref reference to a missing file: ../conventions/brain-first.md
  • warning missing-ref reference to a missing file: ../_brain-filing-rules.md
  • warning missing-ref reference to a missing file: ../conventions/agent-operator-protocol.md
  • note frontmatter-key unknown frontmatter key "triggers"
  • note frontmatter-key unknown frontmatter key "mutating"
  • note frontmatter-key unknown frontmatter key "writes_pages"
  • note frontmatter-key unknown frontmatter key "writes_to"
  • note frontmatter-key unknown frontmatter key "upstream"

Process rating: all ten parameters 47/100

Will not run. References files that are not bundled: ../conventions/brain-first.md, ../_brain-filing-rules.md, ../conventions/agent-operator-protocol.md
  • 0Tools and files. 3 referenced file(s) missing: ../conventions/brain-first.md, ../_brain-filing-rules.md, ../conventions/agent-operator-protocol.md
  • 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. 6 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 31 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3190 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 11 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (4 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 355: enough signal without eating the budget
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 31 items
  • +3Output format is stated explicitly
  • +4Has examples (11 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.