Skip to content

Split skyflow-skills into its own marketplace; make this repo MCP-only - #25

Open
jstjoe wants to merge 1 commit into
mainfrom
claude/skyflow-skills-marketplace-split-ddq7jk
Open

jstjoe wants to merge 1 commit into
mainfrom
claude/skyflow-skills-marketplace-split-ddq7jk

Conversation

@jstjoe

@jstjoe jstjoe commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Why

The security team is happy to authorize a Claude Code marketplace that contains only the skyflow-skills plugin, but not one that also carries the MCP servers (which they haven't yet approved for global internal use).

In Claude Code, allowlisting a marketplace (strictKnownMarketplaces) authorizes every plugin listed in it — there's no per-plugin gate. So a "skills-only" guarantee requires the authorized source to physically contain no MCP servers. The cleanest way to achieve that is a dedicated skills-only marketplace repo, with this repo slimmed down to just the MCP plugins.

The skills now live in SkyflowFoundry/skyflow-skills (marketplace name skyflow-skills-marketplace).

What changed in this repo

  • Removed the skyflow-skills-plugin/ directory (moved to the new repo, unchanged).
  • marketplace.json: dropped the skyflow-skills entry (now lists skyflow-developer-mcp and skyflow-runtime-mcp only), added a marketplace description, and added renames: { "skyflow-skills": null } so existing users get an automatic "removed from this marketplace" notice instead of a plugin-not-found error. (Automatic migration requires Claude Code v2.1.193+.)
  • Removed the skills-only CI (validate-skills/package-skills workflows + scripts) — these moved to the skills repo, which is now the source of truth for the standalone skill .zip releases.
  • README / CONTRIBUTING: rewritten as MCP-only, with a pointer to the new skills marketplace and updated upgrade guidance.

The draft/ directory is left in place (it isn't part of the published plugins).

Sequencing

Merge this after the new SkyflowFoundry/skyflow-skills marketplace is live, so there's no window where the skills aren't installable from any marketplace. The MCP plugins and their SKYFLOW_* environment variables are unchanged.

Validation

  • claude plugin validate . → passes.
  • marketplace.json parses; both MCP plugin sources resolve.

🤖 Generated with Claude Code

https://claude.ai/code/session_01EM64x84NsCFmy44MGYUeEx


Generated by Claude Code

The skyflow-skills plugin moves to a dedicated skills-only marketplace
(SkyflowFoundry/skyflow-skills) so a security team can authorize the
skills without authorizing the MCP servers. Allowlisting a marketplace
authorizes every plugin in it, so the skills-only guarantee requires a
source that contains no MCP servers.

This repo becomes the MCP-only marketplace:
- Remove the skyflow-skills-plugin/ directory
- Drop skyflow-skills from marketplace.json and add renames:
  {"skyflow-skills": null} so existing users get a clean migration notice
- Remove the skills-only validate/package CI (moved to the skills repo)
- Rewrite README/CONTRIBUTING as MCP-only and point skills users at the
  new marketplace

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EM64x84NsCFmy44MGYUeEx
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