agent-loop-ext
Crash-resilient external agent loop with state persistence and CI/CD integration
Manage the AIWG MCP server — start it, configure clients, and maintain the registered server registry
$ npx -y skills add jmagly/aiwg --skill aiwg-mcp-server --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/aiwg-mcp-serverContext preview
The summary Claude sees to decide when to auto-load this skill.
Manage the AIWG MCP server — start it, configure clients, and maintain the registered server registry
namespace: aiwg name: aiwg-mcp-server platforms: [all] description: Manage the AIWG MCP server — start it, configure clients, and maintain the registered server registry
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.
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
| 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` |
When triggered:
1. **Identify the subcommand**:
2. **Run the appropriate command**:
# 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.
**User**: "Start the MCP server"
**Extraction**: Serve subcommand, no options
**Action**:
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."
**User**: "Configure MCP for Claude Desktop"
**Extraction**: Install for claude client
**Action**:
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."
**User**: "Add the filesystem MCP server from @modelcontextprotocol/server-filesystem"
**Extraction**: Add subcommand, ref = @modelcontextprotocol/server-filesystem
**Action**:
aiwg mcp add @modelcontextprotocol/server-filesystem
**Response**: "Registered filesystem MCP server. It will be available as 'filesystem' in `aiwg mcp list`."
**User**: "Which MCP servers are registered?"
**Extraction**: List subcommand
**Action**:
aiwg mcp list
**Response**: "2 MCP servers registered: aiwg (built-in), filesystem (@modelcontextprotocol/server-filesystem)."
**User**: "What does the AIWG MCP server expose?"
**Extraction**: Info subcommand
**Action**:
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)."
If the user's intent is ambiguous:
Reusable project context and specialist workflows for the AI tools you already use. Plan software, coordinate specialist reviews, prepare campaigns, investigate incidents, organize research, curate media, and maintain operational knowledge.
Repo: jmagly/aiwg
Crash-resilient external agent loop with state persistence and CI/CD integration
Detect requests for iterative autonomous agent loops and route to the appropriate loop executor
Automatically execute tests when code-generating agents modify source files, enforcing the execute-before-return pattern
Enable agent loops to learn from similar past tasks and share patterns across loops
Query and manage the executable feedback debug memory
Execute tests on generated code and iterate until passing