BD memory-recall
Recall facts from past sessions via memoir for questions or tasks that may depend on prior preferences, decisions, conventions, or knowledge. Use one fast summarize/get pass by default, exclude metrics unless requested, never call legacy `memoir recall`, and defer repo-structure onboarding questions to memoir-onboard.
Recall facts from past sessions via memoir for questions or tasks that may depend on prior preferences, decisions, conventions, or knowledge.
As a process D 45/100 · Unfinished process — References files that are not bundled: scripts/resolve-memoir-cli.sh
How to improve
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/resolve-memoir-cli.sh - note
edit-residuethe text marks something as outdated (lines 177): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 45/100
- 0Tools and files. 1 referenced file(s) missing: scripts/resolve-memoir-cli.sh
- 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. 4 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 65Failures and branches. 3 branches
- 85Steps. 27 steps, 2 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2905 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 tags): a typed call is more reliable
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)
- +1No license
- +2Single-language instructions
- +3Description length 319: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 27 items
- +3Output format is stated explicitly
- +4Has examples (12 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.