skills/workspace/SKILL.md
Show current Octave MCP server connection and status. Use when user says "which workspace", "show connection", "what server", or asks about Octave setup.
npx skillsauth add octavehq/lfgtm workspaceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Show which Octave MCP server is connected.
Find the Octave MCP server by looking at your available tools for ones like verify_connection, get_entity, list_all_entities.
Call verify_connection to confirm the API key is valid and to fetch the authoritative workspace/organization names. This is the canonical probe.
Show the server name and workspace info from the verify_connection response:
Current Octave Workspace
========================
MCP Server: <mcpServerName>
Workspace: <workspaceName> (<workspaceOId>)
Organization: <organizationSlug> (<organizationOId>)
No Octave MCP server detected.
Add one with: claude mcp add octave-<workspaceName> --transport http <url>
If verify_connection fails (invalid API key, network error): surface the error message and suggest re-running claude mcp add with a fresh API key.
If user asks to switch: Explain they need to configure a different MCP server in their Claude settings.
tools
Capture a brand's visual design system from its website and build a reusable component kit. Walks key pages on a domain (screenshots + HTML via the Octave scrape tool), derives design tokens (colors, type, spacing, radius, shadow), and produces a minimal component library (buttons, cards, headers, stats, tables, badges, hero, footer) as a self-contained HTML reference plus CSS tokens. Use when the user says "get brand components", "capture the brand", "build a component kit for <domain>", "make outputs look like <company>", or wants other skills to generate on-brand HTML for a target company.
tools
Define, run, and manage multi-step GTM workflows with human-in-the-loop execution. Use when user says "run a workflow", "show workflows", "create a workflow", "automate this process", or references workflow-based tasks.
development
Analyze won and lost deals for patterns, insights, and actionable learnings. Use when user says "win/loss analysis", "why did we lose", "deal patterns", "win themes", or asks about deal outcome trends. Do NOT use for visual HTML reports — use /octave:win-loss-report instead.
development
Generate visual win/loss analysis reports as self-contained HTML with CSS-based charts and data visualizations. Use when user says "win/loss report", "deal report", "visual analysis", or wants a formatted HTML version of deal outcome analysis. Do NOT use for text-based deal analysis — use /octave:wins-losses instead.