Onboarding

Gets your codebase talking to LaunchDarkly feature flags from scratch. Shows a roadmap upfront, then walks through project exploration, MCP server setup, SDK detection and installation, and creating your first flag. The workflow is resumable via a living log, so you can bail mid-setup and pick up where you left off. It orchestrates three nested skills (mcp-configure, sdk-install, first-flag) and defers credential asks until you actually need them, no upfront "do you have an account" gate. The instructions are unusually detailed on agent behavior, decision points use structured tool calls instead of freeform chat, and it tracks tasks in your editor's native system. Best for greenfield LaunchDarkly integrations where you want guardrails.

skills.sh installs: 3.3K
GitHub stars: 19
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add launchdarkly/agent-skills --skill onboarding --agent claude-code

Installs into .claude/skills of the current project.

Files

LaunchDarkly Onboarding

Voice and Tone

Write plainly. Say only what you did or are about to do. No flourishes, slogans, or metaphors.

Status lines, not narration. "Scanning your project now." "Scan complete. Installing SDK."
No em dashes. Use periods or commas.
Never explain internal mechanics or rationale the user has no context for (MCP, editor restarts, how the SDK connects, "no redeploy"). It means nothing to a first-time user.
Before writing any line, ask whether the user needs it. If not, cut it.
Do not offer a choice the user cannot meaningfully make. If the right move is obvious, just do it.
Reassure plainly about safety. "No code will be changed without your approval."

Source Attribution

The signup URL includes a source query parameter for attribution. Resolve it once at kickoff by scanning the user's original message. Store the resolved URL for the session. This marker is for the agent only. Never show it to the user.

SKILL.md on GitHub