القائمة
Create, validate, and publish Claude Code plugins from forge modules. USE WHEN create plugin, validate plugin, publish plugin, marketplace, plugin.json, cowork plugin.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | BuildPlugin |
| version | 0.1.0 |
| description | Create, validate, and publish Claude Code plugins from forge modules. USE WHEN create plugin, validate plugin, publish plugin, marketplace, plugin.json, cowork plugin. |
| argument-hint | [create|validate|marketplace] [module-path] |
Create, validate, and publish forge modules as Claude Code plugins. Covers plugin.json creation, marketplace registration, and Cowork deployment.
| Workflow | Trigger | Reference |
|---|---|---|
| Create | "create plugin", "add plugin.json" | Instructions below |
| Validate | "validate plugin", "check marketplace readiness" | Instructions below |
| Marketplace | "add to marketplace", "publish to cowork" | @ClaudeMarketplace |
| Structure | "plugin layout", "auto-discovery", "bin PATH", "plugin env vars" | @ClaudePlugin |
module.yaml for name, version, description..claude-plugin/plugin.json:{
"name": "module-name",
"version": "0.1.0",
"description": "From module.yaml",
"author": {"name": "Author"},
"license": "EUPL-1.2",
"repository": "https://github.com/owner/repo",
"keywords": [],
"skills": ["../skills"]
}
"hooks": "./hooks/hooks.json" only if the module has hooks.Check these in order. Stop on first failure.
| Check | Pass criteria |
|---|---|
| plugin.json exists | .claude-plugin/plugin.json present and valid JSON |
| name | Lowercase kebab-case (Cowork enforces strictly) |
| version | Valid semver, matches module.yaml |
| description | Non-empty string |
| author | Object with name field |
| license | SPDX identifier present |
| repository | URL string present |
| keywords | Non-empty array |
| README.md | Exists, not empty |
| LICENSE | Exists |
| INSTALL.md | Follows install.md standard (OBJECTIVE, DONE WHEN, TODO) |
| CLAUDE.md | Exists |
| Skills | Each has SKILL.md with name/description/version frontmatter |
| Skill YAML | Each has SKILL.yaml with sources field |
Report:
Section Status
──────────────────────────────
plugin.json PASS / FAIL
module.yaml PASS / FAIL
Documentation PASS / FAIL
Skills PASS / FAIL
──────────────────────────────
Verdict: READY / NOT READY
Create and validate skills for forge modules. USE WHEN create skill, new skill, write skill, validate skill, check skill, skill structure, skill conventions.
Create, validate, evaluate, and iterate skills for forge modules. USE WHEN create skill, new skill, write skill, validate skill, check skill, skill structure, skill conventions, test a skill, run skill evals, benchmark a skill, skill not triggering, optimize skill description. Not for adopting community skills (AdoptArtifact) or shipping artifacts downstream (PublishArtifact).
Create, validate, or place behavioral rules in forge modules. USE WHEN create rule, new rule, write rule, capture rule, add a rule, graduate a correction or convention to a rule, validate rule, rule conventions, where does this rule belong, or the user runs /Rule.
Scaffold a workshop project: a VCS spine (git + jj colocate + entire + forge hooks), the private/public/assets flow layout with a .tlp manifest, a .claude/ that mounts the knowledge vault, and on-demand satellites (vault folder-note, data dir, private remote). USE WHEN starting a new project, initializing a folder for work, adding a vault note or data dir or remote to a project, archiving a project, or the user runs `project` / `atlas`.
Collaborative ideation before implementation — explore context, clarify intent, propose approaches. USE WHEN starting creative work, new features, design decisions, or modifying behavior.
Write a formal design spec from brainstorming output or requirements. USE WHEN design approved, write spec, formalize design, spec document.