CtrlK
BlogDocsLog inGet started
Tessl Logo

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?'

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

The body is a well-structured, actionable framework with worked examples and a clear 6-step sequence backed by real reference files. It is efficient but carries some redundancy across the Keywords, Common Scenarios, and Integration sections that could be consolidated.

Suggestions

Remove or trim the Keywords section — it duplicates triggers already in the description and adds token cost without new guidance.

Consolidate 'Common Scenarios by Stage' and 'Integration with C-Suite Roles' with the Step 2 domain table to eliminate overlapping tabular content.

Add a brief usage example or two for scenario_modeler.py beyond the single bare command so the CLI path is as actionable as the manual framework.

DimensionReasoningScore

Conciseness

Mostly lean — concrete tables and worked examples earn their place — but the Keywords section duplicates the description's triggers and the 'Common Scenarios by Stage' / 'Integration with C-Suite Roles' tables overlap the 6-step framework, giving minor trim opportunities.

4 / 5

Actionability

Provides concrete copy-paste templates (variable block, cascade map, trigger definitions, hedge table, output format) and a runnable command, with specific quantified examples; minor gap is that scenario_modeler.py usage is shown only as a single one-line command.

4 / 5

Workflow Clarity

The 6-Step Cascade Model is a clear numbered sequence with per-step structure and guardrails in 'Rules for Good War Room Sessions'; no explicit validate/retry checkpoints, but this is an analytical (non-destructive) skill so that cap does not apply.

4 / 5

Progressive Disclosure

Well-organized sections with a clear References block pointing one level deep to references/scenario-planning.md and scripts/scenario_modeler.py (both verified to exist); the core framework is appropriately inlined while deeper methodology lives in the reference, with minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

87%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.

The description is strong: third-person, concrete, with an explicit 'Use when...' clause anchored by a vivid natural-language trigger. Its only weakness is that the action list and trigger synonym coverage could be marginally broader.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'cross-functional what-if modeling,' 'models compound adversity across all business functions simultaneously,' 'cascading multi-variable scenarios' — but stops short of an exhaustive multi-action list like the 5-anchor.

4 / 5

Completeness

Explicitly answers both what ('cross-functional what-if modeling for cascading multi-variable scenarios') 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 the natural user phrase 'what if X AND Y both happen?' plus 'complex risk scenarios' and 'strategic decisions with major downside,' giving good keyword coverage, though a few common synonyms (stress test, contingency) are absent from the description itself.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche — compound/cascading multi-variable adversity — and explicitly differentiates from single-assumption stress testing, giving minimal conflict risk with adjacent skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alirezarezvani/claude-skills
Reviewed

Table of Contents

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.