Repository navigation
skills(flags-sdk): trigger on any feature-flag task and route by stack - #554
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
vincent-derks
approved these changes
Oct 13, 2026
This branch was successfully deployed
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.
Broadens the
flags-sdkskill description so agents load it for any feature-flag task, and adds a short section that picks the right integration for the project's stack.Why
Agents pick a skill by reading its description. The current one opens with "the Flags SDK (
flagsnpm package)" and spends most of its ~990 characters (close to the 1024-character limit) listing CLI subcommands and provider names. When someone asks to "put this behind a flag", "add a kill switch", or "roll this out to 10% of users", especially outside Next.js or SvelteKit or before picking a library, the description doesn't obviously match, so the skill isn't loaded.Once loaded, the body also assumes Next.js or SvelteKit. The guidance for other frameworks (
@vercel/flags-core) is buried inreferences/providers.md.Approach
Because the description is the only trigger signal, rewriting it around user intent should get the skill loaded for more flag-related requests:
@vercel/flags-core, OpenFeature, provider adapters, Flags Explorer,vercel flagsCLI). The full subcommand list is left to the body and tovercel flags --help.@vercel/flags-corefor other frameworks, OpenFeature for provider portability. It also says to keep an existing provider and connect it through its adapter.The skill name is unchanged.
Validation
Core client in other frameworksheading inreferences/providers.md.Relevant context
vercel/vercel-plugin syncs this skill body into
skills/flags-sdk/upstream/and keeps its own frontmatter inoverlay.yaml. A companion PR, vercel/vercel-plugin#334, updates the overlay description to match. The body change will reach the plugin on its next resync.