AB identity-theft-recovery
Take back control after identity theft — the right first moves, in the right order, so you contain the damage and rebuild. Use when asked what to do about identity theft, someone stole my identity, my details are being used fraudulently, or help me recover from fraud. Produces an immediate-actions checklist (freeze, report, secure), an evidence and reporting plan for the right authorities and institutions, a dispute path for fraudulent accounts/charges, and an ongoing-monitoring setup — flagging where to use official channels and when to involve police/regulators.
Take back control after identity theft — the right first moves, in the right order, so you contain the damage and rebuild.
As a process B 69/100 · Nearly there — weak spots: when it triggers, failures and branches, 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: 1. 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 69/100
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 8 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 36 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1053 tokens
- 100Progress reporting. Reports progress
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 570: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 36 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.