Skip to content

Remove Agent Skills from web + docs, redirect to bundles (skills purge, stage 2)#125

Open
mgoldsborough wants to merge 2 commits into
mainfrom
chore/purge-skills-web
Open

Remove Agent Skills from web + docs, redirect to bundles (skills purge, stage 2)#125
mgoldsborough wants to merge 2 commits into
mainfrom
chore/purge-skills-web

Conversation

@mgoldsborough

@mgoldsborough mgoldsborough commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

Stage 2 of 4: bundle-only web UI + docs

mpak is being refocused to handle only MCPB bundles. This removes all Agent Skills surfaces from the web app and docs site. Skill URLs are redirected on-domain (per decision: redirect to mpak.dev URLs, not off-domain).

Builds on the positioning refocus in #124.

Redirects (both layers)

From To Mechanism
/skills (listing) /bundles (listing) nginx 301 + React Router <Navigate>
/skills/* (deep) /bundles (listing) nginx 301 + React Router <Navigate>
/publish/skills /publish nginx 301 + React Router <Navigate>

Note: there is no 1:1 skill→bundle mapping, so deep /skills/@scope/name URLs collapse to the /bundles listing rather than to a specific bundle. This preserves the domain/path and avoids 404s on previously-indexed URLs; the tradeoff is that search engines may treat the many-to-one collapse as soft-404s for the deep URLs. No more specific target exists. nginx uses ^~ /skills/ prefix matching so /skills/@scope/name redirects while /skillsfoo does not; client-side <Navigate> matches the repo's existing convention (/browse/bundles).

Web

  • Deleted: SkillsPage, SkillDetailPage, PublishSkillsPage, generated skill.ts schema
  • Pruned: nav links, homepage hero "Browse skills" + "What are Skills?" FAQ, About page skills column, publish gateway/page skill cards, lib/api skill methods, BadgeSection (now bundle-only)
  • SEO/build: prerender, generate-sitemap, generate-feed, generate-og-image, manifest.json, llms.txt, committed sitemap.xml/feed.xml all bundle-only

Docs

  • Deleted: docs/skills/* (5 pages) + cli/skills.mdx; removed the Skills sidebar section
  • Pruned: skill refs from index, ecosystem, quickstart, browsing, cli/{search,show,completion}, registry/{api,access-model,how-it-works}
  • Cleanup: untracked the 6 generated apps/docs/.astro/ cache files (already covered by .gitignore:10, committed before that rule; removes per-build reorder churn). astro build regenerates them.

Surface staging (intentional)

The docs now omit mpak skill * commands, but the CLI still ships them until stage 3 (#126), which deletes the mpak skill namespace. Docs narrower than the CLI is the safe direction; #126 closes the gap.

Verification (all green)

  • web typecheck ✓ · 60 tests ✓ · biome lint ✓
  • docs build ✓ (34 pages, no skills) · web build ✓
  • prerender ✓ (10 routes, zero skills)

The backend /v1/skills API still exists after this PR (removed in #126). Until then, the redirected /bundles UI simply does not query skill endpoints.

…bundles

Stage 2 of the skills purge. mpak's web UI and docs are now bundle-only.
Inbound skill links resolve on-domain to bundle equivalents.

Web:
- delete SkillsPage, SkillDetailPage, PublishSkillsPage, generated skill schema
- App.tsx routes: /skills + /skills/* -> /bundles, /publish/skills -> /publish
  (React Router Navigate); nginx.conf adds matching server-side 301s
- prune skills from nav, homepage hero/FAQ, About, publish gateway/page,
  lib/api (searchSkills/getSkill/getSkillDownloadUrl), BadgeSection (bundle-only)
- SEO/build: prerender, sitemap, feed, og-image, manifest, llms.txt -> bundles only

Docs:
- delete docs/skills/* and cli/skills.mdx; drop Skills sidebar section
- prune skill refs from index, ecosystem, quickstart, browsing, cli/*, registry/*

Verified: web typecheck, 60 tests, biome lint, docs build, web build, prerender
(10 routes, no skills) all green.
These 6 files under apps/docs/.astro/ were committed before the root
.gitignore added the .astro/ rule (.gitignore:10), so they have been
tracked by mistake and carried reorder churn on every docs build
(this PR otherwise showed 38 lines of Map-reorder noise in
content-modules.mjs). astro build regenerates the whole .astro/ dir, so
untracking them is safe and removes the churn + future merge conflicts.
No .gitignore change needed; the ignore rule already exists.
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