# Use Growthos > Work with a GrowthOS workspace through its connected MCP server. Use when someone asks about their GrowthOS pages, portfolio, context, briefs, opportunities, traffic, AI visibility, reports, or asks an agent to make a change in GrowthOS. Resolves the workspace first, discovers the tools available to the current account, reads complete data, and previews every write before applying it. - Skill: `growthxai/use-growthos` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add growthxai/use-growthos` - Raw SKILL.md: https://api.skillmd.com/api/skills/growthxai/use-growthos/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: growthxai (https://skillmd.com/u/growthxai) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/growthxai/use-growthos --- # Use GrowthOS GrowthOS gives agents access to a brand's live website portfolio, strategy, context, content production, and performance data through MCP. Use the connected GrowthOS tools. Do not look for a repository credential or invent a raw API fallback. Read [references/growthos-mcp-reference.md](references/growthos-mcp-reference.md) when you need the concept map, tool-routing guide, recipes, or troubleshooting steps. ## Start every task this way 1. Discover the connected MCP tools and identify GrowthOS by its tool names, such as `list_workspaces`, `search_pages`, and `show_page`. Connector names can differ between clients and sessions. 2. Read the schema for each tool before calling it. The current schema is the contract. 3. Call `list_workspaces` and resolve the workspace the user means. 4. If more than one workspace could match, ask which one before continuing. 5. Pass that workspace to every workspace-scoped call. Never mix pages, metrics, briefs, or context from different workspaces unless the user asks for a comparison. ## Route the request ### Pages and portfolio - Find a page by title or topic with `search_pages`. - Use `show_page` for identity, classification, scores, traffic, targets, and other page metadata. - Use `show_page_content` when you need the page's body copy. - Use the audit, keyword, traffic, similarity, linking, or cannibalization tools exposed by the current connection when the question calls for them. A title does not identify a page. Resolve it to a page id or exact URL path before calling detail tools. ### Context and writing Use the context tools for the company's foundation, products, audience, personas, competitors, market, and writing guidance. Read the current document before proposing an edit because document writes can replace the full document. ### Strategy and opportunities Use clusters, topics, buyer questions, and opportunities to answer what the brand should cover next. Keep these nouns separate: - A cluster is a strategic territory. - A topic is a subject inside or outside a cluster. - A buyer question is what the audience needs answered. - An opportunity is a proposed page or rewrite. ### Briefs and production Use brief tools for the plan, research, outline, article, coverage, review, and publishing state of a proposed page. Creating a record and starting generation are separate actions. Do not start an agent run unless the user asked for it. ### Analytics, visibility, and reports Choose the surface that matches the question: - Page traffic for one page - Site or zone summaries for a portfolio view - Search Console data for search performance - Analytics data for channel and referral questions - AI traffic and visibility segments for AI-answer performance - Reports for written deliverables Read each tool's field descriptions before comparing numbers. Similar-looking metrics can cover different channels, periods, or sources. ## Read complete data List tools can paginate. When the response includes a total count, limit, or offset: 1. Keep requesting pages until you have the complete result set. 2. Treat a response whose row count equals the limit as possibly truncated. 3. State any filter, date range, source, or workspace that shaped the answer. Do not report a workspace-wide count from the first page of results. ## Make writes safely GrowthOS write tools use a preview-and-confirm flow. 1. Read the current record first when changing existing content. 2. Call the write without confirmation to get a no-op preview. 3. Show the user what will change. 4. Apply the write only after the user approves it. 5. Repeat the call with confirmation enabled. 6. Verify that the response says the change was applied. 7. Read the record back when the applied response does not contain enough detail to verify the result. A response that asks for confirmation means nothing changed. Prefer reversible actions: - Archive instead of delete. - Detach or remove from a collection instead of deleting the underlying record. - Pause instead of stop or delete when work can resume later. Ask again before deletes, publishing, merges, stopping in-progress work, member changes, or taking over an editor lock. Never take an editor lock without the user accepting the risk of losing someone else's unsaved work. ## Tool availability The available tools reflect the current person's account, workspace role, and granted permissions. - Do not assume a tool exists because another user has it. - If a needed tool is absent, explain the missing capability. - If permissions changed recently, reconnect before diagnosing a broken tool. - Never hardcode a session-specific connector id. ## Good first prompts ### Portfolio check > Using GrowthOS, give me a portfolio check-in for my workspace. Compare the > current period with the previous one, find pages whose momentum declined, > and recommend the three actions I should take first. ### Page diagnosis > Using GrowthOS, diagnose `/example-page`. Pull its audits, traffic trend, and > search performance. Tell me the main bottleneck and the first change you > recommend. ### Safe context update > Using GrowthOS, compare this new positioning note with our current Company > Overview. Draft the smallest useful update and show me the preview. Do not > apply it yet. ## Report what the tools cannot prove A stored crawl, score, or report describes what GrowthOS last observed. It does not prove the live page still has the same content or status. Say when a result comes from stored workspace data. Verify the live asset in a separate call when the decision depends on its current state.