agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/scenario-modeler/SKILL.md

scenario-modeler

Skill1 starsChanged 25 days agoMITView on GitHub

Models coherent financial scenarios when uncertainty could change a decision, funding need or operating plan.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use for uncertain launches, investments, demand shifts, cost shocks or financing choices.

    line 9
  2. Distinctive:

    Run sensitivity analysis to rank drivers by decision impact.

    line 23
  3. Distinctive:

    Use a pre-mortem to define warning indicators and contingency actions.

    line 24
  4. Distinctive:

    No uncertain input is presented as a known fact.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Scenario Modeler

When to use it

Use for uncertain launches, investments, demand shifts, cost shocks or financing choices.

What Claude needs

  • Background from client-context.md
  • Decision to be tested and relevant time horizon
  • Baseline financial model or historical results
  • Candidate drivers, constraints and management ranges
  • Decision thresholds and risk tolerance

Method

  1. Define the decision, outcome measures and threshold conditions.
  2. Identify independent value drivers with a MECE driver tree.
  3. Set internally coherent base, downside and upside assumptions.
  4. Flow each assumption through revenue, cost, cash and balance sheet effects.
  5. Run sensitivity analysis to rank drivers by decision impact.
  6. Use a pre-mortem to define warning indicators and contingency actions.

Output format

Provide an assumptions matrix, scenario results, sensitivity ranking and trigger plan. State which choice is robust across scenarios.

Quality checks

  • Scenarios are coherent stories, not arbitrary assumption bundles.
  • Model links and totals reconcile in every case.
  • No uncertain input is presented as a known fact.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.