BA emotion-journal
Help users record emotions, identify triggers, notice patterns, and build a gentle self-observation habit
As a process A 80/100 · Runs to the end — weak spots: inputs and preconditions
GeneratorPersonal productivityInfrastructuretype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 80/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 60Result and completion. Output format stated, no completion criterion
- 65Failures and branches. 3 branches
- 100Tools and files. No external tools needed
- 100Steps. 73 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1390 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- 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
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)
- +3Description length 105: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 20 headings
- +3Step-by-step instructions: 73 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.
External checks
ClawHub: clean
The artifact appears to be a ClawHub staff/developer skill set with powerful but disclosed admin, migration, review, and documentation workflows guarded by user confirmation and existing auth.
LLM: benign (medium) · VirusTotal: · 20 Jun 2026