This skill should be used when the user says setup, check my setup, verify config, is everything configured, or wants to confirm their development environment is ready. It verifies that environment variables, MCP servers, and related tools are configured correctly.
From hugin-coworknpx claudepluginhub michelve/hugin-marketplace --plugin hugin-coworkThis skill uses the workspace's default tool permissions.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Guides agent creation for Claude Code plugins with file templates, frontmatter specs (name, description, model), triggering examples, system prompts, and best practices.
Run each of the following checks and report a summary table at the end.
If the user provided arguments (e.g. /setup FIGMA_API_KEY=fig_xxx), parse them first:
FIGMA_API_KEY=<value>: Persist the key for the current and future sessions:
export FIGMA_API_KEY=<value> in the current shellFIGMA_API_KEY is already in ~/.zshrc (or ~/.bashrc):
export FIGMA_API_KEY=<value>If no arguments are provided, proceed normally and prompt for missing required values at the end.
Check whether each variable is set (non-empty) in the current shell environment:
| Variable | Required | Used by |
|---|---|---|
FIGMA_API_KEY | Yes | figma, figma-console MCP servers |
For each variable, report ✅ Set or ❌ Missing.
If any required variable is missing, show the setup command for the user's OS:
export FIGMA_API_KEY=fig_xxxxxxxxxxxxxxxxxxxxx (add to ~/.zshrc or ~/.bashrc)Check if typescript-language-server is available on $PATH by running:
which typescript-language-server
Report ✅ Installed or ❌ Missing. If missing, show:
npm install -g typescript-language-server typescript
Check if the figma-console-mcp package is installed globally:
npm list -g figma-console-mcp 2>/dev/null
If not installed, install it:
npm install -g figma-console-mcp
Report ✅ Installed or ⚠️ Missing (and auto-install if missing).
Read .mcp.json at the project root and verify each server:
| Server | Type | Check |
|---|---|---|
| context7 | npx | npx -y @upstash/context7-mcp --help resolves |
| playwright | npx | npx -y @playwright/mcp --help resolves |
| figma | npx + env | Package resolves AND $FIGMA_API_KEY is set |
| figma-console | npx + env | Package resolves AND $FIGMA_API_KEY is set |
| sequential-thinking | npx | npx -y @anthropic/sequential-thinking-mcp --help resolves |
| miro-mcp | URL (SSE) | URL https://mcp.miro.com/sse is configured |
| shadcn | npx | npx -y shadcn@latest mcp --help resolves |
For servers marked as needing env vars, cross-reference with section 1 results.
If any server is missing from .mcp.json, offer to add it.
Report each server as ✅ Configured or ⚠️ Needs attention.
Print a single summary table:
┌───────────────────────────┬────────┐
│ Check │ Status │
├───────────────────────────┼────────┤
│ FIGMA_API_KEY │ ✅/❌ │
│ TypeScript LSP │ ✅/❌ │
│ figma-console-mcp (npm) │ ✅/⚠️ │
│ context7 MCP │ ✅/⚠️ │
│ playwright MCP │ ✅/⚠️ │
│ figma MCP │ ✅/⚠️ │
│ figma-console MCP │ ✅/⚠️ │
│ sequential-thinking MCP │ ✅/⚠️ │
│ miro-mcp MCP │ ✅/⚠️ │
│ shadcn MCP │ ✅/⚠️ │
└───────────────────────────┴────────┘
If any checks failed, offer to fix them automatically:
FIGMA_API_KEY: Ask the user for their key, then set it (export + append to shell profile)npm install -g typescript-language-server typescriptfigma-console-mcp: Run npm install -g figma-console-mcp/setup again after fixing network/npm issuesOnly proceed with auto-fixes if the user confirms.