Defame1297
66e2e6a04d
## Why The UPDATE flow only bumped version when the version field itself was the target. Metadata changes (description, keywords, author) went out without a version bump, making them invisible to consumers with a cached copy. Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
plugin-author
Creates, updates, and releases plugin scaffolds for the holocron marketplace.
What it does
Manages both manifests (plugin.json for Copilot CLI and .claude-plugin/plugin.json for Claude Code) in one pass. Three operations: create a new plugin scaffold with placeholder manifests and skeleton dirs; update configuration fields (shared fields updated in both manifests simultaneously); release a version with HITL gate before tagging.
Out of scope: plugin content (skills, agents, hooks, MCP servers inside those dirs) and marketplace.json entries.
Before you start
Have ready: the plugin name (kebab-case) and the repo root path.
Usage
/plugin-author
Manual scaffold (human workflow):
bash scripts/new-plugin.sh <plugin-name> <repo-root>
# Examples:
bash scripts/new-plugin.sh my-tools /root/ai-development
bash scripts/new-plugin.sh data-tools .
Files
| File | Purpose |
|---|---|
SKILL.md |
Skill instructions for agents |
scripts/new-plugin.sh |
Scaffolds both manifests and skeleton dirs for a new plugin |
references/manifest-fields.md |
All optional fields for both manifests beyond the scaffolded defaults |
references/sources.md |
Research provenance — sources that informed this skill |
scripts/README.md |
Directory meta-documentation for scripts/ |
references/README.md |
Directory meta-documentation for references/ |