AA skill-autogenesis
Review completed work, summarize reusable procedures, identify recurring workflow patterns, and decide whether to create a skill, patch an existing skill, store a memory note, or do nothing. Built for agents that need structured procedural memory in Hermes, OpenClaw, or similar tool-using environments without confusing abstract rules with reusable procedures.
As a process A 84/100 · Runs to the end — weak spots: progress reporting
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: 16. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 361 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
Process rating: all ten parameters 84/100
- 0Progress reporting. Says nothing while it works
- 60Result and completion. Output format stated, no completion criterion
- 60Consistency. The Hermes dialect needs category and tags
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4278 tokens
- 100Tools and files. No external tools needed
- 100Steps. 187 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 22 branches, has a failure section
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 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)
- +4No input/output examples
- +2Single-language instructions
- +3Description length 361: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 187 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (1 of 3)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.