new-plugin
Generates scaffolding for new MCP plugins.
Install
mkdir -p .claude/skills/new-plugin && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10218" && unzip -o skill.zip -d .claude/skills/new-plugin && rm skill.zipInstalls to .claude/skills/new-plugin
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when user wants to create a new MCP Tool Hub plugin — automates scaffolding with directory structure, __init__.py, backend.py, and README.md from templatesKey capabilities
- →Scaffold plugin directory
- →Generate backend boilerplate
- →Create README templates
- →Register plugins
How it works
Automates directory creation and file generation for new MCP Tool Hub plugins using predefined templates.
Inputs & outputs
When to use new-plugin
- →Initialize a new plugin project
- →Create standard file templates for plugins
- →Structure new MCP tools
About this skill
New Plugin Workflow
This skill automates creating a new MCP Tool Hub plugin with proper scaffolding.
When to Use
User asks to:
- "create a new plugin"
- "add a plugin"
- "make a new tool"
- Any variant expressing intent to create a new MCP plugin
Input Parameters
| Parameter | Required | Description |
|---|---|---|
plugin_name | Yes | Unique plugin identifier (no _ or . prefix) |
display_name | No | Human-readable name (defaults to plugin_name) |
tools | No | Comma-separated list of tool names |
has_widget | No | Whether to include a PySide6 widget (default: false) |
has_config | No | Whether to include configuration support (default: false) |
Workflow
Step 1: Validate Input
- Check
plugin_namedoesn't start with_or. - Check
plugin_namedoesn't already exist inplugins/
Step 2: Create Directory
Create plugins/{plugin_name}/ directory.
Step 3: Generate Files
Generate the following files from templates:
__init__.py:
from .backend import PluginClass
PLUGIN_CLASS = PluginClass
WIDGET_CLASS = None # or WidgetClass if has_widget=true
backend.py:
- Plugin class with
ToolDefdeclarations for each tool - Handler methods
handle_{tool_name} - PluginMeta property
widget.py (if has_widget=true):
BasePluginWidgetsubclass with UI components
README.md:
- Plugin description
- Tools table
- Dependencies list
- Usage examples
Step 4: Register in Project
No manual registration needed — PluginManager auto-discovers.
Output
- Plugin directory at
plugins/{plugin_name}/ - All required files generated
- Summary of created files and next steps
Example
User: /new-plugin plugin_name=weather,tools=get_forecast;get_weather,has_widget=true
Output: Creates plugins/weather/ with backend.py, widget.py, init.py, README.md
When not to use it
- →Modifying existing plugins
Limitations
- →Plugin name cannot start with _ or .
How it compares
Standardizes plugin structure automatically instead of manual file creation.
Compared to similar skills
new-plugin side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| new-plugin (this skill) | 0 | 1mo | Review | Beginner |
| telegram-bot-builder | 106 | 6mo | Review | Intermediate |
| mcp-integration | 21 | 8mo | Review | Intermediate |
| n8n-workflow-patterns | 16 | 2mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
telegram-bot-builder
davila7
Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.
mcp-integration
anthropics
This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides comprehensive guidance for integrating Model Context Protocol servers into Claude Code plugins for external tool and service integration.
n8n-workflow-patterns
czlonkowski
Proven workflow architectural patterns from real n8n workflows. Use when building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture, or asking about webhook processing, HTTP API integration, database operations, AI agent workflows, or scheduled tasks.
n8n-code-javascript
czlonkowski
Write JavaScript code in n8n Code nodes. Use when writing JavaScript in n8n, using $input/$json/$node syntax, making HTTP requests with $helpers, working with dates using DateTime, troubleshooting Code node errors, or choosing between Code node modes.
n8n-expression-syntax
czlonkowski
Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, or working with webhook data in workflows.
n8n-node-configuration
czlonkowski
Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node_essentials and get_node_info, or learning common configuration patterns by node type.