Menu
Retrieve and update company hypotheses in Primr. Use when the user asks what is already known, wants to validate a claim, or wants to persist a research finding.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Produce a primr-style strategic company brief using ONLY the host agent's own tools (web search, page fetch, shell DNS lookups) at subscription cost. No primr install, no API keys, no GPU. Use when the user wants a structured pre-discovery brief on a company but cannot or does not want to run the full primr pipeline. For the full pipeline (deeper scraping, 40+ sources, cross-validation, QA gates), use the primr skill instead.
Build a substantial, sourced Primr-style company dossier with zero Primr model API spend by combining keyless evidence collection with an official agent host. Use when an agent host receives a bare Primr company-and-URL request without explicit paid intent, the user has no API keys or GPU, wants to use an included Codex, Claude, Copilot, Gemini, Cowork, or other plan allowance, asks for a free or hard-zero Primr path, or supplies a Primr prep evidence bundle. Verify that the host is plan-backed and will not bill API usage or overages before promising zero total incremental spend.
Route and run Primr company research from an agent host. Use for a bare Primr company-and-URL request, named Primr report, full strategic dossier, Strategic Overview, or strategy module. Default to Primr Zero unless the user explicitly requests paid, metered, provider-backed, or premium execution; use an inline primr prep fallback when primr-zero is unavailable. Route quick briefs to host web research and DNS-only requests to primr recon.
Run and monitor company research through Primr MCP. Use when the user wants a new research run, asks for status, or needs mode selection help before starting.
Run end-to-end company research through Primr. Use when the user asks to research a company, provides a company URL, or wants a new strategic analysis run.
Guide mode selection when site scraping is weak, blocked, or low quality. Use when the user asks why scraping failed or how Primr should proceed on a protected site.
| name | hypothesis-tracking |
| version | 1.1.0 |
| description | Retrieve and update company hypotheses in Primr. Use when the user asks what is already known, wants to validate a claim, or wants to persist a research finding. |
| mcp_server | primr |
| tools | ["get_hypotheses","save_hypothesis"] |
| resources | ["primr://context"] |
Use this skill to manage durable research memory for a company. Hypotheses are a working memory layer, not final truth.
Retrieve hypotheses before starting duplicate research.
Present confidence clearly: untested, validated, invalidated, or confirmed.
Update confidence only when new evidence exists.
Keep evidence strings short, factual, and source-oriented.
Distinguish known facts from open hypotheses.
Preserve the evidence trail when confidence changes.
Prefer updating an existing hypothesis over creating duplicates.
Expired or weak hypotheses should be re-validated before being presented as current.
get_hypotheses(company="ExampleCo", topic="technology")
save_hypothesis(company="ExampleCo", hypothesis_id="h_001", confidence="validated", evidence="CTO interview confirms AWS usage")