SKILLEMALL.ai

BC neural-memory-enhanced-2

扩散激活的联想记忆,持久智能回忆,主动使用。Zero LLM dependency** — Pure algorithmic: regex, graph traversal, Hebbian learning。Spreading activation** — Associative recall through neural graph, not keyword/vector search。20 synapse types** — Temporal (BEFORE/AFTER), causal (CAUSED_BY/LEADS_TO), semantic

ClawHub Agent Skills author: 天轰穿 v1.0.0 MIT-0 2 files body ≈ 1 783 tokens Open the sourceclawhub.ai analyzed 36 h ago

扩散激活的联想记忆,持久智能回忆,主动使用。Zero LLM dependency — Pure algorithmic: regex, graph traversal, Hebbian learning。Spreading activation — Associative recall through…

As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
65
Run on models
none yet
Process rating
C
61/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
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.
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: 2. 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")
  • note frontmatter-key unknown frontmatter key "slug"
  • note frontmatter-key unknown frontmatter key "displayName"
  • note frontmatter-key unknown frontmatter key "summary"
  • note frontmatter-key unknown frontmatter key "tools"

Process rating: all ten parameters 61/100

  • 0Result and completion. Does not say what the result is
  • 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
  • 30Running it twice. 2 mutating operations with no state check
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 36 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1783 tokens
  • low 13 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)
  • +3Output format is not stated: the model decides each time
  • -5TODO / placeholder text left in the skill
  • +2Single-language instructions
  • +3Description length 280: enough signal without eating the budget
  • +4Structure: 34 headings
  • +3Step-by-step instructions: 36 items
  • +4Has examples (7 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This memory skill is mostly coherent, but it asks agents to automatically retain conversation-derived information without clear user consent or sensitivity limits.
LLM: suspicious (high) · 14 Aug 2026