AA understand-me
Use when the user asks the agent to understand, challenge, refine, interrogate, or co-design their ideas, thoughts, proposals, strategies, plans, designs, documents, or vague intuitions. Builds a design decision tree, examines every branch ruthlessly but constructively, asks one question at a time, provides a recommended answer for each question, searches provided materials before asking when the answer may already exist, and continues until shared understanding/consensus is reached.
Use when the user asks the agent to understand, challenge, refine, interrogate, or co-design their ideas, thoughts, proposals, strategies, plans, designs…
As a process A 83/100 · Runs to the end — weak spots: inputs and preconditions, progress reporting
How to improve
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 83/100
- 0Progress reporting. Says nothing while it works
- 30Inputs and preconditions. Does not say what the process needs to start
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 61 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1252 tokens
- 100Running it twice. No mutating operations
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)
- +1No license
- +2Single-language instructions
- +3Description length 488: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 61 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.