aiwg-mcp
Manage the AIWG MCP server — start it, configure clients, and maintain the registered server registry
What this skill does
# AIWG MCP Server You manage the AIWG MCP (Model Context Protocol) server — starting it, configuring clients, and maintaining the registered server registry. > **Note**: This skill manages AIWG's own MCP server. For platform-native MCP management, use the platform's built-in `/mcp` command instead. ## Triggers Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description): - "expose aiwg over mcp" → serve - "hook up claude desktop" → install claude - "register external server" → add - "what does aiwg mcp expose" → info - "which mcp servers are registered" → list ## Trigger Patterns Reference | Pattern | Example | Action | |---------|---------|--------| | Start server | "start the MCP server" | Run `aiwg mcp serve` | | Configure client | "configure MCP for Claude Desktop" | Run `aiwg mcp install claude` | | Add server | "add the filesystem MCP server" | Run `aiwg mcp add <ref>` | | Remove server | "remove the git MCP server" | Run `aiwg mcp remove git` | | List servers | "what MCP servers are registered?" | Run `aiwg mcp list` | | Capabilities | "what can the AIWG MCP server do?" | Run `aiwg mcp info` | ## Behavior When triggered: 1. **Identify the subcommand**: - Is the user starting the server, configuring a client, or managing the registry? - Is a specific client or server reference mentioned? 2. **Run the appropriate command**: ```bash # Start the MCP server (foreground) aiwg mcp serve # Configure Claude Desktop aiwg mcp install claude # Configure another client aiwg mcp install <client> # Add an external MCP server to AIWG's registry aiwg mcp add <mcp-server-ref> # Remove a registered MCP server aiwg mcp remove <name> # List all registered MCP servers aiwg mcp list # Show AIWG MCP server capabilities aiwg mcp info ``` 3. **Report the result** — summarize what was configured or what the server exposes. ## Examples ### Example 1: Start the server **User**: "Start the MCP server" **Extraction**: Serve subcommand, no options **Action**: ```bash aiwg mcp serve ``` **Response**: "MCP server started. Listening on stdio. Exposes 50 tools mapped from AIWG CLI commands. Connect your MCP client to use AIWG capabilities." ### Example 2: Configure Claude Desktop **User**: "Configure MCP for Claude Desktop" **Extraction**: Install for claude client **Action**: ```bash aiwg mcp install claude ``` **Response**: "Claude Desktop configured. Added AIWG MCP server entry to ~/Library/Application Support/Claude/claude_desktop_config.json. Restart Claude Desktop to activate." ### Example 3: Add an external server **User**: "Add the filesystem MCP server from @modelcontextprotocol/server-filesystem" **Extraction**: Add subcommand, ref = @modelcontextprotocol/server-filesystem **Action**: ```bash aiwg mcp add @modelcontextprotocol/server-filesystem ``` **Response**: "Registered filesystem MCP server. It will be available as 'filesystem' in `aiwg mcp list`." ### Example 4: List registered servers **User**: "Which MCP servers are registered?" **Extraction**: List subcommand **Action**: ```bash aiwg mcp list ``` **Response**: "2 MCP servers registered: aiwg (built-in), filesystem (@modelcontextprotocol/server-filesystem)." ### Example 5: Show capabilities **User**: "What does the AIWG MCP server expose?" **Extraction**: Info subcommand **Action**: ```bash aiwg mcp info ``` **Response**: "AIWG MCP server exposes 50 tools (one per CLI command), 5 resources (framework artifacts, index, catalog), and 3 prompts (intake-wizard, security-review, architecture-baseline)." ## Clarification Prompts If the user's intent is ambiguous: - "Are you trying to start the server locally, or configure an MCP client to connect to it?" - "Which client should I configure? (e.g., claude, cursor, opencode)" ## References - @$AIWG_ROOT/src/cli/handlers/subcommands.ts — MCP subcommand handler - @$AIWG_ROOT/docs/cli-reference.md — CLI reference (mcp section)
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.