Files
holocron/plugins/kyberforge/skills
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
..

skills/

Skills for this plugin. Each skill lives in its own subdirectory:

skills/
  <skill-name>/
    SKILL.md      # required — frontmatter + skill body
    META.md       # required — provenance and audit fields
    references/   # optional — on-demand reference docs
    scripts/      # optional — executable helper scripts
    assets/       # optional — templates, data files, lookup tables

Shared — both Claude Code and GitHub Copilot CLI read skills/<name>/SKILL.md.

To create or improve a skill, run /skill-author in a Claude Code session. To review a skill without modifying it, run /skill-audit. Do not write SKILL.md by hand without following the authoring standard — trigger descriptions and body discipline are required.