create-plugin
Skill208 starsChanged 3 months agoMITView on GitHub
This skill should be used when the user asks to "create a plugin", "make a GitHub plugin", "turn my repo into a plugin", "create a Claude Code plugin", "create a Codex plugin", "publish my skills as a plugin", or "set up a plugin marketplace". Scaffolds the complete file structure for a repo that works as both a Claude Code and Codex plugin with marketplace support.
- Commits and pushes
14 other projects use a version of this.
Adopted by
Most recently taken up by
- rzx007/openharness-tstheir own version, first seen Oct 22, 2026
- rzx007/Vykortheir own version, first seen Oct 22, 2026
- mistralai/mistral-vibetheir own version, first seen Oct 19, 2026
- ToolJet/ToolJettheir own version, first seen Oct 13, 2026
- garbageek/claude-pluginstheir own version, first seen Oct 13, 2026
- bitovi/ai-enablement-promptstheir own version, first seen Oct 9, 2026
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- ToolJet/ToolJet★ 41ksame name
- rundeck/rundeck★ 6.4ksame name
- mistralai/mistral-vibe★ 5.3ksame name
- datavane/tis★ 1.4ksame name
- marcus/sidecar★ 1.1ksame name
- lbedner/aegis-stack★ 146same name
- bitovi/ai-enablement-prompts★ 121same name
- npow/oh-my-claude★ 4same name
- rzx007/openharness-ts★ 3same name
- rzx007/Vykor★ 3same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- audit-offerSkill
- bonus-stackSkill
- business-modelSkill
- dfy-dwy-diySkill
- effort-reductionSkill
- hormozi-hooksSkill
- hormozi-offerSkill
- hormozi-pitchSkill
- idea-to-productSkill
- landing-page-copySkill
- market-researchSkill
- objection-destroyerSkill
- offer-anglesSkill
- pricing-strategySkill
- productizeSkill
- value-acceleratorSkill
- value-perceptionSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Ask the user these questions (all at once):
- Distinctive: line 29
Do not proceed until you have at least: repo name, GitHub username, description, and author name.
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: Plugin Creator (Claude Code + Codex)
Purpose
Scaffold a GitHub repo that works as a plugin for both Claude Code and Codex simultaneously. Outputs ready-to-copy file contents and git commands for every required file.
Step 1: Gather Inputs
Ask the user these questions (all at once):
- Repo name — kebab-case (e.g.
my-skills) - GitHub username or org — (e.g.
alexsmedile) - Plugin description — one sentence
- Author name
- What does this plugin contain? — pick all that apply:
- Skills (
skills/) - Agents (
agents/) - Hooks (
hooks/hooks.json) - MCP servers (
.mcp.json)
- Skills (
- License — default:
MIT
Do not proceed until you have at least: repo name, GitHub username, description, and author name.
Step 2: Generate File Structure
Show the full directory tree based on their selections, then output every file's content ready to copy.
Always-required files
.claude-plugin/plugin.json
{
"name": "{{repo-name}}",
"version": "1.0.0",
"description": "{{description}}",
"author": {
"name": "{{author}}"
},
"homepage": "https://github.com/{{username}}/{{repo-name}}",
"repository": "https://github.com/{{username}}/{{repo-name}}",
"license": "{{license}}",
"keywords": []
}Skills and agents in
skills/andagents/are auto-discovered — no paths needed inplugin.json.
.claude-plugin/marketplace.json
{
"name": "{{repo-name}}",
"owner": {
"name": "{{author}}"
},
"metadata": {
"description": "{{description}}",
"version": "1.0.0"
},
"plugins": [
{
"name": "{{repo-name}}",
"source": "./",
"description": "{{description}}",
"version": "1.0.0",
"author": {
"name": "{{author}}"
},
"homepage": "https://github.com/{{username}}/{{repo-name}}",
"repository": "https://github.com/{{username}}/{{repo-name}}",
"license": "{{license}}",
"category": "productivity"
}
]
}.codex-plugin/plugin.json
{
"name": "{{repo-name}}",
"version": "1.0.0",
"description": "{{description}}",
"author": {
"name": "{{author}}"
},
"homepage": "https://github.com/{{username}}/{{repo-name}}",
"repository": "https://github.com/{{username}}/{{repo-name}}",
"license": "{{license}}",
"skills": "./skills/"
}.codex-plugin/marketplace.json
{
"name": "{{repo-name}}",
"interface": {
"displayName": "{{repo-name}}"
},
"plugins": [
{
"name": "{{repo-name}}",
"source": {
"source": "local",
"path": "./"
},
"category": "Productivity"
}
]
}.gitignore
.DS_Store
**/.DS_Store
output/*
!output/.gitkeepoutput/.gitkeep
Empty file — keeps the output/ folder tracked by git.
If skills selected: skills/example-skill/SKILL.md
---
name: example-skill
description: Replace this description with specific trigger phrases. Use when the user asks to "..."
---
# Skill: Example
Describe what this skill does and how to use it.Rename
example-skill/to your actual skill name. Skill is invoked as/{{repo-name}}:example-skill.
If agents selected: agents/example-agent.md
---
name: example-agent
description: Replace with what this agent does and when to invoke it.
tools: Read, Write, Bash
model: sonnet
---
# Agent: Example
Describe the agent's role, expertise, and behavior here.Rename to your actual agent name.
If hooks selected: hooks/hooks.json
{
"hooks": {
"PostToolUse": [
{
"matcher": "Write|Edit",
"hooks": [
{
"type": "command",
"command": "echo 'File changed'"
}
]
}
]
}
}If MCP servers selected: .mcp.json
{
"mcpServers": {
"example-server": {
"command": "${CLAUDE_PLUGIN_ROOT}/bin/server",
"args": []
}
}
}Step 3: Critical Rules
State these clearly before the user creates any files:
| Rule | Detail |
skills/ and agents/ at repo root | Never inside .claude-plugin/ or .codex-plugin/ |
| Plugin name = skill namespace | Plugin foo → skills run as /foo:skill-name |
plugin.json is auto-discovery | No need to list skills or agents paths unless using custom locations |
Do NOT add skills/agents to marketplace.json | Causes schema validation error with default strict: true |
source: "./" in marketplace.json | Points at repo root — correct for single-plugin repos |
Step 4: Git Setup + Install Commands
Output these exactly, substituting the user's values:
# Create repo (if not exists)
gh repo create {{username}}/{{repo-name}} --public
# Init and push
git init
git add .
git commit -m "feat: initial plugin scaffold"
git remote add origin https://github.com/{{username}}/{{repo-name}}.git
git push -u origin mainInstall in Claude Code:
/plugin marketplace add {{username}}/{{repo-name}}
/plugin install {{repo-name}}@{{repo-name}}Reload after changes:
/reload-pluginsTest locally without installing:
claude --plugin-dir ./Step 5: After Install
Skills are namespaced: /{{repo-name}}:skill-name
Agents appear in /agents
To update: push to GitHub, then /plugin marketplace update {{repo-name}}
Bump version in plugin.json and marketplace.json with each release — Claude Code uses version to detect updates.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

