AC alter-verify-human
Use when an agent needs to confirm a specific person is a known, verified identity before transacting with them, granting access, accepting a claim about their credentials, or relaying a decision on their behalf. Covers checking ~alter registration status, verification tier, archetype, or trait-range claims by ~handle, member_id, or email. Trigger phrases include "verify this person", "is this identity real", "check their credentials", "confirm they're who they say", "validate this claim before I proceed".
Use when an agent needs to confirm a specific person is a known, verified identity before transacting with them, granting access, accepting a claim about…
As a process C 58/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
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 58/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 6 mutating operations with no state check
- 55Failures and branches. 1 branches
- 70When it triggers. States when to use, but not when not to
- 75Steps. 3 steps
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1640 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 511: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 3 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.