Works with the AI Agents you already use
risk scenario reviewer
Reviewing cybersecurity risk scenarios requires a rigorous, objective eye that many general-purpose prompts lack.
$10
risk scenario reviewer
Example session with this skill installed
Review this scenario: An attacker exploits a server vulnerability to steal customer data, causing $1M in damage. We have a firewall. Give me scores and corrections.
- Read your context and instructions
- Compiled the risk scenario reviewer
I have reviewed the provided scenario (SC1). Below is the analytical estimate of its quality.
Risk Scenario Review — unspecified, 2024-05-20
1. Scope, sources and assumptions
- Sources: One scenario provided via user prompt (SC1).
- Assumptions: The $1M damage figure is a user assertion with no stated basis.
2. Summary of scores
Scores are Analytical estimate — validation required.
| Scenario | C1 Causal chain | C2 Plausibility | C3 Specificity | C4 Measurability | C5 Treatment relevance | Verdict |
|---|---|---|---|---|---|---|
| SC1 | Partly met | Met | Not met | Not met | Not met | Rework |
3. Criterion scoring by scenario
SC1: Attacker exploits server vulnerability
| Criterion | Score | Evidence in the scenario | Reason |
|---|---|---|---|
| C1 Causal chain | Partly met | "exploits a server vulnerability to steal customer data" | Missing specific hazard type and enabling conditions. |
| C2 Plausibility | Met | "exploits a server vulnerability" | Mechanism is a standard technical threat. |
| C3 Specificity | Not met | "server", "customer data" | Fails swap test; reads the same for any organization. |
| C4 Measurability | Not met | "$1M in damage" | Basis, period, and unit of measure are not defined. |
| C5 Treatment relevance | Not met | "We have a firewall" | Firewall is a generic control; doesn't map to a specific link. |
4. Prioritised corrections
| Priority | Scenario | Criterion | Defect | Correction |
|---|---|---|---|---|
| P1 | SC1 | C4 | "$1M in damage" | Provide the basis (e.g., fines, recovery) and the scale used. |
| P1 | SC1 | C1 | "exploits a server vulnerability" | Name the specific vulnerability class and the asset at risk. |
| P2 | SC1 | C3 | "a server" | Identify the specific system, site, or role involved. |
| P2 | SC1 | C5 | "We have a firewall" | State if this is existing or proposed and which link it breaks. |
Management decision required
5. Portfolio observations
Single scenario reviewed.
6. Rewritten scenarios
Rewrite not requested.
7. Information gaps and next steps
- Gaps: Need specific system names, vulnerability types, and a breakdown of the $1M impact.
- Next steps: Update SC1 with the P1 corrections to allow for risk prioritization.
This review assesses how well scenarios are written; it does not assess whether they are true or how large the risk is.
Markers: [G] Gap, [A] User Assertion.
Connects securely to your tools. The creator never sees your data.
About this skill
Reviewing cybersecurity risk scenarios requires a rigorous, objective eye that many general-purpose prompts lack. This skill applies a formal five-criterion quality grid to ensure your scenarios are ready for analysis and prioritization without inventing external facts.
What it does
- Five-point scoring evaluates causal chain completeness, plausibility, specificity, measurability, and treatment relevance.
- Priority-based corrections identifies defects (P1 to P3) that block risk prioritization or weaken decision-making.
- Evidence-backed verdicts assigns a status of Ready, Rework, or Revise based on ordinal scoring rules.
- Structural rewrites cleans up wording and organization using provided facts while flagging information gaps with markers.
- Portfolio analysis detects overlaps, duplicate hazards, or generic "template-filled" wording across multiple scenarios.
How it works
- Intake provides one or more scenarios along with any optional organizational context or systems data.
- Analysis parses the text for hazards, vulnerabilities, assets, impacts, and existing controls.
- Evaluation rates each criterion as Met, Partly met, or Not met using strict decision rules.
- Correction generates a table of prioritized fixes and, if requested, a structural rewrite using a standard template.
Frameworks & tools
This skill is based on the information risk management and IPM process methodologies developed by Marc-André Léger. It utilizes a specialized ordinal scoring grid and standard risk scenario templates.
Why this beats prompting it yourself
Generic prompts often "hallucinate" missing details or fail to catch logical breaks in a causal chain. This skill enforces a disciplined evidence model that distinguishes between documented facts, user assertions, and analytical estimates while strictly refusing to invent new hazards.
Use cases
- QA a risk register before presenting findings to a board or CISO.
- Audit a batch of student or junior analyst scenarios for consistency and measurability.
- Tighten vague, generic risk statements into specific, organization-anchored stories.
- Identify overlapping risks in a large portfolio to streamline treatment plans.
Known limitations
Does not generate new scenarios, calculate risk scores (CVSS/residual risk), or provide legal/audit opinions. Scoring is an analytical estimate requiring validation.
Cannot create new scenarios or calculate numeric risk levels/indices. Limited to reviewing provided text. Requires validation of all analytical estimates.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 5 days ago
Permissions
No special permissions declared or detected