SKILLEMALL.ai

BC elite-longterm-memory

融合六种成熟方法的AI代理记忆架构:会话状态热内存、向量数据库 温存储、Git笔记冷存储、策展归档、云端备份与自动事实提取。通过 WAL协议保证持久性,覆盖记忆卫生、故障诊断与即时修复。适用于 独立开发者、企业团队和自动化工作流场景.

ClawHub Agent Skills author: 天轰穿 v1.0.2 MIT-0 2 files body ≈ 1 797 tokens Open the sourceclawhub.ai analyzed 3 d ago

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

ReferenceSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
67
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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"
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "suggested_price"
  • note frontmatter-key unknown frontmatter key "pricing_tier"
  • note frontmatter-key unknown frontmatter key "pricing_model"

Process rating: all ten parameters 51/100

  • 0Result and completion. Does not say what the result is
  • 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
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 51 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1797 tokens
  • low 11 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)
  • +3Description length 117: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Structure: 35 headings
  • +3Step-by-step instructions: 51 items
  • +4Has examples (5 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This memory skill is coherent for its stated purpose, but it asks agents to persist user context automatically across multiple stores and optional cloud sync without clear consent, retention, or deletion controls.
LLM: suspicious (high) · 24 Jul 2026