Setting the skill. One moment.
Skills
Skill 48 of 49
Install and initialize the correct LaunchDarkly SDK during onboarding by running nested skills in order: detect, plan, apply.
2 minutes · 447 words · 8 sections
Install
npx skills add launchdarkly/ai-tooling --skill sdk-installnpx skills add launchdarkly/ai-tooling/plugin marketplace add launchdarkly/ai-toolingThe first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.
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 continues with .
49 skills · 220 min
| SDK Type | Variable (logical) | Source in LaunchDarkly |
|---|---|---|
| Server-side | LAUNCHDARKLY_SDK_KEY | Environments → SDK key |
| Client-side | Client-side ID (bundler-prefixed env names) | Environments → Client-side ID |
| Mobile | LAUNCHDARKLY_MOBILE_KEY | Environments → Mobile key |
Never hardcode keys. Full env rules, consent, and bundler tables: Apply code changes Step 2.
Execute all three unless the detect decision tree short-circuits (e.g. skip to apply only). Each nested skill may contain decision points — some blocking (marked D<N> -- BLOCKING, where you must call your structured question tool and wait for the user’s response before continuing) and some non-blocking (where you present information and continue unless the user objects). Do NOT batch tool calls across blocking boundaries.
| Order | Nested skill | Role |
|---|---|---|
| 1 | Detect repository stack | Language, package manager, monorepo target, entrypoint, existing LD usage |
| 2 | Generate integration plan | SDK choice, files to change, env plan – presented to user (non-blocking; see plan SKILL.md D6) |
| 3 | Apply code changes | Install package(s), .env / secrets with consent, init code, compile check (both tracks when dual-SDK plan) |
Shared references for all steps: SDK recipes (opens in a new tab), SDK snippets (opens in a new tab).
Continue with the parent skill:
Do not add standalone “sample flag” evaluation in this skill unless the user explicitly needs a throwaway check; the parent flow creates the first flag in order.
.env.example entries when the project uses dotenv.Install and initialize the correct LaunchDarkly SDK during onboarding by running nested skills in order: detect, plan, apply. Parent onboarding Step 4 is first flag.
The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.
skills/onboarding/sdk-install/SKILL.mdmain, last pushed 21 September 2026.SKILL.md, not by matching a directory convention. 8 distinct layouts observed: skills/agentcontrol/*/SKILL.md, skills/experiments/*/SKILL.md, skills/feature-flags/*/SKILL.md, skills/metrics/*/SKILL.md, skills/observability/*/SKILL.md, skills/onboarding/*/SKILL.md, skills/onboarding/sdk-install/*/SKILL.md, skills/*/SKILL.md.h1 and no skipped levels:.claude-plugin/marketplace.json by LaunchDarkly, declaring 1 plugin. It is read for editorial metadata only — never as the skill index, which is always the repository tree./launchdarkly/ai-tooling.md, and each skill at its own .md URL.