conventions — Claude Code skill for financial model rules
The conventions Claude Code skill sets formatting and sourcing rules for financial work. It applies across deskstack roles, from analyst tasks to VP reviews.
MIT ★ 86 updated 2026-11-16
/plugin marketplace add joaquimmj/deskstack
/plugin install deskstack@deskstackWhat conventions does
conventions defines how deskstack roles build and review financial models. Every figure needs a source, period, and unit; inputs beyond the connector’s coverage must come from the user. Work stops when the deskstack connector is disconnected, and the guide skill explains how to add it.
The rules cover banking-style Excel formatting, a Sources sheet for typed figures, and explicit assumptions with rationales. Reviewers flag cell references and severity without editing the deliverable; analysts make changes only after user approval. For banks and insurers, the skill rules out EBITDA, EV, and an unlevered DCF, and offers P/E, P/B, or a dividend model instead.
What it helps with
- format typed inputs, formulas, and cross-sheet links with distinct colors
- record a source and period for every manually entered figure
- separate reported data from user-provided assumptions
- review a model with cell references and issue severity
Example prompts for the agent
- Build a company financial model using deskstack rules and add a Sources sheet.
- Review this model and list affected cells with severity levels.
- Value this bank using an approach other than EBITDA and EV.
How to install conventions
1Plugin marketplace
/plugin marketplace add joaquimmj/deskstack/plugin install deskstack@deskstackThis installs the whole deskstack plugin with all its skills
2Skills CLI (Vercel)
npx skills add joaquimmj/deskstack --skill conventions -a claude-code3Manually: put the files in place
~/.claude/skills/conventions/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/conventions/
1Skills CLI (Vercel)
npx skills add joaquimmj/deskstack --skill conventions -a codex2Manually: put the files in place
.agents/skills/conventions/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add joaquimmj/deskstack --skill conventions -a cursor2Manually: put the files in place
.cursor/skills/conventions/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install joaquimmj/deskstack plugins/deskstack/skills/conventions2Manually: put the files in place
.github/skills/conventions/SKILL.md1Skills CLI (Vercel)
npx skills add joaquimmj/deskstack --skill conventions -a gemini-cli2Platform CLI
gemini skills install https://github.com/joaquimmj/deskstack --path plugins/deskstack/skills/conventionsManually: put the files in place
.devin/skills/conventions/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about conventions
How do I install conventions in Claude Code?
Add the marketplace with /plugin marketplace add joaquimmj/deskstack, then install the skill with /plugin install deskstack@deskstack.
What does conventions do?
It sets rules for financial models, including spreadsheet formatting, figure sources and periods, assumption notes, and review workflow.
What does conventions need to work?
Company figures, rates, and valuation inputs come from the deskstack connector. If it is disconnected, work stops; the guide skill covers connecting it.
Source text
SKILL.md · MIT
--- name: conventions description: deskstack house rules for financial work: banking formatting, a cited source for every number, units and periods stated, ask instead of invent. Use with any deskstack role. --- # deskstack conventions Every deskstack role (analyst, associate, VP review, one-shot commands) follows these rules. They are public, widely used modeling practices. ## Numbers come from tools or from the user, never from memory - Filed figures come from the **deskstack connector**: - `financial_statements` and `key_metrics` for company figures (SEC for the US, ESEF for the EU); - `risk_free_rate` and `fx_rate` for rates; - `valuation_inputs` for Damodaran ERP, betas and cost of capital. - Each tool result carries `sources` (URL, accession or ID, period). Keep them. - **If a tool returns `null`, the figure is not reported.** Say so, and never fill the gap with a number from memory. - Anything the tools don't cover (share price, target multiples, management guidance, a scenario) is **asked of the user** and cited as "User-provided, <date>". - If the connector isn't connected, stop and say how to add it (see the `guide` skill). Don't fall back to web numbers without saying so, and cite the page for each one if the user accepts. ## Workbook formatting (banking convention) | Element | Format | |---|---| | Typed input | **Blue** font (`0000FF`) | | Formula | Black font | | Link to another sheet | Green font | | Calculations | Formulas only. No number typed inside a formula (`=B5*1.05` hides an assumption) | | Units | In the sheet title: "Inputs (USD in millions)". One unit per sheet. Convert explicitly when linking | | Periods | Unambiguous labels: `FY2025` (fiscal year, with its end date when not December), `LTM`, `FY2026E` | | Signs | Capex and D&A positive, subtracted in the formula. One convention throughout | ## A Sources sheet row for every typed number | Column | Content | |---|---| | Cell | e.g. `Inputs!D5` | | Item | e.g. "Revenue" | | Period | e.g. `FY2025` | | Value | The number as typed | | Source | e.g. "SEC 10-K FY2025, accession 0000320193-25-000079, us-gaap Revenues (deskstack financial_statements)". For assumptions: "Analyst assumption: <rationale>". For user inputs: "User-provided, <date>" | ## Every deliverable - Starts with what it is, the company, the currency and the units. - Lists assumptions explicitly, each with its rationale. - Ends with: **"Draft for human review. Not investment advice."** - **Banks and insurers:** when `company_lookup` or `financial_statements` flags a financial company, say that EBITDA, EV and an unlevered DCF don't apply. Offer P/E, P/B or a dividend model instead. - Reply in the user's language (French or English); keep tool and cell names as they are. ## Reviews - Reviewers (associate, VP) **report**; they never edit the deliverable. - The analyst applies fixes only after the user agrees. - Each review lists cell references and severity: blocker, major, minor. - Nothing is final until the user signs off.
© Joaquim · MIT · joaquimmj/deskstack