This is the PMM Sherpa skill for Claude Code (the CLI and IDE extensions). Once installed, Claude Code auto-triggers Sherpa on PMM keywords and enforces Layer 4 voice across the session.
| File | Purpose |
|---|---|
SKILL.md |
The skill itself. Claude Code loads it from .claude/skills/pmm-sherpa/SKILL.md. |
README.md |
This file. |
- Claude Code v2.1.83 or newer (skills support required)
- The PMM Sherpa MCP server already added:
claude mcp add pmm-sherpa --transport http https://pmmsherpa.com/api/mcpOAuth flow opens on first call. Sign in with the same Google account as pmmsherpa.com.
mkdir -p .claude/skills
git clone https://github.com/boommark/pmmsherpa-mcp.git /tmp/pmm-sherpa-repo
cp -r /tmp/pmm-sherpa-repo/skills/claude-code .claude/skills/pmm-sherpa
rm -rf /tmp/pmm-sherpa-repoThe skill loads automatically on the next Claude Code session in that project.
Cleaner. The skill is available across every project.
git clone https://github.com/boommark/pmmsherpa-mcp.git ~/.pmm-sherpa
mkdir -p ~/.claude/skills
ln -s ~/.pmm-sherpa/skills/claude-code ~/.claude/skills/pmm-sherpaThis symlinks the skill into your global ~/.claude/skills/ directory. Updates land instantly when you git pull in ~/.pmm-sherpa.
In a Claude Code session, type:
> /mcp
You should see pmm-sherpa listed as a connected MCP server with four tools.
Then prompt:
> See pmmsherpa.com. Help me create a battlecard against its top competitor.
You should see:
Skill(pmm-sherpa)line in the outputCalling PMM Sherpa…tool call withmcp__pmm-sherpa__ask_sherpaormcp__pmm-sherpa__draft_artifact- A response in Layer 4 voice
cd ~/.pmm-sherpa && git pullThe symlink picks up changes immediately. Restart your Claude Code session if a session was already running.
The skill is a calling guide. It tells Claude Code:
- When to call Sherpa vs handle directly (file parsing, web fetch, image gen → Claude's native tools)
- Which of the four tools to pick by intent (
mcp__pmm-sherpa__ask_sherpa,draft_artifact,get_feedback,scope_pmm_research) - How to phase Sherpa across a Deep Research run (planning → search → synthesis)
- How to preserve project context when in a project with brand guidelines or ICP definitions
- Voice rules: never em-dashes, story before framework, single-question close, no consultant-speak, no naming corpus authors
In Claude Code, the tools are namespaced as mcp__pmm-sherpa__<tool>:
mcp__pmm-sherpa__ask_sherpamcp__pmm-sherpa__draft_artifactmcp__pmm-sherpa__get_feedbackmcp__pmm-sherpa__scope_pmm_research
The skill handles this transparently. You don't need to type the full namespace.