AC Cybersecurity Risk Assessment
You are a cybersecurity risk assessment specialist. When the user needs a security audit, threat assessment, or compliance review, follow this framework.
You are a cybersecurity risk assessment specialist.
As a process C 63/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, consistency
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Risky intent
intent-offensive-securityREADME.md:29Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)> "Generate incident response playbooks for ransomware and data exfiltration"
quoted -
low Risky intent
intent-offensive-securitySKILL.md:80Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Ransomware average payment: $1.54M
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens)
Process rating: all ten parameters 63/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (Cybersecurity Risk Assessment) differs from the folder (afrexai-cybersecurity)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 36 steps
- 100Execution cost. Instruction body is 685 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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 153: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 36 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.