8.3 · Install the GrowthOS agent kit

Install the agent kit in Claude Code or Cursor to give your agent, an automated worker acting on your behalf, a consistent set of GrowthOS operating instructions. It tells the agent to name the workspace it is working in (the container holding everything GrowthOS knows and does for your brand), read complete data before answering, and preview each change before applying it. Installation takes about 5 minutes.

The connection and the kit do different jobs:

• Your MCP connection grants the access. It decides which workspaces your agent can reach and whether it can only read or also write.
• The kit teaches your agent how to use that access. It carries the habits: resolve the workspace first, page through long lists instead of reporting the first screen, read a document before rewriting it, show a preview and wait.

Those instructions apply across everything your agent reaches: pages and their audits, your context documents (what GrowthOS knows about your company), briefs (the plan for one page), and opportunities (proposed pages worth writing or rewriting).

Installing the kit does not change permissions. A read-only connection stays read-only. If you want your agent to make changes, use the separate opt-in in 8.2 · Give your agent write access.

Before you start

You need a working GrowthOS MCP connection in Claude Code or Cursor. Set it up in 2.3 · Connect your agent via MCP first, and confirm your agent already answers a workspace question. The kit assumes the connection works; it can't repair a broken one.

Get the kit

The kit lives in a public repository: github.com/growthxai/growthos-agent-kit. You install it by cloning that repository straight into your skills directory, which makes a later update one git pull rather than another download.

The repository holds SKILL.md and a references/ folder at its root, so the folder you clone into becomes the skill. Name that folder use-growthos exactly as written below; it has to match the skill name inside SKILL.md. You also need git installed. Run git --version to check.

Install in Claude Code

1. Clone it into your skills directory

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

Expected result: the terminal reports the clone, and ~/.claude/skills/use-growthos/SKILL.md now exists alongside ~/.claude/skills/use-growthos/references/growthos-mcp-reference.md.

2. Confirm the files landed

ls ~/.claude/skills/use-growthos

Expected result: README.md, SKILL.md, and references. If the command reports no such file, the clone didn't run: re-run it exactly as written. If git clone said the destination already exists, you have an earlier install in place; update it instead, per Update or remove the kit.

3. Reload if the skills directory is new

Claude Code detects skill changes during an open session when the top-level ~/.claude/skills directory already existed. If the install command created that directory for the first time, close Claude Code and start a fresh session.

Expected result: the kit is available for your next prompt. If the check below suggests otherwise, start a new session and run it again.

Install in Cursor

Clone the kit into Cursor's personal skills directory:

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

Expected result: ~/.cursor/skills/use-growthos/SKILL.md exists, and the kit is available in every project you open.

Then restart Cursor and start a new chat. Expected result: the kit is in scope for that chat.

Install for one project folder only

If you'd rather keep the kit inside a single project, run the same command from that project's root folder and target its local skills directory instead:

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

Expected result: the files land at .cursor/skills/use-growthos/SKILL.md and apply only when you have that folder open. Pick this when the instructions belong with one codebase, and pick the ~/.cursor install when you want the kit everywhere. A project install and a personal install can coexist. The clone carries its own .git folder, so it doesn't commit cleanly into your project's repository: have teammates run the same command, or add it as a submodule.

Check it works

Run one read-only prompt first. It touches nothing and tells you whether the kit is in play:

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.

Expected result: your agent names the workspace it chose before answering, or asks you which one when several match, and closes with the workspace and period behind the numbers. Both behaviors come from the kit. If the answer skips them, check the installation under Troubleshooting.

Using GrowthOS, read our current Company Overview, then draft the smallest useful update that reflects this note: [paste a sentence or two of real positioning]. Show me the preview of exactly what would change and stop there. Do not apply it.

Expected result: your agent reads the current document, returns a preview of the proposed replacement, and states that nothing changed. If it applies the edit without pausing, stop using write access and check the installation.

Update or remove the kit

To update, pull the latest commit into the install you used:

git -C ~/.claude/skills/use-growthos pull   # Claude Code
git -C ~/.cursor/skills/use-growthos pull   # Cursor, all projects
git -C .cursor/skills/use-growthos pull     # Cursor, this project folder

Expected result: git lists the changed files, or reports Already up to date. Claude Code detects the changed files during an open session. Restart Cursor before using the updated kit.

To remove, delete the folder for the install you used:

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

Expected result: your agent keeps its GrowthOS access and loses the operating instructions from the next session on. Removing the kit is not a disconnect. Ending the connection itself happens in your AI tool, covered in the MCP server reference.

Troubleshooting

Your agent ignores the kit

The file is in the wrong place, or the session predates it.

1. Run the ls check above and confirm the path ends in use-growthos/SKILL.md, with no extra folder in between.
2. Start a new session or chat, and in Cursor restart the app first.
3. Run the read-only check again and confirm the response names the workspace and date range.

Your agent can't reach GrowthOS

The GrowthOS connection is missing or unavailable. The kit tells an agent how to work with GrowthOS tools; it cannot create the connection. Work through 2.4 · Fix a broken MCP connection, which covers an expired sign-in, an unregistered server, and a session that started before the server was added.

The write step isn't available

Your agent reports it can read GrowthOS but has no tool for the change you asked for. Write tools appear only after you grant write access, per person and per area, and adding the grant takes a fresh sign-in to the connector. 8.2 · Give your agent write access has the grant screen and the per-area list. If the approval screen never offers write access, it isn't enabled for your workspace yet: ask your GrowthX team.

Where to go next