Refocus mpak positioning on MCPB bundles (skills purge, stage 1)#124
Open
mgoldsborough wants to merge 2 commits into
Open
Refocus mpak positioning on MCPB bundles (skills purge, stage 1)#124mgoldsborough wants to merge 2 commits into
mgoldsborough wants to merge 2 commits into
Conversation
mpak is being refocused to do one thing well: package MCP servers as portable, security-scanned MCPB bundles. Skill packaging and distribution move to the skills.sh / npx skills ecosystem. This is stage 1 of the skills purge (positioning/messaging only). Web, docs, backend API, and CLI removal follow in subsequent PRs. - README: remove the Skills concept section, mpak skill CLI rows, /v1/skills API surface line, SkillSchema export, and skill mentions in SDK/web/docs blurbs; reword the seed section around bundles - CLAUDE.md: scope statement now bundles-only - package.json: drop the agent-skills keyword
This was referenced Jun 20, 2026
QA on this stage-1 PR flagged that the 'mpak search' table row and the seed step described the stage-3 end state as current fact: 'mpak search' still searches bundles and skills (program.ts + commands/search.ts), and 'npm run db:seed' still seeds skills (prisma/seed.ts) until the backend PR lands. A command table and a numbered setup procedure are contracts a reader executes, so they cannot lead the code. Revert those two reference edits to match current behavior; they move to the backend PR (stage 3) alongside the program.ts/search.ts/seed.ts changes that make them true. The skill-command rows stay removed (de-advertising is the point of stage 1).
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
1 participant
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.
Refocusing mpak: bundles only
mpak is being refocused to do one thing well: package MCP servers as portable, security-scanned MCPB bundles. Agent Skills support is being removed because the broader ecosystem is moving to
skills.sh/npx skillsfor skill packaging and distribution.This is stage 1 of 4 — positioning and messaging only. No code is removed yet.
Staged rollout
/skills*→/bundles) — Remove Agent Skills from web + docs, redirect to bundles (skills purge, stage 2) #125/v1/skillsroutes,SkillRepository, skill schemas, SDK methods,mpak skillCLI; dropSkill/SkillVersiontables — Remove Agent Skills from backend: API, SDKs, CLI, drop tables (skills purge, stage 3) #126contributor-toolkit,org-profile, template reposChanges here
mpak skill *CLI rows, the/v1/skills/*API-surface line, theSkillSchemaexport, and skill mentions in the SDK / web / docs blurbsagent-skillskeywordIntentional staging boundary
This PR only de-advertises skills (removes inventory entries and narrative). It does not restate any live behavior as bundles-only: the
mpak searchcommand-table row still reads "Search bundles and skills" and thenpm run db:seedstep still describes seeding skills, because both track code that does not change until stage 3 (#126). Reference docs that a reader executes must not lead the implementation. Those two edits land in #126 alongside theprogram.ts/commands/search.ts/prisma/seed.tschanges that make them true.CHANGELOG.mdhistory is left intact (the 0.1.0 entry is accurate for that release); the "Removed" entry lands with the code removal in #126.