fix(skills): drop first-class "default API key" framing (0.6.2)#24
Merged
Conversation
The monorepo backend never shipped is_default as a first-class concept (it was reverted in mono#330 after a design review), and the API returns the full key value on every read by design. The skill prose here had leaked both assumptions — correct them so the agent doesn't promise behavior the platform doesn't provide. - The "Default" key is just a name — created during onboarding for UX but ordinary on every other axis (deletable, renameable, no flag). - API key values are visible on every read. Treat them as sensitive in agent output (no commits, no logs) but don't claim last-4-only masking. - workspaces.md: API tokens are per-org, not per-workspace. Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Summary
Strips the "permanent default API key" framing from the
devhelm-manageskill docs. The mono API revertedis_defaultafter a design review (devhelmhq/mono#330) — the starter key minted during onboarding is an ordinary key named "Default" with no special backend treatment. It can be renamed, revoked, deleted, and rotated like any other key.Also corrects the prose around key visibility: the API returns the full
keyvalue on every read (list, get, create, regenerate). The skill was claiming last-4-only masking, which doesn't match the platform.Changes
skills/devhelm-manage/SKILL.md— reframe starter key section; update sensitivity rule (treat as sensitive in output, don't promise masked reads).skills/devhelm-manage/references/api-keys.md— remove "default key is permanent/non-deletable" claims; update create/list JSON examples; note rotation via both new-key-then-revoke andregeneratepatterns.skills/devhelm-manage/references/workspaces.md— clarify tokens are per-org, not per-workspace.Test plan
npm run build— clean.npm run lint— clean.npm run typecheck— clean.npm test— 893 passing.Ready for the usual release flow: merge → integration tests → manual npm publish approval.
Made with Cursor