AD agent-bom-analyze
Analyze blast radius, attack paths, and threat landscape across your AI infrastructure. Use when: "blast radius", "threat intel", "risk score", "attack path", "lateral movement", "context graph", "who can reach what".
Analyze blast radius, attack paths, and threat landscape across your AI infrastructure.
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Risky intent
intent-offensive-securitySKILL.md:6Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)"attack path", "lateral movement", "context graph", "who can reach what".
quoted -
low Risky intent
intent-offensive-securitySKILL.md:60Offensive-security / dual-use content (legitimate for authorised testing; review intended use)infrastructure. Maps lateral movement risks, identifies high-impact CVEs, and
-
low Risky intent
intent-offensive-securitySKILL.md:77Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)- "lateral movement"
quoted -
low Risky intent
intent-offensive-securitySKILL.md:96Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| `context_graph` | Agent context graph with lateral movement analysis |
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 49/100
- 0Result and completion. Does not say what the result is
- 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
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (agent-bom-analyze) differs from the folder (analyze)
- 100Tools and files. No external tools needed
- 100Steps. 11 steps
- 100Execution cost. Instruction body is 518 tokens
- 100Running it twice. No mutating operations
- 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
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 217: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 11 items
- +4Has examples (4 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.