first-flag

Create and toggle a boolean LaunchDarkly flag to verify end-to-end behavior.

25|8|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/launchdarkly/ai-tooling --skill first-flag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: first-flag
Source: https://github.com/launchdarkly/ai-tooling/tree/main/skills/onboarding/first-flag
Command: npx skills add https://github.com/launchdarkly/ai-tooling --skill first-flag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides onboarding by enabling users to create, evaluate, and toggle a boolean LaunchDarkly flag to demonstrate end-to-end behavior in a real project.

Core Features & Use Cases

  • Create a boolean first flag and define its evaluation context for demos.
  • Evaluate the flag in code to verify ON/OFF behavior across environments.
  • Toggle the flag using MCP, API, or ldcli to validate end-to-end wiring during setup.

Quick Start

Create a new boolean flag named "first-flag" and toggle it on to verify end-to-end behavior.

Frequently Asked Questions about first-flag

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create and toggle my first LaunchDarkly feature flag?

To create your first LaunchDarkly feature flag, you create a boolean flag and toggle it on to verify end-to-end behavior across your project environments using MCP, API, or ldcli workflows.

What is feature flag evaluation and how does it work during onboarding?

Feature flag evaluation verifies ON/OFF behavior in code during LaunchDarkly onboarding. It defines an evaluation context for a boolean flag to demonstrate its end-to-end behavior in a real project setup.

Do I need an SDK installed to create a LaunchDarkly flag with ldcli?

Yes, creating and validating a LaunchDarkly flag requires SDK installation and project access as prerequisites. The flag workflow enforces these prerequisites before supporting MCP, API, or ldcli flag creation.

Can I use MCP to toggle a LaunchDarkly flag for end-to-end validation?

Yes, you can use MCP to toggle a LaunchDarkly flag and validate end-to-end wiring during setup. The workflow supports toggling flags through MCP, API, or ldcli to verify behavior across environments.

What's the best way to validate feature flag wiring across environments?

The best way to validate feature flag wiring is to create a boolean flag, evaluate it in code to verify ON/OFF behavior, and toggle it using MCP, API, or ldcli to confirm end-to-end functionality across environments.