jeremylongshore/tons-of-skills-marketplace / plugins/examples/jeremy-plugin-tool/skills/plugin-creator
plugin-creator
VerifiedCreate automatically creates new AI assistant code plugins with proper structure, validation, and marketplace integration when user mentions creating a plugin, new plugin, or plugin from template. specific to AI assistant-code-plugins repository workflow. Use when generating or creating new content. Trigger with phrases like 'generate', 'create', or 'scaffold'.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.7 KB |
| assets/README.md | markdown | 526 B |
| references/ARD.md | markdown | 4.2 KB |
| references/PRD.md | markdown | 3.7 KB |
| references/README.md | markdown | 581 B |
| references/errors.md | markdown | 319 B |
| references/examples.md | markdown | 751 B |
| references/file-templates.md | markdown | 687 B |
| references/plugin-creation-process.md | markdown | 1.1 KB |
| scripts/README.md | markdown | 623 B |
references/PRD.md
View on GitHub# PRD: Plugin Creator
**Version:** 1.0.0
**Author:** Jeremy Longshore <jeremy@intentsolutions.io>
**Status:** Active
**Marketplace:** [tonsofskills.com](https://tonsofskills.com) by [Intent Solutions](https://intentsolutions.io)
**Portfolio:** [jeremylongshore.com](https://jeremylongshore.com)
---
## Problem Statement
Creating a new Claude Code plugin requires generating multiple interdependent files (plugin.json, README.md, LICENSE, component files) in the correct directory structure, adding a catalog entry to marketplace.extended.json, running marketplace sync, and passing validation. Doing this manually is error-prone: developers forget required fields, use wrong directory structures, misconfigure frontmatter, or skip marketplace registration. Each mistake is caught only at CI time, adding iteration cycles.
## Target Users
| User | Context | Primary Need |
|------|---------|-------------|
| Plugin Author | Creating a new plugin from scratch | Complete scaffolding with all required files, correct structure, and marketplace registration |
| Community Contributor | Adding a plugin to the marketplace for the first time | Guided creation that follows all repository conventions without prior knowledge |
| Internal Developer | Rapidly prototyping new plugin ideas | Fast scaffolding that produces a CI-passing plugin on first commit |
## Success Criteria
1. Generated plugin passes `./scripts/validate-all-plugins.sh` without modifications
2. All required files created: `plugin.json`, `README.md`, `LICENSE`, and at least one component directory
3. Marketplace entry added to `marketplace.extended.json` and `marketplace.json` regenerated via sync
4. Plugin structure matches the category and type (commands/agents/skills/MCP) specified in the request
## Functional Requirements
1. Gather requirements: plugin name (kebab-case), category, type (commands/agents/skills/MCP/hybrid), description, and keywords
2. Create the directory structure under `plugins/[category]/[plugin-name]/`
3. Generate `.claude-plugin/plugin.json` with all required fields (name, version, description, author, license, keywords)
4. Generate `README.md` with installation, usage, and description sections
5. Create `LICENSE` file with MIT text (or specified license)
6. Generate component files with proper YAML frontmatter based on plugin type
7. Add the plugin entry to `.claude-plugin/marketplace.extended.json`
8. Run `pnpm run sync-marketplace` to regenerate `marketplace.json`
9. Validate with `./scripts/validate-all-plugins.sh plugins/[category]/[plugin-name]/`
## Non-Functional Requirements
- Plugin names must be kebab-case and unique across the entire catalog
- Generated `plugin.json` must contain only allowed fields (no extra fields that CI rejects)
- All generated `.sh` files must have execute permissions set
- MCP plugins must include `package.json`, `tsconfig.json`, and build configuration
- Generated README must follow the repository's standard format with installation and usage sections
- Default version for new plugins is `1.0.0`
- Keywords array must contain at least 2 entries for marketplace search discoverability
## Dependencies
- Write access to the `plugins/` directory and `.claude-plugin/marketplace.extended.json`
- `jq` installed for JSON generation and validation
- `pnpm run sync-marketplace` available at the repository root
- `./scripts/validate-all-plugins.sh` available for validation
## Out of Scope
- Implementing the actual skill/command/agent logic (scaffolding only)
- Publishing to external registries
- Generating test files for MCP plugins
- Migrating existing plugins between categories
- Generating reference documentation (PRD, ARD, errors.md, etc.)
- Version bumping after creation (handled by version-bumper)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |