financial-data-collector

Gathers and sources every valuation input with full provenance tracking.

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/lyndonkl/hermesworld --skill financial-data-collector-lyndonkl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: financial-data-collector
Source: https://github.com/lyndonkl/hermesworld/tree/main/packages/financial-data-collector/skills/valuation-specialists/financial-data-collector
Command: npx skills add https://github.com/lyndonkl/hermesworld --skill financial-data-collector-lyndonkl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Valuation and corporate-finance analyses fail when inputs are invented, unsourced, or silently computed. This Skill collects every analysis input — financial statements, footnotes, market data, macro rates, reference tables, and peer sets — and records exactly where each figure came from, which fallbacks were applied, and what remains missing. ## Core Features & Use Cases - Provenance-first collection: Every field in the output JSON carries source, as-of date, retrieval date, and a document reference precise enough to find the page again. - Structured gap accounting: Missing data is never invented; each gap records its status, the fallback ladder rung applied, its cost, and which downstream stages it constrains. - Validation gates: Runs six statement reconciliation ties and a reference-table vintage check (R4 rule) via Python scripts, and assesses the G1 gate predicate before handing off. - Use Case: As the first stage of a valuation orchestrator run, collect ten years of statements, footnotes, market data, Damodaran reference snapshots, and two peer sets for a public company, then emit raw-financials.json, market-data.json, sources.md, and gaps.json for downstream DCF and relative-valuation stages. ## Quick Start Ask the valuation orchestrator to run the data-collection stage for a company by supplying a mandate.json with mode, company identity, valuation currency, and valuation date.

Frequently Asked Questions about financial-data-collector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I collect financial data for a company valuation?

Supply a mandate.json with mode, company identity, valuation currency, and valuation date, plus any user-provided statements. The collector gathers ten years of statements, footnotes, market data, macro rates, reference tables, and peer sets, writing four provenance-tracked artifacts.

What outputs does the financial data collection stage produce?

It writes four files: raw-financials.json with per-field provenance, market-data.json with reference snapshots and vintage checks, sources.md listing every source and fallback, and gaps.json tracing each missing field to the downstream stages it constrains.

Can I use the financial data collector standalone outside a team run?

No, it is a stage brief loaded by the valuation orchestrator and is not for direct use. If you are working outside a team run, load the financial-data-sourcing skill instead, which carries the field tables and fallback ladders.

What happens when a required financial input cannot be found?

The collector never invents a figure. It walks the documented fallback ladder, records the rung used and its cost, and marks the field missing when the ladder runs out. Blocking gaps return a blocked or needs_input status to the orchestrator.

How are reference table vintages validated for a valuation date?

The R4 rule requires max minus min as-of dates within three months and the valuation date within twelve months of the oldest table. Date arithmetic runs through Python scripts, and stale tables are carried with status stale and disclosed in sources.md.