SKILLEMALL.ai

CD soul-audit

Re-run or deepen the agent's identity interview. Drives the SHARED bootstrap answer bank (state/interview.json) via `gbrain bootstrap interview --set/--show/--confirm`, then re-renders the identity files with `gbrain bootstrap render --only <FILE> --force`. One answer store, two surfaces: first-boot bootstrap and this re-run skill write the same bank, so an updated answer flows into SOUL.md, USER.md, ACCESS_POLICY.md, and HEARTBEAT.md without hand-editing rendered files. Every answer is the user's own words — never invented.

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

Re-run or deepen the agent's identity interview.

As a process D 41/100 · Unfinished process — References files that are not bundled: ../conventions/agent-operator-protocol.md

AnalyzerAI and agentsWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
66
Run on models
none yet
Process rating
D
41/100
Unfinished process
References files that are not bundled: ../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: soul-audit (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/agent-operator-protocol.md
  • note frontmatter-key unknown frontmatter key "triggers"
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "mutating"

Process rating: all ten parameters 41/100

Will not run. References files that are not bundled: ../conventions/agent-operator-protocol.md
  • 0Tools and files. 1 referenced file(s) missing: ../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
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 16 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1364 tokens

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 530: enough signal without eating the budget
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 16 items
  • +3Output format is stated explicitly
  • +4Has examples (1 code blocks)

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