SKILLEMALL.ai
RU Sign in

BF brain-map-visualizer

Visualize how attention moves across your agent's projects. 13 named attention categories. Momentum-ready edges (recentCount/lifetimeCount). Directional flow encoding. Sorted by co-access score.

ClawHub Agent Skills author: High Noon Office v3.3.6 MIT-0 5 files body ≈ 4 315 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process F 44/100 · Will not run — References files that are not bundled: scripts/build-brain-map-projects.js

ProcedureInfrastructureAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
Run on models
none yet
Process rating
F
44/100
Will not run
References files that are not bundled: scripts/build-brain-map-projects.js
Tools and files w 18
0
Result and completion w 14
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

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: 5. 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: scripts/build-brain-map-projects.js
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "source"

Process rating: all ten parameters 44/100

Will not run. References files that are not bundled: scripts/build-brain-map-projects.js
  • 0Tools and files. 1 referenced file(s) missing: scripts/build-brain-map-projects.js
  • 0Result and completion. Does not say what the result is
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 7 mutating operations with no state check
  • 55Failures and branches. 1 branches
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 4315 tokens
  • 85Steps. 21 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 194: enough signal without eating the budget
  • +4Structure: 17 headings
  • +3Step-by-step instructions: 21 items
  • +4Has examples (9 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)
  • +1License stated

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

External checks

ClawHub: suspicious
This is mostly a local journal-visualization skill, but it needs review because its parser can process and overwrite local journal-derived data during import and the API/auth/output instructions are inconsistent.
LLM: suspicious (high) · 25 Aug 2026