BF agent-chronicle
AI-powered diary generation for agents - creates rich, reflective journal entries (400-600 words) with Quote Hall of Fame, Curiosity Backlog, Decision Archaeology, and Relationship Evolution. Generates personal, emotional entries from the agent's perspective. Powered by SkillBoss API Hub.
As a process F 49/100 · Will not run — References files that are not bundled: templates/custom.md
The same skill appears in 2 more places: ClawHub, ClawHub
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 18. 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
missing-refreference to a missing file: templates/custom.md
Process rating: all ten parameters 49/100
- 0Tools and files. 1 referenced file(s) missing: templates/custom.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (agent-chronicle) differs from the folder (marjorie-agent-chronicle)
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 4647 tokens
- 100Steps. 76 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 22 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)
- -219 emoji in the instructions: noise for the model
- -31 of 4 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 289: enough signal without eating the budget
- +4Structure: 81 headings
- +3Step-by-step instructions: 76 items
- +3Output format is stated explicitly
- +4Has examples (44 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.