Generate new MCP tools for GitLab operations following the project's standardized pattern. Creates complete TypeScript files with imports, registration functions, Zod schemas, error handling, and format options. Supports simple CRUD operations, complex multi-action tools, and advanced patterns like discussion management. Use when "create mcp tool", "generate gitlab tool", "new tool for", "add tool to gitlab", or building new GitLab integration features.
View on GitHubpy-plugin/skills/mcp-tool-generator/SKILL.md
January 20, 2026
Select agents to install to:
npx add-skill https://github.com/daispacy/py-claude-marketplace/blob/main/py-plugin/skills/mcp-tool-generator/SKILL.md -a claude-code --skill mcp-tool-generatorInstallation paths:
.claude/skills/mcp-tool-generator/# MCP Tool Generator Generate new MCP tools following the standardized patterns from the project. Creates complete tool files with proper imports, Zod schemas, error handling, and GitLab API integration. ## Activation Triggers - "create an mcp tool for..." - "generate a gitlab tool to..." - "I need a new tool that..." - "add a tool for [operation]" - "create tool to [action] [resource]" ## Tool Types Supported ### 1. Simple CRUD Tools Basic get/list/create/update/delete operations with standard patterns: - Get single resource (issue, MR, milestone, etc.) - List multiple resources with filtering and pagination - Create new resources - Update existing resources - Delete resources **Pattern**: `gitlab-[action]-[resource]` (e.g., `gitlab-get-issue`, `gitlab-list-pipelines`) ### 2. Multi-Action Tools Comprehensive tools that handle multiple related operations in one tool: - Multiple actions via `action` enum parameter - Conditional logic based on action type - Structured responses with status/action/message format - More efficient than multiple separate tools **Pattern**: `gitlab-[resource]-[operation]` (e.g., `gitlab-manage-issue`) ### 3. Complex Operation Tools Tools with advanced logic: - Discussion/comment management with update detection - Multi-step workflows - Direct API calls using fetch for specific needs - Position-based operations (code reviews, inline comments) **Pattern**: Based on specific operation (e.g., `gitlab-review-merge-request-code`) ## Autonomous Generation Process ### Step 1: Analyze User Request Extract key information: 1. **Tool Type**: Simple CRUD, multi-action, or complex? 2. **Tool Purpose**: What GitLab operation? (e.g., "get merge request details", "manage issues", "review code") 3. **Resource Type**: What GitLab entity? (issue, MR, branch, milestone, pipeline, label, etc.) 4. **Action Type**: What operation? (get, list, create, update, delete, search, manage, review, etc.) 5. **Required Parameters**: What inputs needed? (proje