BF remember-me
Remember-this trigger: memory updates + recall for preferences, goals, boundaries, prior work, decisions, dates, and todos. Use whenever user asks to remember, continue previous context, personalize behavior, or retrieve what was decided earlier.
As a process F 47/100 · Will not run — References files that are not bundled: references/promotion-checklist.md, references/profile-schema.md
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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Remember-this trigger: memory updates + recall for preferences, go… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
missing-refreference to a missing file: references/promotion-checklist.md - warning
missing-refreference to a missing file: references/profile-schema.md
Process rating: all ten parameters 47/100
- 0Tools and files. 2 referenced file(s) missing: references/promotion-checklist.md, references/profile-schema.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 4 mutating operations with no state check
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 100Steps. 79 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1225 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 17 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 246: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 79 items
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.