SKILLEMALL.ai

CD brain-ingest-gate

Pre-write quality gate for content entering the brain. No raw copies: a bare cp/mv into the brain repo is a bug. Before any new page lands, resolve named entities registry-first (a vector score is a floor for prose, never a gate for named things), then run the read-the-top-hit dedup decision tree (clear-dup / plausible-dup / clear). Owns dedup; delegates enrichment to the shipped ingestion skills. Routing convention, not an operation-boundary enforcement.

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

Pre-write quality gate for content entering the brain.

As a process D 46/100 · Unfinished process — References files that are not bundled: ../conventions/brain-first.md, ../_brain-filing-rules.md, ../conventions/test-before-bulk.md

GeneratorInfrastructureData and analyticsAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
60
Run on models
none yet
Process rating
D
46/100
Unfinished process
References files that are not bundled: ../conventions/brain-first.md, ../_brain-filing-rules.md, ../conventions/test-before-bulk.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

The same skill appears in 2 more places: gbrain, gbrain

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. 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 description-no-when description does not say WHEN to use the skill (no "use when")
  • 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/test-before-bulk.md
  • warning missing-ref reference to a missing file: ../ingest/SKILL.md
  • warning missing-ref reference to a missing file: ../signal-detector/SKILL.md
  • warning missing-ref reference to a missing file: ../enrich/SKILL.md
  • warning missing-ref reference to a missing file: ../concept-synthesis/SKILL.md
  • warning missing-ref reference to a missing file: ../conventions/quality.md
  • warning missing-ref reference to a missing file: ../conventions/agent-operator-protocol.md
  • warning missing-ref reference to a missing file: ../capture/SKILL.md
  • warning missing-ref reference to a missing file: ../bulk-ingestion/SKILL.md
  • warning missing-ref reference to a missing file: ../data-loss-gate/SKILL.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"
  • note frontmatter-key unknown frontmatter key "brain_first"

Process rating: all ten parameters 46/100

Will not run. References files that are not bundled: ../conventions/brain-first.md, ../_brain-filing-rules.md, ../conventions/test-before-bulk.md
  • 0Tools and files. 12 referenced file(s) missing: ../conventions/brain-first.md, ../_brain-filing-rules.md, ../conventions/test-before-bulk.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 48 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3569 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • low 12 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 459: enough signal without eating the budget
  • +4Structure: 17 headings
  • +3Step-by-step instructions: 48 items
  • +3Output format is stated explicitly
  • +4Has examples (5 code blocks)

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