Menu
Check and set up base technical environment — Python, uv, .env, .mcp.json. Use when repo is freshly cloned or operator hits a missing-tool error.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Dashboard of current GTM state across all active modules. Use when user asks about status, progress, or what to do next.
Upgrade this GTM Context OS instance to the latest template developments. Fetches the latest template, reconciles what's new against THIS instance's structure, and applies approved changes on a review branch — pausing before anything destructive. Operator-initiated.
Guided first-use setup. Walk through filling context.md and ingesting the first sales call. Use when the repo is empty or context.md is unfilled.
Smoke test before merging dev to main. Bootstraps a clean worktree, runs evals, checks instruction consistency — all automated via sub-agents.
First thing to run. Checks repo state and recommends what to do next. Use when operator says 'what do I do', 'help me get started', 'where do I begin', or just seems lost.
Audit the health of THIS instance's lived-in state — structural completeness, evidence chains, index integrity, output hygiene, drift, and context.md consistency (conflicts + cached-vs-source drift). Reports findings and fixes safe drift; flags judgment calls. Runs inside Claude Code, no API key.
| name | setup-env |
| description | Check and set up base technical environment — Python, uv, .env, .mcp.json. Use when repo is freshly cloned or operator hits a missing-tool error. |
Check and bootstrap the base technical environment for this GTM system.
Run these checks silently, report results as a status table:
| Check | Command | What to look for |
|---|---|---|
| Python | python3 --version | 3.10+ |
| uv | uv --version | Any version |
| Homebrew (macOS) | which brew | Present if macOS |
| Node/npx | npx --version | Needed for MCP servers |
| .env | Check file exists | Has content beyond comments |
| .mcp.json | Check file exists | Has server configs |
| git | git --version | Should always exist |
Python (if missing):
brew install python@3.12sudo apt install python3.12 or equivalentuv (if missing):
curl -LsSf https://astral.sh/uv/install.sh | sh# /// script metadataNode/npx (if missing and MCP servers are wanted):
brew install nodecurl -fsSL https://fnm.vercel.app/install | bash && fnm install --ltsIf .env doesn't exist, create from .env.example:
cp .env.example .env
Tell the user: "Add your API keys to .env as you connect tools. Use /setup-api to set up specific integrations."
If .mcp.json doesn't exist and user is on Claude Code, create a starter:
{
"mcpServers": {}
}
Tell the user: "MCP servers will be added here as you connect tools via /setup-api."
Environment Status:
Python 3.12 ✓
uv 0.6.x ✓
npx ✓
.env ✓ (empty — add keys as you connect tools)
.mcp.json ✓ (no servers configured yet)
Ready to go. Use /setup-api to connect your CRM, call recorder, or other tools.