company-research

# Company Research ## Purpose Use this skill to start and monitor Primr research runs through MCP. Treat MCP as the source of truth for current modes, defaults, and outputs. ## Workflow 1. Read `primr://research/modes` to confirm the current mode guidance. 2. Read `primr://research/status` to see whether a run is already active. 3. Call `estimate_run` before starting a new run. Supports `platforms` (array), `strategy_type`, and `no_ai_strategy` parameters. Returns `estimated_time_range` alongside `estimated_time_minutes`. 4. Present the estimate, state that the run incurs real API cost, and get explicit approval before calling `research_company`. 5. After starting a run, monitor with `wait_for_status_change` or `check_jobs` until terminal. 6. Read `primr://output/artifacts/by_job/{job_id}` to inventory completed-job artifacts without report body content, then read `primr://output/latest` only when a report preview is needed to present the result and next actions. Read `primr://output/qa_summary/by_job/{job_id}` when QA artifacts are attached and the user needs QA outcome metadata. Read `primr://output/usage_summary/by_job/{job_id}` when the user needs cost, timing, approval, or artifact-count metadata. Read `primr://output/source_summary/by_job/{job_id}` when the user needs citation/source appendix metadata. Read `primr://output/trace_summary/by_job/{job_id}` when the user needs scrape trace health metadata. Read `primr://output/verification_summary/by_job/{j...