GrowthOS agent kit

Operating instructions for an AI agent working with a GrowthOS workspace over MCP. Install it in Claude Code or Cursor and your agent resolves the workspace before answering, reads complete data instead of the first page of it, and previews every change before applying it.

This repository is the skill: SKILL.md plus the references/ folder it reads on demand.

The kit does not grant access. Your MCP connection decides which workspaces the agent can reach and whether it can write. A read-only connection stays read-only after installing this.

Install

You need a working GrowthOS MCP connection first — see 2.3 · Connect your agent via MCP.

Claude Code

mkdir -p ~/.claude/skills
git clone https://github.com/growthxai/growthos-agent-kit.git ~/.claude/skills/use-growthos

Cursor, all projects

mkdir -p ~/.cursor/skills
git clone https://github.com/growthxai/growthos-agent-kit.git ~/.cursor/skills/use-growthos

Cursor, one project only — run from that project's root:

mkdir -p .cursor/skills
git clone https://github.com/growthxai/growthos-agent-kit.git .cursor/skills/use-growthos

The clone target folder must be named use-growthos — it has to match the name in SKILL.md.

Restart Cursor and start a new chat before using the kit. Claude Code picks up new skills during an open session, unless the install just created ~/.claude/skills for the first time — then start a fresh session.

Update

git -C ~/.claude/skills/use-growthos pull

Swap the path for whichever install you used.

Remove

rm -rf ~/.claude/skills/use-growthos   # Claude Code
rm -rf ~/.cursor/skills/use-growthos   # Cursor, all projects
rm -rf .cursor/skills/use-growthos     # Cursor, this project folder

Removing the kit is not a disconnect — your agent keeps its GrowthOS access and loses these operating instructions from the next session on.

Check it works

Run one read-only prompt. It touches nothing:

Using GrowthOS, tell me which workspaces you can see, then give me a portfolio check-in for mine: how traffic moved against the previous period, which pages lost momentum, and the 3 actions you'd take first. Say which workspace and date range you used.

Your agent should name the workspace before answering, or ask which one when several match, and close with the workspace and period behind the numbers. Both behaviors come from the kit.

Docs

• 8.3 · Install the GrowthOS agent kit — install, verification prompts, troubleshooting
• 8.1 · What to do with MCP today — the prompts worth running first
• 8.2 · Give your agent write access — the write opt-in
• MCP server reference — scope, permissions, disconnecting

Contents

Path	What it is
SKILL.md	The operating instructions your agent loads
references/growthos-mcp-reference.md	Concept map, tool routing, recipes, and troubleshooting, on demand

Feedback

Open an issue here, or tell your GrowthX contact.