Aimed at financial investment research data development and governance; for non-investment-research data requests, the responsibility classification applies equally, except that when the corresponding execution skill is missing, this will be stated truthfully.
MUST
- Routes only; does not connect to data sources, does not execute queries, does not generate business deliverables. The router itself does not execute; when the primary responsibility falls to an execution skill,that skill takes over execution, and the router no longer intervenes.
- Only selects skills actually provided by the current repository; capabilities that are not installed must be explicitly stated as unavailable.
- Select one primary responsibility at a time. For cross-domain tasks, first confirm the result to be delivered now, then handle subsequent responsibilities.
User wording → responsibility (speak plainly first, then determine responsibility)
| How the user might say it | Primary responsibility | Falls to |
|---|---|---|
| "Help me create an XX table / design the table schema / write DDL / define schema / how to create a table" | Data contract / DDL | finance-ddl-design |
| "Help me do incremental sync of XX data / pipeline / how to import daily / backfill history / the task is very slow / data loss / duplicates" | Pipeline development | finance-pipeline-dev |
| "Help me design an interface to query XX data / MCP tool / view / API" | Query interface | finance-query-contract |
| "Is this data correct / help me quality-check (accept) the XX table / produce a quality check report / market value is absurd / missing data / financial reports not updated / doesn't match" | Quality acceptance | finance-data-qc |
| "Data contract / governance / lineage / owner / SLA / compliance / masking / export" | Governance or compliance | No execution skill provided yet |
Responsibility classification
- Data contract / DDL: schema, primary key, types, naming, partitioning, and compatibility design.
- Table creation/alteration and DDL design for the investment research database → finance-ddl-design, which takes over execution.
- Other datasets → no dedicated execution skill is currently provided.
- Pipeline development: incremental, idempotency, backfill, rerun, and failure recovery.
- Pipeline design/troubleshooting for the investment research database → finance-pipeline-dev, which takes over execution.
- Other datasets → no dedicated execution skill is currently provided.
- Quality acceptance: prove whether the data satisfies traceable rules.
- Financial investment research database (market data, financials, announcement events, master data, index funds, macro industry) → finance-data-qc, which takes over execution.
- Other datasets → no dedicated execution skill is currently provided.
- Query interface: view/API query contract, filtering and pagination, temporal aspects, and performance budget.
- Query interface design/troubleshooting for the investment research database → finance-query-contract, which takes over execution.
- Other datasets → no dedicated execution skill is currently provided.
- Data governance: catalog, lineage, owners, SLA, and lifecycle. No execution skill is currently provided.
- Compliance: classification, least privilege, masking, export, retention, and audit. No execution skill is currently provided.
Routing Steps
- First look at the "user phrasing → responsibility" table, use the deliverable to determine the primary responsibility, and do not classify by database or tool name; if unsure, first list candidate responsibilities.
- If the primary responsibility is table creation/DDL design for the investment research database, read and execute finance-ddl-design。
- If the primary responsibility is pipeline design/troubleshooting for the investment research database, read and execute finance-pipeline-dev。
- If the primary responsibility is query interface design/troubleshooting for the investment research database, read and execute finance-query-contract。
- If the primary responsibility is financial investment research quality acceptance, read and execute finance-data-qc。
- If the target skill is not installed, explain the missing capability; do not pass off an adjacent skill as it.
- If a request contains multiple responsibilities, ask only one focused question that would change the primary responsibility.
STOP
- Unable to determine whether the user wants a "design, development, acceptance, service, governance, or compliance conclusion."
- The target capability is not yet provided.
- A database connection is required to complete the routing determination.