peec-ai-skills

Peec AI Skills for Claude Code

Production-tested Claude Code skills for Peec AI — the brand-visibility tracking platform for LLM-powered search (ChatGPT, Perplexity, Google AI Overviews, Gemini).

These skills turn a freshly-invoked Peec AI project into an operator-ready setup with the right competitors, the right prompts, a proper customer-journey taxonomy, and an actionable content pipeline — using the Peec AI MCP server, Visibly AI (GSC/GA4), and web research.

Quick install (60 seconds)

# 1. Clone + install all 9 skills into ~/.claude/skills/
git clone https://github.com/AntonioBlago/peec-ai-skills.git ~/peec-ai-skills
cd ~/peec-ai-skills
./claude-peec-ai.sh                 # use --copy on Windows without dev mode

# 2. Connect the Peec AI MCP (OAuth in browser on first tool call)
claude mcp add peec-ai --transport streamable-http https://api.peec.ai/mcp

# 3. Restart Claude Code, then in any directory:
#    /peec-start    →  detects state, dispatches the right skill

That's it. /peec-start reads growth_loop/setup_state.json if present, otherwise probes Peec live and either offers brownfield import or runs greenfield setup. Optional MCPs (Visibly AI, SkillMind) are documented under Prerequisites.

📑 5-minute overview: docs/presentation/peec-ai-skills-deck.pdf — 20-slide pitch + tutorial.

Skill system (8 skills + 1 orchestrator + 1 entry point)

Not a feature list — a closed growth loop with a cross-project memory layer underneath. Every skill has a specific job; the orchestrator (peec-agent) decides which one runs next; peec-learn lifts lessons out of one project into priors for the next.

     ┌────────────────────────────────────────────────────────┐
     │                                                        │
     │   ENTER               peec-start  (manual entry)      │
     │                       hooks/peec-detect.py (auto)      │
     │                                    ↓                   │
     │   UNDERSTAND          peec-setup              │
     │   (prompts,           peec-content-intel (demand)      │
     │    demand,                         ↓                   │
     │    taxonomy)                                           │
     │                                                        │
     │   DIAGNOSE            peec-checkup                     │
     │   (read-only          (setup health + brand snapshot   │
     │    health pass)        + ranked improvements)          │
     │                                    ↓                   │
     │   ANALYZE             peec-cluster          │
     │   (strategic          peec-content-intel (sources)     │
     │    zones)                          ↓                   │
     │                                                        │
     │   DECIDE    ◄──────── peec-agent (orchestrator)   │
     │   (one move)          calls /peec-checkup first        │
     │                                    ↓                   │
     │                                                        │
     │   EXECUTE             @content-write (Visibly skill)   │
     │   (build +            peec-outreach                │
     │    distribute)                     ↓                   │
     │                                                        │
     │   LEARN               peec-report             │
     │   (attribution,                    ↓                   │
     │    next moves)                                         │
     │                                                        │
     └────────→ feeds back into UNDERSTAND ───────────────────┘
                             │
                             ▼
     ┌────────────────────────────────────────────────────────┐
     │  CROSS-PROJECT MEMORY     peec-learn            │
     │  (patterns, priors)       read: priors for next loop   │
     │                           write: patterns after lift   │
     └────────────────────────────────────────────────────────┘

All skills are user-invocable — Claude Code triggers them automatically when the conversation matches, and users can invoke them explicitly with /peec-start, /peec-setup, /peec-checkup, /peec-content-intel, /peec-cluster, /peec-outreach, /peec-report, /peec-learn, or /peec-agent.

Prerequisites

Required:

• Claude Code (CLI, VS Code extension, or JetBrains plugin)
• Peec AI MCP server connected (provides mcp__peec-ai__* tools — see below)

Peec AI — hosted MCP (OAuth, zero install)

Peec AI ships a remote MCP server at https://api.peec.ai/mcp with OAuth — no API key file, just a browser redirect on first use.

claude mcp add peec-ai --transport streamable-http https://api.peec.ai/mcp

…or add it directly to your Claude Code settings.json / ~/.claude.json:

{
  "mcpServers": {
    "peec-ai": {
      "type": "http",
      "url": "https://api.peec.ai/mcp"
    }
  }
}

The first time any skill calls a mcp__peec-ai__* tool, Claude Code opens a browser to sign you in to Peec AI and authorize access. Tokens persist; subsequent runs are silent. Full docs: docs.peec.ai/mcp/setup.

Optional but strongly recommended:

Visibly AI — hosted MCP (zero install)

Visibly AI is a remote MCP server — no pip install required. Just add the connection to your Claude Code settings.json:

{
  "mcpServers": {
    "visiblyai": {
      "type": "http",
      "url": "https://mcp.visibly-ai.com/mcp",
      "headers": {
        "Authorization": "Bearer lc_your_key"
      }
    }
  }
}

Get your API key under Account → API Keys. Without the Authorization header, only the 8 free tools are available. Full developer docs: antonioblago.com/de/entwickler/mcp.

Provides: GSC / GA4 read-through, backlinks, onpage analysis, classify_keywords, and — since v0.6.0 — the query_fanout coverage analyzer.

SkillMind — local MCP (pip install)

SkillMind is a local MCP server that provides the cross-project memory layer used by peec-learn. Install:

pip install "skillmind[pinecone,mcp,youtube]"
# or for everything:
pip install "skillmind[all]"

Then add to Claude Code settings.json:

{
  "mcpServers": {
    "skillmind": {
      "command": "python",
      "args": ["-m", "skillmind.mcp.server"],
      "env": {
        "PINECONE_API_KEY": "your-pinecone-key",
        "SKILLMIND_BACKEND": "pinecone",
        "ANTHROPIC_API_KEY": "your-anthropic-key"
      }
    }
  }
}

Credentials can also live in a .env file in your project root instead of the env block. Repo: github.com/AntonioBlago/skillmind.

How skills remember setup (setup_state.json)

Setup is expensive — discovering competitors from real AI chats, designing 20 funnel-spread prompts, building taxonomy. You don't want it re-run from scratch every time the orchestrator asks "what next?". So the skills share one state file:

<project>/growth_loop/setup_state.json

• peec-setup owns it: reads at Phase 0 to decide full | audit | partial | skip, writes at Phase 9 with merged phases + a fresh count snapshot + the resolved target_country / prompt_language.
• All other skills (peec-agent, peec-content-intel, peec-cluster, peec-outreach, peec-report) refuse to run without it. If the file is missing, they output one line:

  No Peec setup state found at <project>/growth_loop/setup_state.json. Run /peec-setup first.

This means: every consumer skill knows the project ID, the language to write briefs in, the country to filter SERPs by, and which forums to mine — without re-asking you and without silently defaulting to English. Setup older than 90 days triggers a warning; older than that without audit mode is a yellow flag in any output.

Schema and full read/write protocol: skills/_shared/SETUP_STATE.md.