agentsclimarketplace
Sign in

Business impact model

Skill sujanbhuiyan/Skills/skills/business-impact-model

Generates a multi-sheet .xlsx financial impact model with live cross-sheet Excel formulas, three scenarios (Conservative/Base/Optimistic), and a consistent input/formula/result color convention. Use when building a revenue projection, ROI model, growth-strategy financial model, or business case that needs a real working spreadsheet rather than static numbers.From its SKILL.md

Install
npx -y skills add sujanbhuiyan/Skills --skill business-impact-model

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.7 KB, 752 tokens by cl100k_base, as published. Nobody here has run it

Business Impact Model

What this does

Produces a client-ready, multi-sheet Excel workbook that turns a set of assumptions into a Year-1 revenue projection, an investment plan, and an ROI/KPI dashboard — with live cross-sheet formulas so every number recalculates when an input changes. It runs three scenarios side by side (Conservative / Base / Optimistic) from a single assumptions block.

When to use it

  • Building the financial half of a growth strategy or proposal.
  • A stakeholder needs a "what if we change this input" model, not a snapshot.
  • You need ROI, payback, and a KPI dashboard derived from revenue pillars.
  • You want consistent, auditable spreadsheet conventions across deliverables.

How to use it

  1. Read references/model-structure.md to understand every sheet, its columns, and the color/formula conventions.

  2. Generate the starter workbook (deterministic — always prefer the script over hand-building cells):

    python scripts/build_model.py                       # -> business_impact_model.xlsx
python scripts/build_model.py /path/to/output.xlsx  # custom output path

    The script requires openpyxl (pip install openpyxl); it exits with a clear message if missing. No network access.

  3. Open the workbook and replace the blue placeholder inputs on Assumptions & Inputs with the client's real numbers across the three scenario columns. All black and green cells are formulas and update automatically — do not overwrite them.

  4. Add or rename pillar/revenue-stream build sheets to match the engagement (one sheet per pillar). Mirror the existing formula pattern so the Y1 Revenue Projection, Investment Plan, and ROI & KPI Dashboard roll-ups keep referencing them.

  5. Sanity-check: every result cell should change when you edit a blue input, and the workbook should open with zero #REF!/#DIV/0! errors.

Inputs

  • The revenue pillars / streams for the engagement (1+).
  • Per-scenario assumptions (price points, volumes, ramp curves, conversion, spend) for Conservative / Base / Optimistic.
  • Investment line items (retainer + project costs + tooling).

Output

business_impact_model.xlsx (default in the working directory, or the path you pass) — a workbook with these sheets: Cover & Summary, Assumptions & Inputs, one or more Pillar build sheets, Y1 Revenue Projection, Investment Plan, ROI & KPI Dashboard.

Notes & constraints

  • Formulas are real Excel formulas (e.g. =Assumptions!C7*'Pillar 1'!N8), never hard-coded results — this is the whole point of the model.
  • Color convention (kept identical everywhere): blue font = manual input, black font = in-sheet formula, green font = cross-sheet link, yellow fill = key result.
  • openpyxl writes formulas but does not evaluate them; open the file in Excel / Google Sheets / LibreOffice once to compute values.
  • Keep state in a single assumptions block so scenarios stay consistent; never duplicate an input across sheets — link to it.
  • Use forward-slash paths. Don't assume openpyxl is installed elsewhere.

What ships with it: 2 files

19.5 KB alongside SKILL.md, 1 of them executable

references/

scripts/

Gives 0 of the 12 instructions most pdf office docs skills give in 752 tokens

Counted across 569 of the 585 authors here whose files we hold, read 2026-09-06

  • Ensure every slide fits inside one viewportin 20 of 569, across 11 files
  • Check for product marketing context firstin 15 of 569, across 5 files
  • Ask for the minimum neededin 15 of 569, across 5 files
  • Set the API key environment variablein 15 of 569, across 10 files
  • Support keyboard and touch navigationin 14 of 569, across 5 files
  • Match the buyer stagein 13 of 569, across 3 files
  • Split overflowing content into multiple slidesin 12 of 569, across 3 files
  • Set page size explicitly for consistent resultsin 12 of 569, across 5 files
  • Convert documents to markdown using pandocin 12 of 569, across 6 files
  • Read STYLE_PRESETS.md before generatingin 12 of 569, across 7 files
  • Send multipart POST requests to the APIin 12 of 569, across 7 files
  • Use smart quotes for new contentin 11 of 569, across 4 files

Said here and by no other author read

  • Read references for structure and conventions
  • Run the python script to generate the starter workbook
  • Replace blue placeholder inputs with real numbers
  • Add or rename pillar sheets to match the engagement
  • Sanity check that results change when editing inputs

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.