Claude Skill

@gary-club/agency

The “AI Agency of 1” skill. Install once and Claude becomes your AAU operator — CRM, SMS, calls, KB, brief and ask, all from natural language.

What it does#

The skill bundles a curated set of named workflows on top of our MCP server. Claude follows the playbook, confirms before destructive actions (sending SMS, initiating calls, deleting), and tells you exactly which tool it's about to call.

Install — Claude Desktop#

Open ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) or the equivalent on your platform. Add a mcpServers entry pointing at our remote MCP:

claude_desktop_config.json

{
  "mcpServers": {
    "gary-club": {
      "url": "https://agency.gary.club/api/public/v1/mcp",
      "headers": {
        "Authorization": "Bearer gc_live_EXAMPLE_AbCdEfGhIj0123456789"
      }
    }
  }
}

Restart Claude Desktop. The tools appear automatically. Ask “triage today” or “brief me on Jane Doe” and Claude executes the matching workflow.

Install — Claude Code#

Two parts: clone the skill files into ~/.claude/skills/, and add the MCP server to your settings.

Skill files

git clone https://github.com/garylhenderson/gary-club-claude-skill \
  ~/.claude/skills/gary-club

~/.claude/settings.json (add to mcpServers)

{
  "mcpServers": {
    "gary-club": {
      "url": "https://agency.gary.club/api/public/v1/mcp",
      "headers": {
        "Authorization": "Bearer gc_live_EXAMPLE_AbCdEfGhIj0123456789"
      }
    }
  }
}

The 1-click button

On agency.gary.club → Settings → API Keys, click Install Claude Skill. It mints a purpose-tagged key, hands you the JSON snippet, and walks you through each Claude product. No manual curl-piping.

The twelve workflows#

Each workflow has a defined tool sequence, confirmation rules, and rollback behaviour. Trigger by name (“daily triage”) or describe the goal — Claude matches.

Daily triage

Pull last 24h inbound calls, SMS, leads. Summarize, queue follow-ups.

Pre-call brief

CRM history + AI gist for an upcoming meeting in one prompt.

Outbound campaign

List-driven dialing with a custom prompt (Phase 1.5).

Pipeline review

Walk every deal in a stage, flag stalls, suggest moves.

Post-call ingest

Turn a transcript into CRM updates and tasks.

SMS reply autopilot

Draft replies to inbound SMS; ask before sending.

Lead enrichment batch

Fill missing contact fields (Phase 2).

KB Q&A

Answer questions using the agency's knowledge base.

EOD report

What happened today across calls, SMS, deals, FUEL.

Sequence health check

Enrolled vs replied vs paused vs dead.

New-client onboarding

Pipeline + welcome sequence for a brand-new client.

Spend alerts

When FUEL drops below threshold, surface the biggest burners.

Customising#

Fork the skill repo to layer your own playbook on top. Common customisations:

Add company-specific workflows in references/workflows.md.
Tighten destructive-action confirmation rules in SKILL.md.
Add custom-field semantics to references/data-model.md.

Repo: github.com/garylhenderson/gary-club-claude-skill.

A note on keys#

The MCP config carries your bearer key in plaintext on disk. Best practice:

Mint a key dedicated to the skill (the install button auto-tags it with claude_skill for easy audit).
One key, full access. Our keys are full-access by design — the single decision is agency-wide vs. per-client. Use a per-client cl_live_… key to confine a Claude installation to one customer's data.
Rotate from the dashboard if the machine is shared or lost; the key's revocation propagates within seconds.