Skip to content

feat(menu): say which projects a skill serves in its tags alone - #538

Draft
edwinyjlim wants to merge 1 commit into
dag/m2-delete-old-step-skillsfrom
dag/m3-delete-old-menu-fields
Draft

edwinyjlim wants to merge 1 commit into
dag/m2-delete-old-step-skillsfrom
dag/m3-delete-old-menu-fields

Conversation

@edwinyjlim

Copy link
Copy Markdown
Member

What this does

A skill's menu entry says which projects it serves in its tags, and nowhere else.

{
  "id": "integration-nextjs-app-router",
  "name": "PostHog integration for Next.js App Router applications",
  "downloadUrl": "…/integration-nextjs-app-router.zip",
  "title": "Next.js App Router",
  "description": "PostHog integration for Next.js App Router applications",
  "tags": ["nextjs", "react", "…", "framework:nextjs", "frameworkVariant:app-router", "integration", "default"]
}
  • An entry has id, name, downloadUrl, title, description and tags. A step skill also has frameworkReferences.
  • The framework a skill serves is its framework:<id> tag, and its default mark is the default tag. Its group is the category it is listed under in categories, with / read as -. The tags and the categories are the ones a release carries today.
  • An entry has no group, framework or default field.
  • cliEntries is unchanged, including the default of a command family.

Every skill publishes as its own zip:

  • A group cannot be packaged as one JSON of its variants. packaging: bundle, the bundle writer, the dev server's /skills/<group>.json route and the group JSON upload step in build-release.yml are gone.
  • A group cannot borrow another group's variants. variants_from is gone. No config sets either key.
  • The old-wizard compatibility test and its snapshot are gone, since they check resolution by the removed fields.

Nothing inside context-mill reads an entry's group, framework or default: the manifest, the marketplace generator, the mirror and the dev server work from the skill list or from downloadUrl.

Verification

  • npm test: 368 tests pass.
  • The build passes, and scripts/mirror-dist.js runs on its output.
  • A build of this branch was compared with a build of the branch below it, both from a clean checkout. Only skill-menu.json differs: across its 254 entries, group is gone from 254, framework from 108 and default from 31. Every entry's tags are the same, and so is cliEntries. No skill zip, the manifest, the MCP archive or the marketplace tree differs.

Rollout

Stacked on the step skill removal.

A wizard that picks a skill by an entry's group, framework and default fields finds none once this ships. Merge it only when all of these hold:

  • cloud runs a wizard release that reads a skill's group from its category, and its framework and default from its tags
  • older wizard versions have drained from the run data
  • wizard-agent-dag and wizard-agent-dag-skills are both still on
  • the marketplace and MCP server owners have agreed

🤖 Generated with Claude Code

A skill's menu entry carries `id`, `name`, `downloadUrl`, `title`,
`description` and `tags`, and `frameworkReferences` where a step skill sets
it. The framework a skill serves, its group and its `default` mark are tags.
The entry has no `group`, `framework` or `default` field.

Every skill publishes as its own zip. A group cannot be packaged as one
JSON of its variants, and cannot borrow another group's variants.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@edwinyjlim
edwinyjlim added this pull request to stack #539 November 17, 2026 01:10
@github-actions

Copy link
Copy Markdown

🧙 Wizard CI

Run the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands:

Test all apps:

  • /wizard-ci all

Test all apps in a directory:

  • /wizard-ci ai-observability
  • /wizard-ci basic-integration
  • /wizard-ci feature-flags
  • /wizard-ci mcp-analytics
  • /wizard-ci replay-vision
  • /wizard-ci revenue
  • /wizard-ci self-driving
  • /wizard-ci warehouse
  • /wizard-ci warehouse-seeded

Test an individual app:

  • /wizard-ci ai-observability/anthropic
  • /wizard-ci ai-observability/google-adk
  • /wizard-ci ai-observability/groq
Show more apps
  • /wizard-ci ai-observability/manual-capture
  • /wizard-ci ai-observability/openai
  • /wizard-ci ai-observability/openai-agents
  • /wizard-ci ai-observability/opentelemetry
  • /wizard-ci ai-observability/vercel-ai
  • /wizard-ci basic-integration/android
  • /wizard-ci basic-integration/angular
  • /wizard-ci basic-integration/astro
  • /wizard-ci basic-integration/django
  • /wizard-ci basic-integration/fastapi
  • /wizard-ci basic-integration/flask
  • /wizard-ci basic-integration/flutter
  • /wizard-ci basic-integration/javascript-node
  • /wizard-ci basic-integration/javascript-web
  • /wizard-ci basic-integration/laravel
  • /wizard-ci basic-integration/next-js
  • /wizard-ci basic-integration/nuxt
  • /wizard-ci basic-integration/python
  • /wizard-ci basic-integration/rails
  • /wizard-ci basic-integration/react-native
  • /wizard-ci basic-integration/react-router
  • /wizard-ci basic-integration/sveltekit
  • /wizard-ci basic-integration/swift
  • /wizard-ci basic-integration/tanstack-router
  • /wizard-ci basic-integration/tanstack-start
  • /wizard-ci basic-integration/vue
  • /wizard-ci feature-flags/django
  • /wizard-ci feature-flags/next-js
  • /wizard-ci mcp-analytics/custom-dispatcher
  • /wizard-ci mcp-analytics/go-sdk
  • /wizard-ci mcp-analytics/python-sdk
  • /wizard-ci mcp-analytics/ruby-sdk
  • /wizard-ci mcp-analytics/rust-sdk
  • /wizard-ci mcp-analytics/typescript-sdk
  • /wizard-ci replay-vision/javascript-node
  • /wizard-ci replay-vision/next-js
  • /wizard-ci replay-vision/react-vite
  • /wizard-ci revenue/stripe
  • /wizard-ci self-driving/astro
  • /wizard-ci self-driving/fastapi
  • /wizard-ci self-driving/nuxt
  • /wizard-ci self-driving/react-router
  • /wizard-ci self-driving/sveltekit
  • /wizard-ci warehouse/monorepo-env
  • /wizard-ci warehouse/multi-source-next
  • /wizard-ci warehouse/stripe-node
  • /wizard-ci warehouse/zero-source
  • /wizard-ci warehouse-seeded/next-stripe
  • /wizard-ci warehouse-seeded/next-stripe-declined

Test against a wizard branch:

  • /wizard-ci all wizard:my-branch

Add wizard:<branch> to any command above to pin the wizard branch. It defaults to main.

Results will be posted here when complete.

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