claude-plugin-dev
Skill0 starsChanged 2 months agoMITView on GitHub
Package and publish a Claude Code plugin and marketplace (.claude-plugin/ manifests, skills, commands, agents, hooks) with a dual-target twist: the same repo simultaneously serves DeepSeek Harness (dsh), Codex, Gemini CLI and Copilot via plain skills and a dsh bundle. Use when creating a Claude Code plugin, setting up a marketplace repo, or making one repo installable across every agent.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- improve-claude-mdSkill
- show-meSkill
- deepseek-cost-routerSkill
- deepseek-migrationSkill
- dsh-plugin-devSkill
- skill-authorSkill
- skill-portability-auditSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 82
Hooks: keep them narrow and fast.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Building a Claude Code plugin & marketplace
A Claude Code plugin bundles skills, slash commands, subagents, hooks and MCP servers into one installable unit. A marketplace is a git repo that lists plugins so users can add it by name and install from it with one command.
Repo layouts
Single plugin:
my-plugin/
├── .claude-plugin/
│ └── plugin.json # {"name": "my-plugin", "version": "1.0.0", "description": "…"}
├── skills/ # <name>/SKILL.md folders
├── commands/ # <command>.md slash commands
├── agents/ # subagent definitions
└── hooks/ # lifecycle hooksMarketplace repo (can list many plugins, including its own subdirectories):
my-marketplace/
└── .claude-plugin/
└── marketplace.json{
"name": "my-marketplace",
"owner": { "name": "you" },
"plugins": [
{
"name": "my-plugin",
"source": "./plugins/my-plugin",
"description": "What it does",
"category": "productivity",
"keywords": ["skills", "automation"]
}
]
}A repo can be both marketplace and plugin: point the plugin entry at
"./" and put a .claude-plugin/plugin.json at the repo root (this is the
zhangliang0115/ai-plugin pattern).
How users install
# inside Claude Code:
/plugin marketplace add you/my-marketplace # git URL or owner/repo
/plugin install my-plugin@my-marketplaceSkills can also be dropped straight into ~/.claude/skills/<name>/SKILL.md
without any plugin packaging — use aipx install owner/repo to do that plus
every other agent in one shot.
Quality rules
- Plugin
name: kebab-case, stable — it's the namespace for commands. - Skill descriptions are routing triggers — say when to fire, not just what it is.
- Version your plugin.json and keep a CHANGELOG; users update via
/plugin marketplace update. - Dual-manifest for reach: adding a
.github/plugin.jsonmakes the same repo installable by GitHub Copilot CLI/VS Code tooling too. - Hooks: keep them narrow and fast; document exactly what they run — hooks execute shell on the user's machine, so earn trust explicitly.
Distribution checklist
.claude-plugin/plugin.json(plugin) ormarketplace.json(marketplace)- Skills validated: kebab-case names, trigger-style descriptions
- README shows the exact
/plugin marketplace addline - GitHub topics:
claude-code,claude-plugin,agent-skills - Cross-agent story (optional but high-leverage): also ship a
dsh-plugin/bundle and plainskills/— see thedsh-plugin-devskill andzhangliang0115/ai-plugin/docs/publish-dual-target.md
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.

