BD engram
Sistema de memoria persistente para agentes IA. Usa mem_save después de bugfixes, decisiones, descubrimientos, cambios de config. Usa mem_search cuando el usuario menciona "remember"/"recordar" o al empezar trabajo que se solapa con sesiones previas. Usa mem_session_summary antes de terminar sesiones para preservar contexto.
As a process D 42/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Dangerous commands
cmd-privilegeSKILL.md:125Privilege escalation / world-writable permissions (quoted — discussed, not commanded)3. **macOS/Linux**: `chmod +x engram && sudo mv engram /usr/local/bin/`
quoted
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 6311 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 42/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. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (engram) differs from the folder (engramclaw)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 70Execution cost. Instruction body is 6311 tokens
- 100Steps. 50 steps
- low 19 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
- +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
- -226 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 326: enough signal without eating the budget
- +4Structure: 67 headings
- +3Step-by-step instructions: 50 items
- +4Has examples (47 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.