company-researchlisted

# 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/latest` to present the result and next actions. ## Operating Rules - Prefer the lightest mode that answers the request. - Do not restate fixed pricing or provider defaults from memory. Use MCP resources and `estimate_run`. - If a job is already in progress, surface that state instead of starting a second run. - Treat `full` as the standard end-to-end workflow and `premium` as the higher-cost, higher-depth option. - Expect standard runs to take roughly 35-50 minutes and premium multi-vendor runs to reach 75-120 minutes. - Do not hold the client in a synchronous wait for the entire run; launch once, then monitor and resume from job state. ## Example ```text User: Research ExampleCo at