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.

76

Quality

96%

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

92%

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

The body is an exceptionally actionable, well-sequenced financial-modeling skill with strong validation gates and feedback loops. Its one weakness is progressive disclosure: with no bundle files, the three large recipes live inline in one file rather than being split into navigable references.

Suggestions

Extract each model-type recipe (3-statement, DCF, LBO) into its own reference file under references/ and keep SKILL.md as an overview with one-level-deep links, improving navigation and token budget on partial use.

Move the peripheral output patterns (print delivery, football-field chart, returns waterfall) into a separate references/outputs.md and reference it from the body.

If the recipes stay inline, add a compact table-of-contents near the top so Claude can jump to the relevant recipe without loading the whole file.

DimensionReasoningScore

Conciseness

Dense and load-bearing rather than padded — it explicitly declines to re-teach finance ('Terse reference — not a finance textbook', 'runnable skeleton, not finance theory') and pushes shared rules to the base skill ('inherited, not re-taught'), so nearly every token earns its place despite the file's length.

3 / 3

Actionability

Copy-paste-ready officecli batch heredocs with exact props, verified flag values pinned to v1.0.63, and concrete formulas make the guidance fully executable rather than descriptive.

3 / 3

Workflow Clarity

Mandatory build orders, an executable six-gate Delivery cycle with explicit validation checkpoints, and feedback loops (cache-refresh pass, write-order surgery de-ring/re-ring, convergence verify) give clear sequencing with error recovery.

3 / 3

Progressive Disclosure

References to the base xlsx skill are clearly signaled one level deep ('→ see xlsx v2 §X'), but no bundle files exist and three full multi-step recipes (A/B/C, ~80 lines each) are inlined in a single monolithic file where they could be split into separate reference files.

2 / 3

Total

11

/

12

Passed

Description

100%

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 specific, trigger-rich, and explicitly scopes both when to invoke and when to route away, with concrete negative examples. It is a strong, third-person description that earns top marks on every dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '3-statement model, DCF valuation, LBO, SaaS unit economics, sensitivity / scenario analysis, debt schedule, or fundraising projections — in Excel' — matching the level-3 anchor of enumerating specific concrete capabilities.

3 / 3

Completeness

Clearly answers both 'what' ('build a financial model ... Output is a single formula-driven .xlsx') and 'when' ('Use this skill when the user wants ... Trigger on: ...'), with an explicit 'Use when' clause plus negative routing.

3 / 3

Trigger Term Quality

An explicit 'Trigger on:' block covers natural terms a finance user would actually say ('financial model', 'DCF', 'WACC', 'NPV', 'LBO', 'debt schedule', 'cash sweep', 'MOIC', 'IRR / XIRR', 'CAC / LTV'), giving good coverage with common variations.

3 / 3

Distinctiveness Conflict Risk

Distinct financial-modeling niche with explicit de-scoping ('DO NOT invoke for a simple budget tracker, CSV dump, or operational KPI sheet — route those to officecli-xlsx base') makes conflict with sibling skills unlikely.

3 / 3

Total

12

/

12

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.

Validation15 / 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.