Skip to content

feat: list sbx-kits (Docker Sandboxes kit authoring skill) - #7

Draft
jedp-docker wants to merge 1 commit into
docker:mainfrom
jedp-docker:feat/sbx-kit-author-marketplace-entry
Draft

feat: list sbx-kits (Docker Sandboxes kit authoring skill)#7
jedp-docker wants to merge 1 commit into
docker:mainfrom
jedp-docker:feat/sbx-kit-author-marketplace-entry

Conversation

@jedp-docker

@jedp-docker jedp-docker commented Jul 3, 2026

Copy link
Copy Markdown

Summary

  • Adds a sbx-kits entry to plugins[] referencing docker/sbx-kits-contrib by git source ({"source": "github", "repo": "docker/sbx-kits-contrib", "ref": "main"}) rather than vendoring the skill's files into this repo. This is the first external-source entry in this marketplace — existing entries all use the ./plugins/... local-path convention, but that's a convention, not a schema requirement.
  • The skill is sbx-kits-contrib's kit-author skill: reference documentation for authoring Docker Sandboxes kits (spec.yaml, v2 schema).
  • Entry is named sbx-kits, matching that repo's own .claude-plugin/plugin.json name (feat: add plugin manifest, fix kit-author skill activation trigger sbx-kits-contrib#126). Component namespacing (<plugin-name>:<skill-name>) is driven by plugin.json's own name, while the marketplace entry's name is only the install alias; a mismatch would mean /plugin install X@docker produces something invoked as Y:skill-name, which is confusing. sbx-kits is a deliberate, user-facing namespace choice, not tied to the source repo's name — chosen so that if more skills fold in later (e.g. workflow skills currently living in sbx-toolkit), they all land under this one sbx-kits: prefix. Namespacing has no cross-repo merging mechanism, so any future skills sharing this prefix must live in the same sbx-kits-contrib repo/plugin, not a separately-sourced one.

Depends on

Test plan

  • marketplace.json is valid JSON.
  • After #126 merges: /plugin marketplace add docker/claude-plugins/plugin install sbx-kits@docker successfully discovers skills/kit-author/ from the referenced repo, invoked as /sbx-kits:kit-author.
  • Follow-up: pin ref to a release tag/SHA instead of main once one is cut.

@jedp-docker jedp-docker changed the title feat: list sbx-kit-author (Docker Sandboxes kit authoring skill) feat: list sbx-kits-contrib (Docker Sandboxes kit authoring skill) Jul 6, 2026
@jedp-docker jedp-docker changed the title feat: list sbx-kits-contrib (Docker Sandboxes kit authoring skill) feat: list sbx-kits (Docker Sandboxes kit authoring skill) Jul 7, 2026
Adds a plugins[] entry that references docker/sbx-kits-contrib
directly by git source rather than vendoring the skill's files into
this repo — the skill's canonical home stays in sbx-kits-contrib,
next to the spec package it documents. This is the first
external-source entry in this marketplace; existing entries all use
the ./plugins/... local-path convention, but that's a convention, not
a schema requirement.

Named sbx-kits, matching that repo's own .claude-plugin/plugin.json
name (docker/sbx-kits-contrib#126) rather than the repo's own name.
Component namespacing (<plugin-name>:<skill-name>) is driven by
plugin.json's name, while the marketplace entry's name is only the
install alias — a mismatch would mean /plugin install X@docker
produces something invoked as Y:skill-name, which is confusing.
sbx-kits is a deliberate, user-facing namespace: if more skills fold
in later (e.g. workflow skills currently living in sbx-toolkit),
they'd need to live in this same sbx-kits-contrib repo/plugin to
share the prefix, since namespacing has no cross-repo merging
mechanism.

Depends on docker/sbx-kits-contrib#126, which adds the plugin.json
and fixes the skill's activation trigger — this entry's `ref: main`
won't resolve to a usable plugin until that merges. Opening as draft
for that reason.
@jedp-docker
jedp-docker force-pushed the feat/sbx-kit-author-marketplace-entry branch from 67341e0 to e3457d6 Compare July 7, 2026 19:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant