Open-source agentic AI Search Execution Platform. Track AI visibility, find opportunities, and let agents turn signals into prioritized actions and drafted fixes across ChatGPT, Claude, Gemini, Google AI Overviews, Google AI Mode, Perplexity, Grok, and Microsoft Copilot.
Ansvisor Skills
A collection of opinionated Anthropic Skills that turn Claude into an AEO analyst with live access to your Ansvisor account.
Most skills come in two flavours: one that talks to the Ansvisor MCP server (cleaner UX in clients that support it) and one that calls the REST API directly with code execution (works anywhere). Pick the flavour that matches your Claude client — see the table below.
Without a skill, Claude can still hit our tools/API if you tell it how — it'll just answer generically. With one of these installed, it behaves like an AEO analyst who's been on your account for six months.
Skills in this repo
| Skill | Flavour | What it's for |
|---|---|---|
ansvisor-aeo-coach |
MCP (preferred) | Brand snapshots, visibility deep-dives, competitor watch, citation sources, prompt coverage and prompt suggestions, Action Center (what to do next, did it work, sending Improve suggestions), mentions and sentiment (how AI talks about the brand, why sentiment moved, what AI associates it with), Content Editor drafts (sources, suggestions for review, Mark ready, what the live page earns), saved reports. Use this when your client (Claude Desktop, Claude Code, Cursor, Zed) is connected to the Ansvisor MCP server. |
ansvisor-aeo-coach-standalone |
REST (fallback) | Same skill, no MCP needed. Use this when you're on claude.ai web without a Connector, or any surface where setting up MCP isn't an option. |
Which flavour should I install?
| Your client | Recommended |
|---|---|
| Claude Desktop | MCP — install the MCP server once, then ansvisor-aeo-coach |
| Claude Code | MCP — same as above |
| Cursor / Zed / other MCP-aware tools | MCP — it's their native primitive |
| claude.ai web with the Ansvisor Connector configured | MCP |
| claude.ai web without a Connector | Standalone — single install, no extra setup |
| Anywhere else with Skills + code execution | Standalone |
Both flavours hit the same data, format the same way, and share the
same references/ knowledge files. The difference is just how Claude
fetches numbers — typed tool calls vs. inline Python HTTP requests.
Prerequisites
You need an Ansvisor API key in either flavour:
- Open your Ansvisor dashboard → Settings → API Keys
- Click New key, give it a memorable name (e.g. Claude — laptop)
- Copy the token (
ans_...). It's shown once — store it in your password manager
If you self-host Ansvisor, both flavours work against your own instance — you'll just provide a different base URL when prompted (MCP: in your client config; standalone: when the skill asks).
Install
Skills are just markdown files — they work in any Claude surface that supports the Skills feature.
Claude.ai (web)
- Open https://claude.ai/skills
- Click New Skill → Paste from markdown
- Paste the contents of your chosen flavour's
SKILL.md - Save
The first time you use the MCP flavour, you also need the Ansvisor Connector added to your Claude.ai account (see the MCP guide). The standalone flavour will ask you for your API key in the conversation itself.
Claude Code / Claude Desktop
git clone https://github.com/ansvisor/ansvisor.git
cp -r ansvisor/skills/ansvisor-aeo-coach ~/.claude/skills/ # MCP flavour
# or
cp -r ansvisor/skills/ansvisor-aeo-coach-standalone ~/.claude/skills/
Restart your Claude client and the skill is live. If you chose the MCP flavour, also configure the Ansvisor MCP server in your client.
Use
Once installed, just ask in plain English:
- "How is my brand doing this week?"
- "Why did visibility drop on ChatGPT?"
- "Who are my biggest competitors right now?"
- "Which sites does AI cite instead of us?"
- "What should we work on next — and did last month's actions work?"
- "Give me a 30-second standup on the Acme brand."
- "Why did our sentiment drop on Gemini?"
- "What's waiting for review in the Content Editor?"
Claude picks the right tools / endpoints, fills in filters, interprets the numbers, and answers with action items. Tools that change your account (accepting a suggestion, updating a task, sending Improve suggestions to Action Center, running a page audit, correcting a response's sentiment, writing a draft or suggestions in the Content Editor, marking a draft ready) are only used when you ask for that specific change.
Contributing
Got an idea for another skill? Open a PR with a new folder under
skills/:
skills/
your-skill-name/
SKILL.md # frontmatter + body
references/ # optional supporting docs
A few principles we follow:
- Skills layer knowledge, not data. Data comes from the MCP server or the matching REST endpoint. A skill's job is to know when and how to use it.
- Be opinionated about output. Marketers don't want a CSV dump — they want a 3-line summary, a delta, and a suggested next step.
- Ship MCP and standalone flavours together when it makes sense. Users on different surfaces shouldn't have to fork the skill themselves.
- Handle errors gracefully. Missing tool / bad key / empty data → tell the user, don't fabricate.
- Don't echo API keys. In the standalone flavour, hold tokens in execution memory and redact them in any output.
See CONTRIBUTING.md for branch naming, commit conventions, and PR workflow.