CtrlK
BlogDocsLog inGet started
Tessl Logo

officecli-financial-model

Use this skill when the user wants to build a financial model — 3-statement model, DCF valuation, LBO, SaaS unit economics, sensitivity / scenario analysis, debt schedule, or fundraising projections — in Excel. Trigger on: 'financial model', '3-statement model', 'P&L + BS + CF', 'DCF', 'WACC', 'NPV', 'terminal value', 'LBO', 'debt schedule', 'cash sweep', 'MOIC', 'IRR / XIRR', 'sensitivity table', 'scenario analysis', 'ARR model', 'unit economics', 'CAC / LTV', 'cap table forecast'. Output is a single formula-driven .xlsx. This skill is a scene layer on top of officecli-xlsx — it inherits every xlsx v2 rule (4-color code, visual floor, number formats, cache-drift, Known Issues, Delivery Gate minimum cycle). DO NOT invoke for a simple budget tracker, CSV dump, or operational KPI sheet — route those to officecli-xlsx base.

72

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a strong, deeply actionable skill body: fully executable commands, mandatory build sequences, and unusually rigorous validation gates with feedback loops. The main weakness is token efficiency — the same engine-caveat material (NPV cache-0, iterate/write-order surgery) is repeated across three sections and version pins are scattered inline rather than consolidated.

Suggestions

Consolidate the NPV/XNPV cache-0 guidance into one canonical section (e.g., Known Issues) and have Recipe B Step 4 and 'Financial function patterns' reference it with a single line instead of re-explaining the SUMPRODUCT fallback three times.

Merge the write-order/iterate material in Recipe C Step 3 with the 'Write-order surgery' playbook under 'Circular references & iterative calc', keeping only a pointer in the recipe.

Move version-pinned caveats ('verified on v1.0.63', 'on v1.0.63+') into a dedicated version-compatibility note in Known Issues instead of repeating the version number inline, so stale pins are easy to update.

Consider splitting the three recipes into references/ files (three-statement.md, dcf.md, lbo.md) with a short in-body overview, since the 560-line single file is at the upper limit of navigable.

DimensionReasoningScore

Conciseness

The body is mostly operational with no finance-theory padding ('runnable skeleton, not finance theory'), but guidance is systematically duplicated across sections — the NPV-caches-0 fix appears in Recipe B Step 4, twice in 'Financial function patterns', and again in 'Known Issues'; write-order/iterate surgery appears in both Recipe C and 'Circular references' — and the version pin 'v1.0.63' is cited five times inline with no deprecated/old-patterns section. This matches 'mostly efficient but could be tightened' rather than the minor-instances anchor.

3 / 5

Actionability

Nearly every instruction is a copy-paste-ready command: complete heredoc `officecli batch` JSON with exact props and number formats, precise `--type`/`--prop` flags for named ranges, comments, validation dropdowns, and per-recipe verification one-liners. Specific examples cover the three common model cases end-to-end.

5 / 5

Workflow Clarity

Each recipe has a mandatory build order with dependency rationale ('Do NOT build BS before P&L — RetainedEarnings depends on NI'), and the Audit & Delivery Gate section provides six executable gates with REJECT/exit-1 checks, error-recovery feedback loops (cache-refresh pass, de-ring/write/re-ring surgery, convergence verification), and an explicit 'assume there are problems' posture.

5 / 5

Progressive Disclosure

Structure is good: base xlsx rules are delegated one level deep to skills/officecli-xlsx/SKILL.md via clearly signaled '→ see xlsx v2 §X' pointers, and the body keeps only financial-model deltas. However, no bundle files exist, so all three large recipes plus sensitivity/scenario and circularity playbooks live inline in a single 560-line file where a references/ split (e.g., per-recipe files) would ease navigation — a minor organization gap rather than misplaced content.

4 / 5

Total

17

/

20

Passed

Description

100%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 exemplary: explicit what and when, an extensive natural-language trigger list with synonyms, a concrete output statement, and explicit reverse-routing that minimizes conflict with the sibling xlsx base skill. No fluff or over-claims are present.

DimensionReasoningScore

Specificity

The description enumerates concrete deliverable types ('3-statement model, DCF valuation, LBO, SaaS unit economics, sensitivity / scenario analysis, debt schedule, or fundraising projections'), names the tool and output form ('Output is a single formula-driven .xlsx'), and comprehensively covers the skill's scope with no obvious gaps.

5 / 5

Completeness

It explicitly answers both questions: what ('build a financial model ... in Excel', 'Output is a single formula-driven .xlsx') and when ('Use this skill when the user wants to build...', plus a concrete trigger-term list), which is the top anchor's what-and-when-with-concrete-triggers pattern.

5 / 5

Trigger Term Quality

The 'Trigger on:' list covers 18 natural phrases a user would actually say, including synonyms and abbreviations ('financial model', 'DCF', 'WACC', 'NPV', 'terminal value', 'IRR / XIRR', 'MOIC', 'CAC / LTV', 'sensitivity table', 'cap table forecast'), matching the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

It stakes a clear niche (financial modeling in Excel on top of officecli-xlsx) and actively manages overlap risk with an explicit negative trigger ('DO NOT invoke for a simple budget tracker, CSV dump, or operational KPI sheet — route those to officecli-xlsx base').

5 / 5

Total

20

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (562 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
Team-Commonly/commonly
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.