Conversation
Both links the skill gives a user during onboarding point at pages that do
not exist, so the two moments where it hands off to a human — fetch your SDK
key, go flip the flag — are exactly the two moments it breaks.
SDK keys. The page is Organization settings -> SDK keys, which takes the
project and environment as query parameters rather than as a path:
- /projects/{projectKey}/settings/environments/{envKey}/keys
+ /settings/sdk-keys?projKey={projectKey}&envKey={envKey}
The same page carries pickers for both, so the partial forms in
sdk-install/apply now drop a parameter instead of pointing somewhere else
entirely.
Flag targeting. The path shape is different, and LaunchDarkly's own API is
the authority here: get-flag returns
"url": "https://app.launchdarkly.com/default/local/features/ld-example-..."
so the canonical form is /{projectKey}/{envKey}/features/{flagKey}, not
/projects/{projectKey}/flags/{flagKey}/targeting?env={envKey}.
Found while onboarding a real project. Verified against a live account:
the SDK keys page by using it, the flag URL against the API response for a
flag that was toggled through it.
Not changed: the flag-create URL in step 4
(/projects/{projectKey}/flags/new?key={flagKey}) is likely wrong by the same
reasoning, but I have not verified it and did not want to guess.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Author
|
Closing this — not pursuing it on our side. The URL corrections still stand if they're useful to anyone: the SDK keys page is /settings/sdk-keys?projKey=X&envKey=Y, and the flag page is /{projectKey}/{envKey}/features/{flagKey} per get-flag's own url field. Feel free to take them or ignore them. |
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
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.
Both links the onboarding skill gives a user point at pages that don't exist. Unluckily, they're the two moments the skill hands off to a human — fetch your SDK key and go flip the flag — so the failure lands exactly where the user is already doing manual work.
Found while onboarding a real project, and verified against a live account.
SDK keys page
The page is Organization settings → SDK keys, which takes the project and environment as query parameters rather than as a path segment:
That page carries pickers for both project and environment, so the partial forms in
sdk-install/apply/SKILL.md(project known but not environment; neither known) now drop a query parameter and tell the user to use the picker, instead of pointing at a different page.Verified by using it to retrieve four server-side SDK keys.
Flag page
Different path shape, and the API is the authority here —
get-flagreturns:So the canonical form is
/{projectKey}/{envKey}/features/{flagKey}:Verified against the API response for a flag that was then toggled through that URL.
Not changed
The flag-create URL in step 4,
/projects/{projectKey}/flags/new?key={flagKey}, is likely wrong by the same reasoning. I haven't verified it and didn't want to guess in your repo — worth a look while you're here.Scope
Five URL strings across two files. No catalog regeneration: per CONTRIBUTING that's for new skills, and these URLs appear nowhere else in the repo.
🤖 Generated with Claude Code
Note
Overview
Updates broken LaunchDarkly dashboard handoff links in the onboarding and SDK apply skills so manual steps (SDK keys and first-flag reveal) land on real pages.
SDK keys: Replaces project/environment path URLs with Organization settings → SDK keys query forms (
/settings/sdk-keyswithprojKey/envKey). The apply skill’s partial-key cases now use the same page with fewer query params and instruct users to use the on-page pickers.Flags: Replaces
/projects/.../flags/.../targeting?env=...with the/{projectKey}/{envKey}/features/{flagKey}shape (flip-in-dashboard and wrap-up links in onboarding).Documentation-only; five URL strings across two markdown skill files. Flag-create URL in step 4 is unchanged in this PR.
Reviewed by Cursor Bugbot for commit 9dfce0d. Bugbot is set up for automated code reviews on this repo. Configure here.