Trim duplicated vercel flags CLI docs from flags-sdk skill - #492
Merged
vincent-derks merged 12 commits intoSep 3, 2026
Conversation
Point agents at --help for syntax and keep lifecycle/safety guidance that skills must own (EXP-3411).
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Drop duplicate CLI trigger phrases; keep subcommand names once for activation.
Make --help discovery and the vercel-cli cross-link explicit in SKILL.md and providers.md.
feugy
approved these changes
Sep 3, 2026
feugy
left a comment
feugy
left a comment
Member
There was a problem hiding this comment.
I'm not very used to writing skill, so maybe having repetition is better. But maybe a shorter skill with internal reference works well?
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
2 participants
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.
Summary
vercel flagssubcommand table and option-annotated examples fromreferences/providers.md;--helpowns syntax--helpcannot say, each bullet sourced from vercel.com/docs/flags or flags-sdk.dev:identify()↔--byentity attributes, kind → type,defaultValuefor archived/draft flags, static value vs targeting mode, embedded definitions /prepare,override↔FLAGS_SECRET, the roll-out / A/B / clean-up flowsvercelAdapter()uses Vercel OIDC by default,vercel env pullprovides it locally, SDK keys (FLAGS) are the manual path, activation provisionsFLAGS_SECRET(verified in vercel/apiactivate.ts)Siblings: EXP-3424 (vercel/vercel skill), EXP-3425 (vercel-plugin sync), EXP-3427 (flags-sdk.dev auth docs)
Test plan
providers.mdlinks to the doc page it comes from; spot-check two against the page--flagoption examples remain in the CLI sectionnode scripts/validate-skills.mjspasses