BB risk-assessment
Framework-directable information security risk assessment. Identifies threats, evaluates likelihood/impact via a 3x3 matrix, maps findings to any compliance framework, and recommends risk treatment options with prioritization guidance.
As a process B 72/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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-securitySKILL.md:140Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)"rationale": "Likelihood is High (3) because RDP without MFA is heavily targeted by ransomware operators and credential compromise is common. Impact is High (3) because the connection leads directly t
detector -
low Risky intent
intent-offensive-securitySKILL.md:171Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)"rationale": "Likelihood is Medium (2) because while patching does occur, the quarterly cycle creates a significant window of exposure. Perimeter controls provide some mitigation. Impact is Medium (2)
quoted
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "default_framework"
Process rating: all ten parameters 72/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 55Failures and branches. 1 branches
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 16 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3352 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)
- +2Single-language instructions
- +3Description length 235: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 16 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.
External checks
ClawHub: clean
This skill is a coherent risk-assessment prompt with a purpose-aligned API example, but users should avoid sending confidential assessment details to external AI providers unless approved.
LLM: benign (high) · VirusTotal: · 20 Jul 2026