Financial Data Sourcing
Maps every input a company analysis needs to where it comes from — filing line items, market data, Damodaran reference datasets, macro series — with units, update frequency, acceptable fallbacks and the consistency rules that bind them. Use when gathering data for a valuation, when an input is missing and a substitute is needed, when deciding whether a user-supplied figure can be accepted at face value, or when checking that figures are internally consistent.
Install
/plugin marketplace add lyndonkl/claudeThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add lyndonkl/claude --skill financial-data-sourcinggit clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/financial-data-sourcing ~/.claude/skills/financial-data-sourcingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Financial data sourcing Every number in a valuation comes from somewhere, and the analysis is only as good as the worst-sourced number in it. This skill is the input contract. It says what to fetch, from which source, in what units, how stale it may be, whether a user may hand it over directly, and what to substitute when it cannot be found. Two consumers depend on it. The `financial-data-collector` agent uses it to fill four artifacts. The orchestrator's gates `G1_data`, `G3_financials`, `G4_discount_rate` and `G5_forecast` are predicates over the fields defined here. This skill does not carry method. It says what must be in hand before a procedure can run. For how a number is used, follow the concept path cited beside it. ## What you produce | Artifact | Contents | |---|---| | `01-data/raw-financials.json` | Every company field, per period, with `source` and `as_of` on each leaf | | `01-data/market-data.json` | Every market field, plus the loaded reference-table snapshots with their `as_of` | | `01-data/sources.md` | One line per source actually used, with retrieval date and document reference; every fallback and stale field listed | | `01-data/gaps.json` | One entry per attempted field: status, fallback applied, and the stage it constrains | Collect. Do not compute. Derived quantities belong to the downstream skills: `financial-statement-normalization` for lease and R&D capitalization, invested capital and
Details
- Skill name
financial-data-sourcing- Repository
- lyndonkl/claude
- Path
skills/financial-data-sourcing/SKILL.md- Repo updated
- 1 September 2026
FAQ
What does the Financial Data Sourcing skill do?
Maps every input a company analysis needs to where it comes from — filing line items, market data, Damodaran reference datasets, macro series — with units, update frequency, acceptable fallbacks and the consistency rules that bind them. Use when gathering data for a valuation, when an input is missing and a substitute is needed, when deciding whether a user-supplied figure can be accepted at face value, or when checking that figures are internally consistent.
How do I install the Financial Data Sourcing skill?
Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Financial Data Sourcing popular?
It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.
Related skills
Abstraction Concrete Examples
200lyndonkl/claude
Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.
Academic Letter Architect
200lyndonkl/claude
Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.
Adr Architecture
200lyndonkl/claude
Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.
Financial Statement Normalization
200lyndonkl/claude
Converts reported financial statements into valuation-ready numbers — capitalizes R&D into a research asset, capitalizes operating leases into debt, strips one-time items, normalizes cyclical or trough earnings, derives FCFF and FCFE, and computes invested capital, ROIC, economic value added and the diagnostic ratio pack. Use when cleaning up EBIT before a DCF, capitalizing research or leases, deciding whether a restructuring charge is really non-recurring, computing free cash flow to the firm or to equity, measuring return on invested capital, normalizing earnings for a cyclical or commodity
Expense Report
213TerminalSkills/skills
Organize, categorize, and summarize business expenses for reimbursement and tax preparation. Use when a user asks to create an expense report, organize receipts, categorize expenses, summarize spending, prepare expenses for reimbursement, or compile business expenses for tax filing. Handles receipts, CSV data, and manual entries.
Financial Unit Economics
200lyndonkl/claude
Analyzes profitability per customer, product, or transaction to determine business model viability and scalability. Covers CAC, LTV, contribution margin, cohort analysis, and growth-readiness assessment. Use when evaluating business model viability, validating startup metrics (CAC, LTV, payback period), making pricing decisions, comparing business models, or when user mentions unit economics, CAC/LTV ratio, contribution margin, customer profitability, or break-even analysis.
Browse the most popular Claude skills, all finance & crypto skills, or write your own with the skills generator.