Name: scenario-war-room
Rating: 64 (1 reviews)
Author: alirezarezvani

scenario-war-room

Cross-functional what-if modeling for cascading multi-variable scenarios. Unlike single-assumption stress testing, this models compound adversity across all business functions simultaneously. Use when facing complex risk scenarios, strategic decisions with major downside, or when the user asks 'what if X AND Y both happen?'

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/scenario-war-room/SKILL.md

The canonical home for this skill is scenario-war-room in alirezarezvani/claude-skills

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable planning skill with concrete worked examples and a clear 6-step workflow. Its main defects are missing bundle files (the referenced reference doc and CLI script do not exist) and the absence of an explicit validation checkpoint in the workflow.

Suggestions

Create the referenced `scripts/scenario_modeler.py` and `references/scenario-planning.md` (or remove the references) so the signaled navigation actually resolves.

Add an explicit validation/verification step to the 6-step workflow (e.g. 'Confirm every variable has a cascade path and at least one interrupt point before drafting the output').

Tighten or move 'Common Scenarios by Stage' and 'Integration with C-Suite Roles' into the reference file to reduce inline length and improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes Claude's competence (no padding about what scenarios or runways are), but sections like 'Common Scenarios by Stage', 'Integration with C-Suite Roles', and the duplicated 'Keywords' list could be trimmed — efficient with minor over-explanation.	4 / 5
Actionability	Concrete worked templates with real numbers ($560K ARR, runway 14→8 months), a filled cascade diagram, severity and hedge tables, and an output format — but the primary Quick Start command (`python scripts/scenario_modeler.py`) points to a script that does not exist, leaving a gap in executable guidance.	4 / 5
Workflow Clarity	A clearly sequenced 6-step cascade model with sub-structure per step and a closing 'Rules' checklist, but no explicit validation/feedback checkpoint (e.g. 'verify the cascade is complete before producing output'); the destructive/batch cap does not apply since this is a planning skill.	4 / 5
Progressive Disclosure	Good in-file section structure and a clearly signaled References section, but both referenced paths (`references/scenario-planning.md`, `scripts/scenario_modeler.py`) do not exist, so the one-level-deep navigation is broken rather than functional.	3 / 5
	Total	15 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-targeted description that clearly states both capability and trigger conditions, with an explicit differentiation from adjacent stress-testing skills. The main weakness is specificity — it names the domain and one action rather than enumerating several concrete actions.

Dimension	Reasoning	Score
Specificity	It names the domain ('cascading multi-variable scenarios', 'compound adversity across all business functions') and one concrete action ('what-if modeling'), but does not list multiple distinct concrete actions — closer to 'names domain and 1-2 concrete actions' than the multi-action anchors at 4-5.	3 / 5
Completeness	Explicitly answers both what ('Cross-functional what-if modeling... models compound adversity across all business functions') and when ('Use when facing complex risk scenarios... or when the user asks what if X AND Y both happen?') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes strong natural triggers like 'what if X AND Y both happen?', 'complex risk scenarios', and 'strategic decisions with major downside', but lacks several common synonyms (e.g. 'contingency planning', 'pre-mortem', 'stress test') that appear only in the body.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche ('Unlike single-assumption stress testing') with a distinctive multi-variable cascade trigger, minimizing overlap with generic stress-test or planning skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/scenario-war-room/SKILL.md
Commit: 19392f7

Reviewed: ~14 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.