AB data-breach-impact-calculator
Calculate data breach costs, financial impact, regulatory fines, and remediation expenses. Use when estimating breach costs, GDPR/CCPA penalty exposure, incident financial impact, cyber insurance claims, breach notification costs, or board-level breach risk reporting.
As a process B 72/100 · Nearly there — weak spots: when it triggers, running it twice
ProcedureInfrastructureData and analyticstype and topics are labelled automatically from the skill text
How to improve
For the model run — optional
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 72/100
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 59 steps
- 100Failures and branches. 5 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1990 tokens
- 100Progress reporting. Reports progress
- 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)
- +1No license
- +2Single-language instructions
- +3Description length 268: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 59 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.
External checks
ClawHub: clean
This is a disclosed ToolWeb API-backed breach cost calculator, but users should avoid sending sensitive incident details unless they are comfortable with that vendor handling the data.
LLM: benign (high) · VirusTotal: · 29 May 2026