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/ARD.md
View on GitHub# ARD: Plugin Creator
> Part of [Tons of Skills](https://tonsofskills.com) by [Intent Solutions](https://intentsolutions.io) | [jeremylongshore.com](https://jeremylongshore.com)
## System Context
The Plugin Creator generates new plugin scaffolds within the claude-code-plugins monorepo, wiring them into the marketplace catalog and validation pipeline.
```
User Request ("Create a security plugin with skills")
↓
[Plugin Creator]
├── Creates: directory structure, plugin.json, README, LICENSE, components
├── Updates: marketplace.extended.json
└── Runs: sync-marketplace, validate-all-plugins.sh
↓
CI-Ready Plugin
├── plugins/[category]/[name]/
├── Catalog entry in marketplace.extended.json
└── Validation passing
```
## Data Flow
1. **Input**: Plugin name, category, type (commands/agents/skills/MCP/hybrid), description, keywords, and optional author override from the user request
2. **Processing**: Validate the name is unique and kebab-case, create the directory tree, generate all required files from templates, add the marketplace entry, run sync to regenerate `marketplace.json`, then execute the validation script to confirm the plugin is CI-ready
3. **Output**: Complete plugin directory with all required files, marketplace catalog entry, validation confirmation, and suggested next steps (implement logic, commit, push)
## Key Design Decisions
| Decision | Choice | Rationale |
|----------|--------|-----------|
| Template-driven generation | Predefined templates for each file type | Ensures consistency; templates encode all CI requirements (field allowlist, frontmatter format) |
| Validation-last workflow | Create everything, then validate at the end | Single validation pass catches all issues at once; faster than validate-as-you-go |
| Kebab-case enforcement | Reject names that aren't kebab-case | Repository convention; CI enforces it; catching early saves a cycle |
| Default MIT license | MIT unless explicitly overridden | Most plugins in the marketplace use MIT; lowest friction for contributors |
| Minimum 2 keywords | Required in plugin.json template | Marketplace search and discovery depend on keywords; enforced by CI |
| Author defaults to repo owner | Use Jeremy Longshore when unspecified | Reduces friction for internal plugins; community contributors always specify |
| Category validation | Check against allowed category list | Invalid categories cause marketplace sync failure; catch early |
## Tool Usage Pattern
| Tool | Purpose |
|------|---------|
| Write | Create all plugin files: plugin.json, README.md, LICENSE, component files (commands/agents/skills/MCP) |
| Read | Check existing plugins for name conflicts; read marketplace.extended.json for entry addition |
| Grep | Search catalog for duplicate plugin names; verify naming conventions |
| Bash(cmd:*) | Run `jq` for JSON validation, `pnpm run sync-marketplace`, `./scripts/validate-all-plugins.sh`, `chmod +x` |
## Error Handling Strategy
| Error Class | Detection | Recovery |
|------------|-----------|----------|
| Duplicate plugin name | Grep finds existing entry in marketplace.extended.json | Suggest alternative names; show the existing plugin for disambiguation |
| Invalid category | Category not in the allowed set | List valid categories; suggest the closest match |
| JSON syntax error in generated files | `jq empty` returns non-zero | Re-generate the JSON file; parse the jq error to identify the broken field |
| Marketplace sync failure | `pnpm run sync-marketplace` exits non-zero | Check for schema violations in the new entry; verify required fields |
| Validation failure | `validate-all-plugins.sh` reports errors | Parse the validation output; fix each flagged issue; re-validate |
## Extension Points
- Custom templates: allow users to specify a template directory for org-specific plugin conventions
- Interactive mode: prompt for each field interactively when minimal input is provided
- Batch creation: generate multiple related plugins from a manifest file
- Post-create hooks: run custom scripts after plugin creation (e.g., initialize git, create branch)
- SaaS pack support: extend to create multi-skill packs with shared configuration
- Migration tool: convert existing non-standard plugins into the validated structure
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 |