Menu
Review Primr outputs and diagnose integration issues. Use when the user wants report quality assessment, output review, or system health checks.
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 | primr-qa |
| version | 1.1.0 |
| description | Review Primr outputs and diagnose integration issues. Use when the user wants report quality assessment, output review, or system health checks. |
| metadata | {"openclaw":{"requires":{"bins":["primr-mcp"],"env":["XAI_API_KEY","GEMINI_API_KEY"],"os":["linux","darwin","win32"]}}} |
| mcp_server | primr |
| tools | ["run_qa","doctor"] |
| resources | ["primr://output/latest","primr://config"] |
Use QA to judge research usefulness and trustworthiness, not just formatting. Use diagnostics when the failure is operational rather than editorial.
This skill should stay close to MCP outputs. Avoid embedding fixed provider assumptions in the skill body.
Read primr://output/latest when no path is specified, then call run_qa on the concrete report file.
run_qa(report_path="output/exampleco/report.md")
Call doctor when the issue looks like environment, API, or runtime configuration rather than report quality.
Focus on factual gaps, weak evidence, and thin strategic interpretation before cosmetic issues.
QA failures: run doctor and confirm the report path.
Low scores: identify the weakest sections and recommend one next action.
Config issues: use primr://config and doctor to explain what is missing.