Once the uncov skill exists (#6), make llbbl/uncov its own native Claude Code marketplace so users install with /plugin marketplace add llbbl/uncov → /plugin install <plugin>@llbbl-uncov. This gives first-class auto-update, /plugin discovery, and clean uninstall — replacing the current DIY/guide-based setup.
Background
- A plugin is defined by
.claude-plugin/plugin.json (name, description, version, author) with skills under skills/<name>/SKILL.md.
- A marketplace is defined by
.claude-plugin/marketplace.json cataloging the plugin(s). A single repo can be its own marketplace.
- The skill ships as pure markdown and calls
uncov from PATH (no bundled binary), so the plugin stays tiny.
Acceptance
- Repo contains
.claude-plugin/plugin.json and .claude-plugin/marketplace.json.
/plugin marketplace add llbbl/uncov then /plugin install <plugin>@<marketplace> installs the uncov skill, namespaced.
- README documents the marketplace install path (and notes the
uncov binary prerequisite via brew/npm/install.sh).
- Verified end-to-end on a clean profile.
Tasks
Depends on #6 — the skill must exist (and be PATH-based) before it can ship via the marketplace.
Once the
uncovskill exists (#6), makellbbl/uncovits own native Claude Code marketplace so users install with/plugin marketplace add llbbl/uncov→/plugin install <plugin>@llbbl-uncov. This gives first-class auto-update,/plugindiscovery, and clean uninstall — replacing the current DIY/guide-based setup.Background
.claude-plugin/plugin.json(name, description, version, author) with skills underskills/<name>/SKILL.md..claude-plugin/marketplace.jsoncataloging the plugin(s). A single repo can be its own marketplace.uncovfromPATH(no bundled binary), so the plugin stays tiny.Acceptance
.claude-plugin/plugin.jsonand.claude-plugin/marketplace.json./plugin marketplace add llbbl/uncovthen/plugin install <plugin>@<marketplace>installs the uncov skill, namespaced.uncovbinary prerequisite via brew/npm/install.sh).Tasks
.claude-plugin/plugin.json.claude-plugin/marketplace.jsoncataloging the uncov pluginskills/layout matches plugin expectations (skills/<name>/SKILL.md)/plugin marketplace add+/plugin installend-to-endDepends on #6 — the skill must exist (and be PATH-based) before it can ship via the marketplace.