Skip to content

Capabilities

This is the menu. Each capability is one thing James (or Claude acting on his behalf) can do inside this environment — a concrete, invokable action with a clear input, a clear output, and a clear implementation somewhere under ~/apps/.

The capabilities registry is also maintained as a machine-readable table at ~/apps/cc/memory/capabilities.md. This wiki is the human-readable, “how does this thing actually work” version — one page per capability, written for a future-James who forgot how it all fits together.

Every capability page follows the same structure:

  • What it does — one sentence, no jargon
  • When to use — the trigger, the situation, the “why would I run this”
  • How to invoke — the actual command or slash command
  • Prerequisites — credentials, connectors, other capabilities it depends on
  • Where it lives — repo, file path, and any supporting services
  • Example session — a realistic walkthrough of what happens when you run it
  • Known gaps / TODOs — what does not work yet, or what should be better
  • GSC Audit — multi-site Search Console health audit with historical benchmarking
  • Create a Blog Post — transform any raw content into a polished TMS blog post
  • GKP Facebook Ads — (gap) pull Go Kart Park ad performance
  • Send a Gmail — send an HTML or plaintext email via the Gmail API

Everything in ~/apps/cc/memory/capabilities.md that is not yet on a page here. Candidates by category:

  • Send — SMS via GHL, iMessage, ATH weekly analytics email
  • Post / Publish — Google Business Profile, YouTube metadata update, set YouTube public
  • Read / Fetch — Calendar events, CRM contacts, CRM conversations, GSC performance, GA4 traffic, MTS logs
  • Update / Write — macOS text replacements, GHL contact fields, GHL pipeline stages, Cloudflare DNS
  • Generate / Create — Social media comment ladder, Upwork proposals, episode checklist
  • Analyze — CRM journey, infrastructure health checks, voice AI call quality
  • Deploy — ATH website, TMS website, VPS services, static apps to VPS
  1. If it is not documented here, Claude should ask where it lives before running it. This page is the source of truth.
  2. If a capability has a skill (slash command), it gets a page here. Skills are in ~/.claude/commands/.
  3. If a capability is a one-liner script, it still gets a page here. Small does not mean undocumented.
  4. Known gaps belong at the bottom of the page, not buried in prose. The gap list is a TODO list for James.