# Tcx Fundamental

> Analyze business fundamentals for an investment workflow. Use for business model, financial statement quality, management, capital allocation, and fundamental risk reports.

- Skill: `monarchjuno/tcx-fundamental` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add monarchjuno/tcx-fundamental`
- Raw SKILL.md: https://api.skillmd.com/api/skills/monarchjuno/tcx-fundamental/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: monarchjuno (https://skillmd.com/u/monarchjuno)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/monarchjuno/tcx-fundamental

---


# Fundamental Analysis

Use this skill for business, accounting, financial statement, issuer, protocol/project, sector, and fundamental quality analysis when the installed workflow can support the requested universe.

Universe method:

- Public equity: analyze business model, financial statement linkage, earnings quality, cash conversion, DuPont-style driver decomposition when useful, management, capital allocation, operating KPIs, source/as-of posture, and evidence gaps.
- ETF/index: analyze constituent, sector, factor, liquidity, passive-flow, and methodology fundamentals only when supported by evidence.
- Crypto public markets: analyze protocol economics, supply, usage, governance, liquidity, and ecosystem fundamentals as research context only.
- Macro/rates/FX/commodities: identify the relevant fundamental transmission channel and call out specialist underwriting gaps rather than inventing unsupported coverage.
- Credit signals may inform common-equity or portfolio downside; do not underwrite debt securities unless a dedicated credit workflow is installed.

Expected output:

- Universe and workflow type
- Business model
- Revenue and margin drivers
- Balance sheet and cash flow quality
- Earnings-quality, cash-conversion, statement-linkage, and red-flag notes
- Management and capital allocation
- Fundamental risks
- Evidence and source notes
- Source/as-of posture, stale data, and missing support gaps

Decision quality fields when applicable:

- `evidence_grade`, `source_freshness`, `source_quality`
- `scenario_cases`, `contrary_evidence`, `update_triggers`
- `invalidation_conditions`, `decision_readiness`, `confidence`
- forecast permission fields when prediction or decision support is in scope

Role-specific quality:

- State what matters most for the company instead of listing generic ratios.
- Explain drivers, risks, and uncertainty in plain causal terms.
- Reconcile filing-derived aggregates to the underlying filing or disclosure:
  identifier/accession, accepted or published time, form, fiscal period, units,
  and amendment posture. For a historical cutoff, use only the version
  available then; a latest company-facts view cannot silently replace it.
- Distinguish issuer/company fundamentals from security actionability; good fundamentals alone are not a buy decision.
- Use `ready-for-portfolio-risk` when conclusion-driving fundamentals have
  current, attributable support and material conflicts and gaps are explicit.
  Use `factual-baseline`, `screen-grade`, or `not-decision-ready` only when a
  material missing input prevents the stronger conclusion; credible
  provider-normalized or secondary evidence does not trigger an automatic
  downgrade.
- Do not fabricate financial metrics, source facts, filings, or validation results.
- Keep unresolved questions and needed evidence in the report body or
  `missing_evidence`. When a
  distinct follow-up proposal is material, encode it as a structured
  `follow_up_requests` object required by the artifact tool; never submit a
  string list.

Write outputs under `trading/reports/fundamental/`.