Back to Skills

onboarding

Onboard a project to LaunchDarkly: kickoff roadmap, resumable log, explore repo, MCP, companion flag skills, nested SDK install (detect/plan/apply), first flag. Use when adding LaunchDarkly, setting up or integrating feature flags in a project, SDK integration, or 'onboard me'.

17stars5forksUpdated 6/12/2026

Security Assessment

High Risk(30/100)

Detected risks:

Persistence([references/sdk/snippets/dotnet-client-sdk.md] LaunchD, [references/sdk/snippets/dotnet-client-sdk.md] launchd, [references/sdk/snippets/electron-client-sdk.md] LaunchD)
Sensitive File Access([references/sdk/snippets/ios-client-sdk.md] .env, [references/1.8-summary.md] .env, [references/sdk/snippets/javascript-browser-sdk.md] .env)
Security Score30/100

About onboarding

The onboarding skill guides users through integrating LaunchDarkly into an existing codebase using a structured, resumable workflow. It addresses the complexity of introducing feature flagging by providing a clear sequence of steps that begin with a kickoff roadmap and the creation of a living onboarding log. The workflow is designed so users can pause and resume progress across sessions, reducing friction during adoption. It also avoids unnecessary upfront requirements by deferring account verification and credential collection until they are actually needed in the process.

Its capabilities include exploring the target repository, detecting the coding agent environment, installing companion flag-management skills, configuring the LaunchDarkly MCP server early in the process, and orchestrating SDK installation through nested detect, plan, and apply stages. The skill can also guide users through creating their first feature flag. When MCP is configured, it can leverage optional tools to retrieve environment information, obtain SDK-related identifiers from a single source, create feature flags, and update flag configurations. If MCP is unavailable or declined, the workflow remains completable through documented fallback approaches.

This skill is intended for developers and teams introducing LaunchDarkly into new or existing projects. It is particularly useful for engineers setting up feature flags for the first time, teams standardizing onboarding practices, and users working with MCP-capable coding agents. Common scenarios include adding LaunchDarkly to an application, configuring SDK integrations, establishing initial feature-flag workflows, and responding to requests such as "onboard me" during project setup.

FAQ

When should I use the onboarding skill?

Use it when adding LaunchDarkly to a project, integrating feature flags, setting up an SDK, or when you want guided onboarding for LaunchDarkly adoption.

What are the compatibility requirements?

The skill requires an MCP-capable coding agent, a LaunchDarkly account, and npx available on the system PATH for optional companion skill installation.

Do I need a LaunchDarkly account before starting?

No. The workflow intentionally avoids asking about account status upfront. Early steps can proceed without an account, and account requirements surface naturally when relevant.

When are SDK keys or tokens required?

Keys and tokens are collected only when the workflow reaches steps that require them, such as SDK configuration or certain command-line and REST-based operations.

Can the onboarding process continue without MCP?

Yes. Although MCP configuration is the preferred approach, the workflow includes fallback paths using ldcli or REST-based methods so onboarding can still be completed.

All Files

32 files
references/sdk/snippets/dotnet-client-sdk.md1.1 KB
View
references/sdk/snippets/electron-client-sdk.md0.8 KB
View
references/sdk/snippets/flutter-client-sdk.md1.2 KB
View
references/sdk/snippets/go-server-sdk.md2.1 KB
View
references/sdk/snippets/ios-client-sdk.md4.5 KB
View
references/sdk/snippets/java-server-sdk.md3.4 KB
View
references/sdk/snippets/lua-server-sdk.md1.0 KB
View
references/sdk/snippets/node-client-sdk.md0.9 KB
View
references/sdk/snippets/php-server-sdk.md0.8 KB
View
references/1.8-summary.md7.0 KB
View
marketplace.json0.6 KB
View
references/sdk/recipes.md23.0 KB
View
references/sdk/snippets/apex-server-sdk.md0.7 KB
View
references/sdk/snippets/android-client-sdk.md4.0 KB
View
references/sdk/snippets/cpp-client-sdk.md0.9 KB
View
references/1.9-editor-rules.md10.3 KB
View
references/sdk/snippets/browser-frameworks-sdk.md1.0 KB
View
references/sdk/snippets/cpp-server-sdk.md0.6 KB
View
references/sdk/snippets/edge-sdks.md1.8 KB
View
references/sdk/snippets/dotnet-server-sdk.md3.3 KB
View
references/sdk/snippets/erlang-server-sdk.md0.8 KB
View
references/sdk/snippets/haskell-server-sdk.md0.8 KB
View
references/sdk/snippets/javascript-browser-sdk.md2.6 KB
View
references/sdk/snippets/node-server-sdk.md2.8 KB
View
references/sdk/snippets/python-server-sdk.md2.7 KB
View
references/sdk/snippets/roku-client-sdk.md0.6 KB
View
references/sdk/snippets/vue-client-sdk.md0.7 KB
View
references/sdk/snippets/react-native-sdk.md2.7 KB
View
references/sdk/snippets/ruby-server-sdk.md0.8 KB
View
SKILL.md29.3 KB
View
references/sdk/snippets/react-web-sdk.md2.7 KB
View
references/sdk/snippets/rust-server-sdk.md0.8 KB
View

Install onboarding

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill