financial data collector

Engineering Community

Skill notes

Critical Constraints

NO FALLBACK values. If a field cannot be retrieved, set it to null with _source: "missing". Never substitute defaults (e.g., beta or 1.0). The downstream skill decides how to handle missing data. Data source attribution is mandatory. Every data section must have a _source field. CapEx sign convention: yfinance returns CapEx as negative (cash outflow). Preserve the original sign. Document the convention in output metadata. Do NOT flip signs.

Step 1: Collect Data

Run the collection script: The script collects in this priority: yfinance — market data, historical financials, beta, analyst estimates yfinance ^TNX — 10Y Treasury yield as risk-free rate proxy User supplement — for years where yfinance returns NaN (report to user, do not guess)

Step 2: Validate Data

Checks: field completeness, cross-field consistency (Market Cap = Price × Shares), range sanity (WACC 5-20%, beta 0.3-3.0), sign conventions.

Step 3: Deliver JSON

Single file: {TICKER}_financial_data.json. Schema in references/output-schema.md. Do NOT create: README, CSV, summary reports, or any auxiliary files.

Output Schema (Summary)

Full schema with all field definitions: references/output-schema.md <correct_patterns>

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@daymade · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Collect Data

Run the collection script: The script collects in this priority: yfinance — market data, historical financials, beta, analyst estimates yfinance ^TNX — 10Y Treasury yield as risk-free rate proxy User supplement — for years where yfinance returns NaN (report to user, do not guess)

02
Step 2: Validate Data

Checks: field completeness, cross-field consistency (Market Cap = Price × Shares), range sanity (WACC 5-20%, beta 0.3-3.0), sign conventions.

03
Step 3: Deliver JSON

Single file: `{TICKER}_financial_data.json`. Schema in `references/output-schema.md`. Do NOT create: README, CSV, summary reports, or any auxiliary files.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.