launchdarkly experimental-agent-skills
COMMUNITYLABSCO SUMMARY
onboardingV2 is the top-level, branded, fixed-sequence flow that walks a new LaunchDarkly customer through setup and enforces each step before advancing to the next. Nested inside it, sdk-install runs detect, plan, and apply in order: detect reads the repository's stack, frameworks, and any existing LaunchDarkly usage; plan chooses which SDK or SDK pair to install, including a dual server-and-client setup where one is needed; and apply installs it, wires up the init call, and verifies the project still compiles. mcp-configure is the flow's separate fourth step, wiring up LaunchDarkly's hosted MCP server over OAuth for Cursor, Claude Code, Windsurf, GitHub Copilot, and other MCP-capable agents.
Only detect runs with nothing configured, because it just reads a repository; the other five assume a LaunchDarkly account already exists, whether that means an account key already exported — for apply, onboardingV2, plan, and sdk-install itself — or adding LaunchDarkly's hosted MCP server, for mcp-configure. Nobody without a LaunchDarkly account gets anything from this repository.
READ THE FULL ANALYSIS
"Experimental" is not just a name. The readme states plainly that skills here "may change, be renamed, or be removed as they are refined," and that stable, production-ready versions are published separately in launchdarkly/ai-tooling — so anything installed from this repository should be expected to move or disappear rather than treated as a dependency to build on.
ALSO IN THIS PACKAGE
LaunchDarkly
Feature flags, AgentControl configs and observability — logs, traces, errors and dashboards.
http · https://mcp.launchdarkly.com/mcp/launchdarklyWHAT'S INSIDE
6 showing · 6 totalNothing else to set up — install it and go.
apply
The step where the code actually changes: the LaunchDarkly package gets installed, the startup code goes in, and your secret key goes wherever you say it should.
detect
Works out what the project is built with, where the app starts up, and whether LaunchDarkly is already in there — and asks you which app to target when it cannot tell.
mcp-configure
Connects your coding editor to your LaunchDarkly account so the assistant can list and switch feature flags itself, signing in through the browser instead of asking you for an access token.
onboardingV2
A guided first setup of LaunchDarkly that ends with a real on/off switch working in your own app, one you flip from a web dashboard and watch change on the running page.
plan
A short proposal written before anything is edited: which LaunchDarkly library suits this app, which files will be touched, and where the key will live.
sdk-install
Gets LaunchDarkly running inside an existing project in three passes: read the code, agree what will change, then change it and check the project still builds.
HOW TO GET IT
npx skills add launchdarkly/experimental-agent-skillsnpx skills add launchdarkly/experimental-agent-skills --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.