> ## 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 so Claude Code, Codex, and other skill-aware agents can set up brands, prompt libraries, citation segments, and dashboards.
[Agent Skills](https://agentskills.io) are installable packages that give AI coding agents specialized knowledge about Scrunch. Once installed, your agent can set up a brand end to end, build its non-branded prompt library, configure citation segments, migrate an existing setup over from wherever you're tracking this today, and generate a Scrunch-branded visibility dashboard — all through natural conversation, with the [Scrunch MCP](/mcp/setup) doing the actual work.
## Get your agent up to speed
Copy the prompt below into Claude Code, Claude Cowork, Codex, or any other Agent Skills-aware client to install every Scrunch Skill and have your agent summarize what it can now do:
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.
## Installation
To install all available Skills:
```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). Mintlify auto-publishes every Skill below at `/.well-known/skills/index.json`, which is what the command above reads from.
Every Skill assumes the Scrunch MCP server is already connected — see the [setup guide](/mcp/setup) if it isn't yet. There's no separate flag to install just one Skill from a URL source like this one (unlike a GitHub-hosted skills repo) — `npx skills add` installs all of them together.
## Available skills
| 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 |
## Example prompts
Once Skills are installed, you can ask your AI agent:
| 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` |
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.
The copy-paste version of this same expertise, for any AI chat — no Skill installation needed.
Every Scrunch MCP tool these Skills call, with descriptions and example prompts.