> ## Documentation Index > Fetch the complete documentation index at: https://docs.oppin.ai/llms.txt > Use this file to discover all available pages before exploring further. # Commands > Ready-made analyses you can run from your assistant in one step. Commands are analyses Oppin ships ready to run. Each one follows a fixed, tested sequence, so it is more reliable than the same request typed freehand. Apps list them differently: in Claude Code, type `/` and look for the Oppin ones (they show as `/mcp__oppin__`). In other assistants, look for Oppin's prompts in the menu where you add files or tools. Every analysis command takes an optional **output**: `text` (the default), `page` (one interactive page, an artifact in Claude), `pdf`, `slides`, `csv` or `json`. The csv and json fields stay the same every run, so rows can be appended to a sheet. ## Ideas `oppin_ideas`: Ideas for what to ask Oppin: ready-to-paste prompts, grouped by what you want to get done. | Argument | What it does | | :- | :- | | `category` | Optional: Pulse, Competition, Perception, Hidden demand, Content, Citations, Reporting or Tracking. Default: a starter set across all of them. | ## Weekly pulse `oppin_weekly_pulse`: Week-over-week digest: what moved, who moved it, and what to do about it. | Argument | What it does | | :- | :- | | `brand` | Brand name or id. Optional with a single brand. | | `output` | How to deliver the result: text (default), page (one interactive HTML page, an artifact where the client supports one), pdf, slides, csv or json. | Used in: [Weekly pulse](https://docs.oppin.ai/mcp/use-cases/pulse.md#weekly-pulse). ## Engine scorecard `oppin_engine_scorecard`: Per-engine breakdown: where the brand wins, where it loses, and why. | Argument | What it does | | :- | :- | | `brand` | Brand name or id. Optional with a single brand. | | `period` | The period: 7d, 30d, 3m, 1y or custom:YYYY-MM-DD:YYYY-MM-DD. Default: `30d`. | | `output` | How to deliver the result: text (default), page (one interactive HTML page, an artifact where the client supports one), pdf, slides, csv or json. | Used in: [Engine blind spot](https://docs.oppin.ai/mcp/use-cases/competition.md#engine-blind-spot). ## Competitor radar `oppin_competitor_radar`: Scan every competitor for movements larger than a threshold, and explain them. | Argument | What it does | | :- | :- | | `brand` | Brand name or id. Optional with a single brand. | | `period` | The period: 7d, 30d, 3m, 1y or custom:YYYY-MM-DD:YYYY-MM-DD. Default: `30d`. | | `threshold` | How many points a metric must move to count. Default: `5.0`. | | `output` | How to deliver the result: text (default), page (one interactive HTML page, an artifact where the client supports one), pdf, slides, csv or json. | Used in: [Competitor radar](https://docs.oppin.ai/mcp/use-cases/competition.md#competitor-radar). ## Prompt audit `oppin_prompt_audit`: Grade the tracked prompt set on coverage, balance and bias. | Argument | What it does | | :- | :- | | `brand` | Brand name or id. Optional with a single brand. | | `output` | How to deliver the result: text (default), page (one interactive HTML page, an artifact where the client supports one), pdf, slides, csv or json. | Used in: [Prompt set health check](https://docs.oppin.ai/mcp/use-cases/tracking.md#prompt-set-health-check). ## Source authority `oppin_source_authority`: Audit how the brand's own domain performs as a source, and which third-party pages carry it. | Argument | What it does | | :- | :- | | `brand` | Brand name or id. Optional with a single brand. | | `period` | The period: 7d, 30d, 3m, 1y or custom:YYYY-MM-DD:YYYY-MM-DD. Default: `30d`. | | `output` | How to deliver the result: text (default), page (one interactive HTML page, an artifact where the client supports one), pdf, slides, csv or json. | ## Opportunity briefing `oppin_opportunity_briefing`: Turn Oppin's generated recommendations into a prioritised plan with the evidence attached. | Argument | What it does | | :- | :- | | `brand` | Brand name or id. Optional with a single brand. | | `output` | How to deliver the result: text (default), page (one interactive HTML page, an artifact where the client supports one), pdf, slides, csv or json. | Used in: [Recommendation triage](https://docs.oppin.ai/mcp/use-cases/tracking.md#recommendation-triage). ## Campaign impact `oppin_campaign_impact`: Before and after a campaign or launch: what moved in AI answers, where, and which sources carried it. | Argument | What it does | | :- | :- | | `start` | First day of the campaign or launch, YYYY-MM-DD. Required. | | `end` | Last day to measure, YYYY-MM-DD. Default: today. | | `brand` | Brand name or id. Optional with a single brand. | | `topic` | Optional: the topic the campaign targets, to focus on. | | `output` | How to deliver the result: text (default), page (one interactive HTML page, an artifact where the client supports one), pdf, slides, csv or json. | Used in: [Campaign or launch impact](https://docs.oppin.ai/mcp/use-cases/pulse.md#campaign-or-launch-impact). ## Topic heatmap `oppin_topic_heatmap`: Topic by brand heatmap: which topics the brand owns, which it loses, and to whom. | Argument | What it does | | :- | :- | | `brand` | Brand name or id. Optional with a single brand. | | `period` | The period: 7d, 30d, 3m, 1y or custom:YYYY-MM-DD:YYYY-MM-DD. Default: `30d`. | | `output` | How to deliver the result: text (default), page (one interactive HTML page, an artifact where the client supports one), pdf, slides, csv or json. | Used in: [Topic heatmap](https://docs.oppin.ai/mcp/use-cases/competition.md#topic-heatmap). ## Content brief `oppin_content_brief`: A content brief for one question the brand is losing, built from the pages AI reads and its fan-out queries. | Argument | What it does | | :- | :- | | `question` | The tracked question to write for, in its own words. Default: the one with the widest competitor gap. | | `brand` | Brand name or id. Optional with a single brand. | | `topic` | Optional: only consider questions in this topic. | | `period` | 7d, 30d, 3m, 1y, or custom:YYYY-MM-DD:YYYY-MM-DD (both days inclusive, UTC). Default: `30d`. | | `output` | How to deliver the result: text (default), page (one interactive HTML page, an artifact where the client supports one), pdf, slides, csv or json. | Used in: [Content brief from a gap](https://docs.oppin.ai/mcp/use-cases/content.md#content-brief-from-a-gap). ## Double down `oppin_double_down`: Find what already drives the brand's AI visibility, then suggest content that extends it into nearby weak spots. | Argument | What it does | | :- | :- | | `brand` | Brand name or id. Optional with a single brand. | | `period` | 7d, 30d, 3m, 1y, or custom:YYYY-MM-DD:YYYY-MM-DD (both days inclusive, UTC). Default: `30d`. | | `output` | How to deliver the result: text (default), page (one interactive HTML page, an artifact where the client supports one), pdf, slides, csv or json. | Used in: [Double down on what works](https://docs.oppin.ai/mcp/use-cases/content.md#double-down-on-what-works). ## Brand audit `oppin_brand_audit`: A complete AI brand audit: how AI discovers, describes and recommends the brand, and what it relies on. | Argument | What it does | | :- | :- | | `brand` | Brand name or id. Optional with a single brand. | | `period` | 7d, 30d, 3m, 1y, or custom:YYYY-MM-DD:YYYY-MM-DD (both days inclusive, UTC). Default: `3m`. | | `output` | How to deliver the result: text (default), page (one interactive HTML page, an artifact where the client supports one), pdf, slides, csv or json. | Used in: [AI brand audit](https://docs.oppin.ai/mcp/use-cases/reporting.md#ai-brand-audit). ## Investigate drop `oppin_investigate_drop`: Incident-style investigation of a visibility drop: when, where, who gained, and what changed in the sources. | Argument | What it does | | :- | :- | | `brand` | Brand name or id. Optional with a single brand. | | `period` | 7d, 30d, 3m, 1y, or custom:YYYY-MM-DD:YYYY-MM-DD (both days inclusive, UTC). Default: `30d`. | | `output` | How to deliver the result: text (default), page (one interactive HTML page, an artifact where the client supports one), pdf, slides, csv or json. | Used in: [Visibility drop investigation](https://docs.oppin.ai/mcp/use-cases/pulse.md#visibility-drop-investigation). ## Client report `oppin_client_report`: A plain-language report ready to send to a client or stakeholders, with the previous period alongside. | Argument | What it does | | :- | :- | | `brand` | Brand name or id. Optional with a single brand. | | `period` | 7d, 30d, 3m, 1y, or custom:YYYY-MM-DD:YYYY-MM-DD (both days inclusive, UTC). Default: `30d`. | | `output` | How to deliver the result: text (default), page (one interactive HTML page, an artifact where the client supports one), pdf, slides, csv or json. | Used in: [Monthly or client report](https://docs.oppin.ai/mcp/use-cases/reporting.md#monthly-or-client-report). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.