BF memory-management
Use when the user asks to "remember project context", review saved findings, initialize runtime memory, archive stale work, reconcile notes, or erase a subject; manages authorized HOT/WARM/COLD working memory across all disciplines while preserving registry event ownership and privacy controls. Not for changing canonical registry facts - route those through the owning registry. 项目记忆/跨会话
As a process F 47/100 · Will not run — References files that are not bundled: ../../references/state-model.md, ../../references/skill-contract.md, ../../references/runtime-invocation.md
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The text references files that are not there: add them or drop the references.
- 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: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 389 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
missing-refreference to a missing file: ../../references/state-model.md - warning
missing-refreference to a missing file: ../../references/skill-contract.md - warning
missing-refreference to a missing file: ../../references/runtime-invocation.md - warning
missing-refreference to a missing file: ../../references/registry-event-protocol.md - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 47/100
- 0Tools and files. 4 referenced file(s) missing: ../../references/state-model.md, ../../references/skill-contract.md, ../../references/runtime-invocation.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 14 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 60Consistency. The Hermes dialect needs category and tags
- 100Steps. 46 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 2629 tokens
- 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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 389: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 46 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (4 of 7)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.