AC private-assistant
Personal bookkeeping, memo/journal, reminder, and spending-insight assistant for Hermes. Use when the user wants to record income or expenses, save notes or reflections, query summaries, review spending patterns, correlate spending with memos, or manage explicit reminders backed by local JSONL files and cron.
As a process C 55/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, running it twice
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 310 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
Process rating: all ten parameters 55/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 60Consistency. The Hermes dialect needs category and tags
- 70When it triggers. States when to use, but not when not to
- 100Steps. 70 steps
- 100Execution cost. Instruction body is 1533 tokens
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)
- +2Single-language instructions
- +3Description length 310: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 70 items
- +3Output format is stated explicitly
- +4Has examples (17 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +3All 3 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.