Create a boolean first flag, add evaluation, toggle on/off for end-to-end proof. Parent onboarding Step 6; uses MCP, API, or ldcli; optional flag-create skill.
Create first feature flag The SDK is connected. Now help the user create their first feature flag and see it work end-to-end. This skill is nested under LaunchDarkly onboarding; the parent Step 6 is first flag. Prior: Apply code changes. Optional -- Flag Create skill already installed: If the launchdarkly-flag-create skill from github.com/launchdarkly/ai-tooling is available in the session (install with npx skills add launchdarkly/ai-tooling --skill launchdarkly-flag-create -y --agent <agent>), you may use it for creating the flag and choosing evaluation code that matches the repo. You must still complete default off -> verify OFF -> toggle on -> verify ON (Steps 3-5 below). Do not require that skill: this page stays the full fallback when it is missing or MCP-only flows conflict with the user's setup. Security: Credential handling Never substitute literal token values into commands. Use environment variable references instead: Shell commands: $LAUNCHDARKLY_ACCESS_TOKEN (expanded by the shell, not visible in ps output) Set the variable in your session: export LAUNCHDARKLY_ACCESS_TOKEN=<your-token> This prevents tokens from appearing in process lists, shell history, and screen recordings. Step 0: Consult SDK flag-key guidance
don't have the plugin yet? install it then click "run inline in claude" again.