Sdk Install

Walks you through installing the right LaunchDarkly SDK by running three nested skills in sequence: detect your stack, generate a plan, then apply the changes. Part of a larger onboarding flow, so it stops after wiring up the SDK and doesn't create sample flags. Handles dual-SDK scenarios like Next.js where you need both server and client packages, respects monorepo boundaries, and won't hardcode keys into your source. The blocking decision points mean you'll get asked before it changes dependencies or writes secrets. If your project already has LaunchDarkly initialized, the parent flow should skip this entirely.

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

View on GitHub

Install

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

Installs into .claude/skills of the current project.

Files

LaunchDarkly SDK Install (onboarding)

Installs and initializes the right LaunchDarkly SDK for the user’s project by following three nested skills in order. Do not skip ahead to feature flags here—the parent LaunchDarkly onboarding continues with Step 4: First flag.

Prerequisites

Project context from parent Step 1: Explore the Project (reuse it; only re-run deep detection if something is unclear)
SDK key / client-side ID / mobile key: Needed when you reach Apply code changes (env wiring). Do not ask the user for these during detect or plan solely because you opened this skill—follow parent onboarding: account status is inferred via MCP OAuth when MCP is already configured, or surfaced at D7 in apply; key material is collected at apply (see parent Prerequisites).