feat: list sbx-kits (Docker Sandboxes kit authoring skill) - #7
Draft
jedp-docker wants to merge 1 commit into
Draft
feat: list sbx-kits (Docker Sandboxes kit authoring skill)#7jedp-docker wants to merge 1 commit into
jedp-docker wants to merge 1 commit into
Conversation
Draft
3 tasks
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
force-pushed
the
feat/sbx-kit-author-marketplace-entry
branch
from
July 7, 2026 19:07
67341e0 to
e3457d6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
sbx-kitsentry toplugins[]referencingdocker/sbx-kits-contribby 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.sbx-kits-contrib'skit-authorskill: reference documentation for authoring Docker Sandboxes kits (spec.yaml, v2 schema).sbx-kits, matching that repo's own.claude-plugin/plugin.jsonname (feat: add plugin manifest, fix kit-author skill activation trigger sbx-kits-contrib#126). Component namespacing (<plugin-name>:<skill-name>) is driven byplugin.json's own name, while the marketplace entry's name is only the install alias; a mismatch would mean/plugin install X@dockerproduces something invoked asY:skill-name, which is confusing.sbx-kitsis 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 insbx-toolkit), they all land under this onesbx-kits:prefix. Namespacing has no cross-repo merging mechanism, so any future skills sharing this prefix must live in the samesbx-kits-contribrepo/plugin, not a separately-sourced one.Depends on
.claude-plugin/plugin.jsonand trims/fixes the skill's activation trigger, which is what makes that repo a valid, discoverable plugin target. This PR'sref: mainwill not resolve to a usable plugin until #126 merges. Opening as draft for that reason; will mark ready once #126 is in and, ideally, once a release tag exists to pinrefto instead of the mutablemainbranch.Test plan
marketplace.jsonis valid JSON./plugin marketplace add docker/claude-plugins→/plugin install sbx-kits@dockersuccessfully discoversskills/kit-author/from the referenced repo, invoked as/sbx-kits:kit-author.refto a release tag/SHA instead ofmainonce one is cut.