SKILLEMALL.ai

CC resolve-before-asking

Gate on identity questions to the user. Before any "who is X?" (or role / relationship question) reaches the user, exhaust the brain's lookup chain: think → search + page read → mounted sources → timeline/graph → web. If escalation survives the chain, ask WITH a hypothesis, never a bare unknown. Also owns the no-placeholders-at-ingest rule: pages created during bulk ingestion get their relationship/role resolved immediately.

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

Gate on identity questions to the user.

As a process C 53/100 · Has gaps — References files that are not bundled: ../conventions/brain-first.md, ../_brain-filing-rules.md, ../ask-user/SKILL.md

GeneratorResearchtype and topics are labelled automatically from the skill text
JSON
Technical rating
C
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
55
Run on models
none yet
Process rating
C
53/100
Has gaps
References files that are not bundled: ../conventions/brain-first.md, ../_brain-filing-rules.md, ../ask-user/SKILL.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
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: resolve-before-asking (garrytan/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: ../ask-user/SKILL.md
  • warning missing-ref reference to a missing file: ../conventions/agent-operator-protocol.md
  • warning missing-ref reference to a missing file: ../query/SKILL.md
  • warning missing-ref reference to a missing file: ../brain-ops/SKILL.md
  • warning missing-ref reference to a missing file: ../enrich/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"

Process rating: all ten parameters 53/100

Will not run. References files that are not bundled: ../conventions/brain-first.md, ../_brain-filing-rules.md, ../ask-user/SKILL.md
  • 0Tools and files. 7 referenced file(s) missing: ../conventions/brain-first.md, ../_brain-filing-rules.md, ../ask-user/SKILL.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 55Failures and branches. 1 branches
  • 85Steps. 51 steps, 1 vague phrases
  • 100Result and completion. Output format and completion criterion are stated
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3171 tokens
  • 100Running it twice. Mutating operations check current state
  • low 12 top-level sections: this looks like several domains in one skill

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)
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +3Description length 428: enough signal without eating the budget
  • +4Structure: 21 headings
  • +3Step-by-step instructions: 51 items
  • +3Output format is stated explicitly
  • +4Has examples (5 code blocks)

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