create-plugin-scaffold
Create a new Cursor plugin scaffold with a valid manifest, component directories, and marketplace wiring. Use when starting a new plugin or adding a plugin to a multi-plugin repository.
Best use case
create-plugin-scaffold is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create a new Cursor plugin scaffold with a valid manifest, component directories, and marketplace wiring. Use when starting a new plugin or adding a plugin to a multi-plugin repository.
Teams using create-plugin-scaffold should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/create-plugin-scaffold/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How create-plugin-scaffold Compares
| Feature / Agent | create-plugin-scaffold | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create a new Cursor plugin scaffold with a valid manifest, component directories, and marketplace wiring. Use when starting a new plugin or adding a plugin to a multi-plugin repository.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Create plugin scaffold ## Trigger You need to create a new Cursor plugin from scratch and make it ready for local use or marketplace submission. ## Required Inputs - Plugin name (lowercase kebab-case) - Plugin purpose and target users - Component set to include (`rules`, `skills`, `agents`, `commands`, `hooks`, `mcpServers`) - Repository style (`single-plugin` or `multi-plugin marketplace`) ## Output Location By default, create the plugin inside the user's local plugin directory: ``` ~/.cursor/plugins/local/<plugin-name>/ ``` This path makes the plugin immediately available to Cursor without any install step. If the user explicitly asks to create the plugin elsewhere (e.g. inside an existing repo or a specific directory), respect that choice instead. ## Workflow 1. Validate plugin name format: lowercase kebab-case, starts and ends with an alphanumeric character. 2. Determine the target directory: - Default: `~/.cursor/plugins/local/<plugin-name>/` - Override: use the path the user specifies, if any. - Create the directory (and parents) if it does not exist. 3. Create base files inside the target directory: - `.cursor-plugin/plugin.json` - `README.md` - `LICENSE` - optional `CHANGELOG.md` 4. Populate `plugin.json`: - Required: `name` - Recommended: `version`, `description`, `author`, `license`, `keywords` - Add explicit component paths only when non-default discovery is needed. 5. Create component files with valid frontmatter: - Rules: `.mdc` with `description`, `alwaysApply`, optional `globs` - Skills: `skills/<skill-name>/SKILL.md` with `name`, `description` - Agents: `agents/*.md` with `name`, `description` - Commands: `commands/*.(md|txt)` with `name`, `description` 6. If repository uses `.cursor-plugin/marketplace.json`, add plugin entry: - `name` - `source` - optional metadata (`description`, `keywords`, `category`, `tags`) 7. Ensure all manifest paths are relative, valid, and do not use absolute paths or parent traversal. ## Guardrails - Keep the plugin focused on one use case. - Prefer concise, actionable skill and rule text over long prose. - Do not reference files that do not exist. - Use folder discovery defaults unless custom paths are required. - Always save to `~/.cursor/plugins/local/<plugin-name>/` unless the user provides a different path. ## Output - Created file tree for the plugin (with full path to the output directory) - Final `plugin.json` - Marketplace entry (if applicable) - Short validation report of required fields and component metadata - Confirmation that the plugin is saved under `~/.cursor/plugins/local/` and ready for use
Related Skills
electron-scaffold
Scaffold a native-looking, effective Electron app with best practices baked in. Creates a production-ready Electron application with security hardening, modern tooling, proper IPC patterns, auto-updates, native UI elements, and optimal build configuration. Use this skill when users want to start a new Electron project or modernize an existing one.
developing-claude-code-plugins
Build, test, and distribute Claude Code plugins with slash commands, agents, skills, hooks, MCP servers, and LSP servers. MUST be loaded when creating, reviewing, debugging, or distributing plugins. Use PROACTIVELY when user mentions plugins, extensions, marketplaces, or wants to add custom commands/agents to Claude Code.
cross-plugin-detective
Integration guide for using detective skills across plugins. Maps agent roles from frontend, bun, and other plugins to appropriate detective skills. Developer agents should use developer-detective, architect agents should use architect-detective, etc.
create-target
Scaffold a new target type (e.g., Zed, Windsurf) for universal-ai-config
create-project
Initialize new projects with CAMI capabilities and recommended agent teams. Triggers on "create a new project", "start a new project", "initialize project", "set up project with agents", "what agents do I need for this project", "help me set up my project roster". Guides through project requirements, tech stack detection, agent team recommendations, and full CAMI initialization.
create-pr
JIRAチケットブランチからPRを自動作成するスキル。親ブランチ自動検出、JIRAリンク自動挿入、テンプレートに沿ったPR本文生成を行う。「PR作成」「PRを作って」「/create-pr」などのリクエストで使用。
create-my-tools-profile
Generate a personalized AI skill based on your configured Zapier MCP tools. Scans your enabled actions and creates instructions that help your AI assistant know when and how to use each tool. Use after setting up tools, or when you want to "create my tools profile", "personalize my assistant", or "make a skill from my tools".
create-mcp-json
Create an mcp.json client configuration from a server.json. Use when the user wants to generate a ready-to-use MCP client config for connecting to an MCP server.
create-issues
Systematic GitHub issue creation from requirements. Analyzes codebase, breaks down requirements into multiple issues with dependencies, proposes detailed issues for review, and creates them after user approval. Triggers: /create-issues, create issues, batch issue creation, requirement breakdown.
create-command
Guide for creating custom Claude Code slash commands with proper structure, argument handling, frontmatter configuration, and best practices. Use when the user wants to create slash commands, custom commands, reusable prompts, or mentions creating/designing/building commands.
--- name: create-book
description: Does a dev editor pass on files created from the create-story-bible skill
cowork-plugin-customizer
Customize or personalize a Claude Code plugin for a specific organization's tools and workflows by replacing placeholders and configuring MCP servers.