source-router

Plans evidence source routing with trust tiers, fallbacks, and validation for investment research.

Updated May 9, 2026
One-click install
npx skills add https://github.com/122yjs/invest_harness --skill source-router-122yjs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-router
Source: https://github.com/122yjs/invest_harness/tree/main/plugins/vertical-plugins/invest-research/skills/source-router
Command: npx skills add https://github.com/122yjs/invest_harness --skill source-router-122yjs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Investment research pipelines often pick data sources ad hoc, mixing low-trust vendor snapshots with official filings and leaving gaps unrecorded. This Skill reads an evidence plan and produces a deterministic source-call-plan that maps every required evidence type to capability-matched sources, trust tiers, fallbacks, and validation checks before analyst fan-out begins. ## Core Features & Use Cases - Capability-Based Source Selection: Selects sources by required evidence types and source capability rather than fixed use-case labels, ranking them by trust tier from T0 company/regulator disclosures down to T3 discovery sources. - Runtime Availability Probing: Merges live probe results into the plan, excludes runtime-unavailable sources from primary routing, and records missing tools or endpoints as unresolved data gaps. - Coverage Self-Check: Emits a machine-readable coverage block verifying every evidence type has a primary source and at least one fallback before the plan is declared complete. - Use Case: Before running analyst fan-out on a listed company, route financial statement evidence to SEC EDGAR or DART/KRX as primary with yfinance or FMP as fallback, and log any unavailable endpoints in unresolved-data-gaps.md. ## Quick Start Read the evidence plan in the active workspace and generate the source-call-plan, source-validation, and unresolved-data-gaps files under the 00_evidence directory.

Frequently Asked Questions about source-router

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

FAQPage Schema
How do I route evidence types to the right data sources?▼

Read the evidence plan's required_evidence_types and match each to sources by capability, not fixed use-case labels. Rank candidates by trust tier, preferring T0 company official or regulator disclosures over vendor snapshots, and always include at least one fallback source.

What sources should I use for company financial statements?▼

For reported company facts, financial statements, guidance, and share counts, select Company IR, SEC EDGAR, DART/KRX, or local regulator filings first. Use yfinance, FMP, or Alpha Vantage only as fallbacks, and record a data gap if T0 evidence is unavailable.

Can I use web search results as evidence directly?▼

No. Web Search is only for discovering candidate URLs. You must fetch and read the article, document, or PDF body before citing it as evidence, and record body retrieval failures as data gaps.

What happens when a documented source is unavailable at runtime?▼

The live probe marks it runtime_unavailable and excludes it from primary routing. If a declared fallback exists, routing shifts to it; otherwise the evidence type is recorded as a data gap in unresolved-data-gaps.md before analyst fan-out.

What are the limitations of source routing in this workflow?▼

It is a planning layer only and does not execute API calls or store API keys. It cannot promote lower-trust evidence above T0 for material claims, and sources with documented_only, planned, or external_manual status must be logged as gaps rather than assumed callable.