> ## Documentation Index
> Fetch the complete documentation index at: https://developers.scrunch.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Scrunch Agent Skills

> Install Scrunch's Agent Skills — MCP-based or REST-only — for brand setup, prompt libraries, dashboards, page audits, and more.

[Agent Skills](https://agentskills.io) are installable packages that teach your AI agent how to work with Scrunch. Once installed, it can set up a brand end to end, build a prompt library, configure citation segments, run page audits, migrate an existing setup, and generate a branded visibility dashboard, all through conversation.

## Get your agent up to speed

Copy this prompt into Claude Code, Claude Cowork, Codex, or any Agent Skills-aware client. It installs every Scrunch Skill and has your agent summarize what it can now do:

<Prompt description="Install Scrunch's Agent Skills into your agent." actions={["copy"]}>
  Install the `skill.md` files from the Mintlify-hosted Scrunch documentation site into my agent context so you know what this product can do.

  1. Run `npx skills add https://developers.scrunch.com`

  2. Print the list of skills that were installed, including each skill's name and description.

  3. Summarize the key capabilities in one paragraph so I know what you can now help me accomplish with this product.

  4. If any skill declares required inputs or constraints in its frontmatter, call them out before I ask you to use it.
</Prompt>

## Installation

To install all available Skills yourself:

```bash theme={null}
npx skills add https://developers.scrunch.com
```

Works with Claude Code, Claude Cowork, Cursor, Windsurf, GitHub Copilot, Codex, Gemini CLI, and more. See [all supported agents](https://github.com/vercel-labs/skills?tab=readme-ov-file#supported-agents).

Two families install together as one package, and your agent picks the right one. It uses `scrunch-*` whenever the Scrunch MCP server is connected and falls back to `api-*` when it isn't.

<Note>
  `scrunch-*` Skills need the Scrunch MCP server connected. See the [setup guide](/mcp/setup). `api-*` Skills need a Scrunch API key set as `SCRUNCH_API_TOKEN`. See [API authentication](/api-reference/introduction). You can't install just one family, but each Skill checks for its own prerequisite before running.
</Note>

## Available skills

<Tabs>
  <Tab title="MCP-based">
    The default when the Scrunch MCP server is connected, with the full product surface: sub-brands, citation segments, geo and industry targeting, bulk operations. No API key needed.

    | Skill | Description | When to use |
    | - | - | - |
    | `scrunch-brand-setup` | Brand record, competitors, sub-brands and sub-competitors, personas — generated from just a domain | Setting up a brand that doesn't exist in Scrunch yet, or reviewing an existing one against best practices |
    | `scrunch-migrate-setup` | Exports a setup from wherever you currently track this, maps it into Scrunch's structure, and reconciles it against your plan limits before creating anything | Only when you're already using a comparable tool and want to bring that setup over — not for a brand-new setup |
    | `scrunch-citation-segments` | Groups cited domains into named tiers — Socials, Publications, Marketplaces, Reviews | After a brand exists — proposes sensible defaults automatically, no URL list required |
    | `scrunch-prompt-setup` | The actual prompt library — funnel stages, tags, topics, geo-specific coverage, AI platform selection | Building or auditing what Scrunch tracks, or answering "how is my brand doing in AI search" |
    | `scrunch-visibility-dashboard` | A repeatable, Scrunch-branded visibility dashboard (presence, citations, sentiment, weakest prompts, agent traffic) as an artifact or HTML file — not an Explorer link | Sharing a visual summary of a brand's AI visibility, e.g. for a QBR or stakeholder update |
    | `scrunch-visual-style` | Scrunch's actual typography and color system (Inter, IBM Plex Mono, the Neutrals/Greens/Blues palette) — and the rule against color-coded status badges | Applied by default to any deliverable built from Scrunch MCP data, unless you've specified your own visual style or asked not to use it |
  </Tab>

  <Tab title="REST-only">
    For agents, scripts, and CI pipelines calling the REST API directly with a `SCRUNCH_API_TOKEN`. A smaller surface than MCP, and each Skill says plainly what it can't do.

    | Skill | Description | When to use |
    | - | - | - |
    | `api-brand-setup` | Brand record, competitors, and personas via the Configuration API | Setting up or updating a brand when MCP isn't connected — CI, a backend script, an agency onboarding tool |
    | `api-prompt-setup` | Adding prompts via the Configuration API | Building a prompt library when MCP isn't connected |
    | `api-page-audit` | Queues and retrieves AI-search-readiness audits for specific URLs | Checking how AI crawlers see a page — no MCP equivalent exists for this today |
    | `api-get-started` | Orchestrates brand setup, prompt setup, and page audits into one flow | "Let's get started in Scrunch" / "set me up in Scrunch" when MCP isn't connected |
    | `api-dashboard-builder` | The same repeatable visibility dashboard, built entirely from REST API calls | Sharing a visual AI-visibility summary when MCP isn't connected |
    | `api-sitemap-export` | Page inventory, audit scores, and CSV/XLSX export of the crawled sitemap | Content inventory and per-page metrics — no MCP equivalent exists for this today |
    | `api-query-metrics` | Ad hoc, custom metric queries via the structured Query API | Custom reporting that goes beyond the standard dashboard shape |
    | `api-responses-export` | Raw AI response text and citations, for ETL pipelines | Bulk export or audit of what AI platforms actually said |
    | `api-signals-monitoring` | Reads Scrunch's nightly detected-change feed | Feeding a custom alert channel or weekly digest |
    | `api-agent-traffic-connect` | Optional — pushes custom AI-crawler traffic data | Seeing which AI agents visit your pages, without a native CDN integration |
    | `api-ai-referrals` | Optional — pushes Adobe Analytics-style AI referral data | Powering the AI Traffic dashboard for brands not using Google Analytics 4 |
  </Tab>
</Tabs>

## Example prompts

Once Skills are installed, ask your agent in plain language:

<Tabs>
  <Tab title="MCP">
    | You say | Skill used |
    | - | - |
    | "Set up a Scrunch brand for smithoptics.com" | `scrunch-brand-setup` |
    | "Set up my brand in Scrunch — here's my website" | `scrunch-brand-setup` |
    | "We're switching from our current AI-visibility tool" | `scrunch-migrate-setup` |
    | "Import my brand and prompts from \[another tool]" | `scrunch-migrate-setup` |
    | "Set up citation segments for \[brand]" | `scrunch-citation-segments` |
    | "Segment these publications for \[brand]" | `scrunch-citation-segments` |
    | "Build our prompt library" / "Are we showing up in AI search" | `scrunch-prompt-setup` |
    | "Which AI platforms should we track" | `scrunch-prompt-setup` |
    | "Add prompts for our \[city] location" | `scrunch-prompt-setup` |
    | "Build a visibility dashboard for \[brand]" | `scrunch-visibility-dashboard` |
    | "Make an HTML citation dashboard I can share" | `scrunch-visibility-dashboard` |
    | "Make this on-brand for Scrunch" / "Use Scrunch's colors" | `scrunch-visual-style` |
  </Tab>

  <Tab title="REST API">
    | You say | Skill used |
    | - | - |
    | "Set up a Scrunch brand for smithoptics.com" | `api-brand-setup` |
    | "Build our prompt library" | `api-prompt-setup` |
    | "Build a visibility dashboard for \[brand]" | `api-dashboard-builder` |
    | "Run a page audit on our pricing page" | `api-page-audit` — no MCP equivalent |
    | "Export our sitemap to a spreadsheet" | `api-sitemap-export` — no MCP equivalent |
    | "Let's get started in Scrunch" | `api-get-started` |
  </Tab>
</Tabs>

<Warning>
  Skill discovery depends on your client. Claude Code and Claude Cowork read installed skills automatically once added; some clients need the skill named explicitly the first time ("use the scrunch-brand-setup skill to..."). If nothing triggers, re-run `npx skills add https://developers.scrunch.com` — every Skill is plain markdown, so it's cheap to retry.
</Warning>

<CardGroup cols={2}>
  <Card title="Feature Reference" icon="wrench" href="/mcp/tools">
    Every Scrunch MCP tool the `scrunch-*` Skills call, with descriptions and example prompts.
  </Card>

  <Card title="API Reference" icon="plug-circle-bolt" href="/api-reference/introduction">
    The REST API the `api-*` Skills call directly, including authentication and scopes.
  </Card>
</CardGroup>


## Related topics

- [Connect your AI tool to the Scrunch MCP](/mcp/setup.md)
- [Connect Your CDN to Scrunch Agent Traffic](/integrations/agent-traffic.md)
- [Agent Traffic to a Spreadsheet Dashboard](/mcp/workflows/agent-traffic-to-spreadsheet.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.