Files

Defame1297 4d061bd199 feat(kyberforge): add plugin-author and marketplace-author skills

## Why

Plugin and marketplace management had no governed authoring path. Creating or
updating a plugin required knowing the dual-manifest convention, version parity
rules, and directory skeleton by memory — nothing enforced consistency or guided
the process.

`/plugin-author` closes that gap by owning the full plugin scaffold lifecycle:
create, update, rename, and release. `/marketplace-author` handles the
marketplace-facing side: register, deregister, and update plugin entries in
`marketplace.json`.

ADR-0016 codifies the version parity convention (identical `version` in both
`plugin.json` and `.claude-plugin/plugin.json`) that `/plugin-author` now
enforces. The two plugin.json files in this repo are backfilled to comply
(keys also sorted to pass the pretty-format-json hook). CONTEXT.md gains
glossary entries for "plugin scaffold" and "version parity" so future agents
have shared vocabulary for these concepts.

## Implementation Notes

`/plugin-author` ships a `scripts/new-plugin.sh` scaffold script that generates
the directory skeleton and both manifests in one shot; the skill calls the script
rather than generating files ad hoc so the scaffold is reviewable and repeatable.

Version parity is an invariant, not a suggestion — the skill will fail loudly
on create/update if the two versions would diverge.

ADR: docs/adr/0016-plugin-version-parity.md

2026-06-28 10:45:03 +00:00

1.5 KiB

Raw Blame History

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/
`tests/README.md`	Test dependency instructions and run command

1.5 KiB Raw Blame History