All skills
launchdarkly avatar

/projects

@ef54971 official

Guide for setting up LaunchDarkly projects in your codebase. Helps you assess your stack, choose the right approach, and integrate project management that makes sense for your architecture.

Use this Skill: https://skilld.dev/gh/launchdarkly/agent-skills/projects

This session only. Nothing lands on disk.

README.md

≈464 tokens on demand. Your agent reads this file only when SKILL.md points to it.

LaunchDarkly Config Projects Skill

An Agent Skill for setting up LaunchDarkly project management in a codebase. Guides exploration of the stack, assessment of the right approach, and integration that fits the architecture.

Overview

This skill teaches agents how to:

  • Explore the codebase to understand the tech stack and patterns
  • Assess what project setup approach makes sense
  • Choose the right implementation path (by language, use case, or tooling)
  • Create projects and save SDK keys via API or MCP
  • Verify the setup via API fetch and SDK integration test

Installation (Local)

For now, install by placing this skill directory where your agent client loads skills.

Examples:

  • Generic: copy skills/agentcontrol/projects/ into your client's skills path

Prerequisites

Choose one:

  • LaunchDarkly API access token with projects:write permission
  • LaunchDarkly MCP server configured in your environment

Usage

Once installed, the skill activates automatically when you ask about project setup:

Set up a LaunchDarkly project for our configs
Create a project for our customer support agent
Add LaunchDarkly project management to this codebase

Structure

projects/
├── SKILL.md
├── README.md
└── references/
    ├── quick-start.md
    ├── python-setup.md
    ├── nodejs-setup.md
    ├── go-setup.md
    ├── env-config.md
    ├── project-cloning.md
    ├── iac-automation.md
    ├── admin-tooling.md
    └── multi-language-setup.md

Related

License

Apache-2.0

Source: SKILL.md on GitHub

2 alerts2d3 checks · Risk HIGH
  • Gen Agent Trust Hub2d

    The skill facilitates LaunchDarkly project setup but performs high-risk operations, including instructions to automatically extract credentials from sensitive agent configuration files (~/.claude/config.json) and system environment variables. It also generates and executes local scripts to verify integrations, creating a potential path for local code execution.

  • Socket2d

    1 alert: gptAnomaly

  • Snyk2d

    Risk: HIGH · 1 issue

Signed by skilld at ef54971. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 3 days ago
metadata
{
  "author": "launchdarkly",
  "version": "0.4.0"
}
Other metadata
compatibility
Requires LaunchDarkly API access token with projects:write permission or LaunchDarkly MCP server.
  • Python
  • Go
  • Infrastructure
  • launchdarkly
  • project-setup
  • api-integration
  • nodejs
  • configuration-management
  • feature-flags
  • secrets-management

README badge

README badge for launchdarkly/agent-skills/projects

Guides setup of LaunchDarkly projects in a codebase by exploring the stack, assessing architecture, and choosing the right implementation path. Supports Python, Node.js, Go, and polyglot setups, with reference guides for quick setup, environment configuration, project cloning, and infrastructure automation.

Generated from the current SKILL.md.

What permissions do I need to set up LaunchDarkly projects?
Your API access token must have the projects:write permission, or you can use a LaunchDarkly MCP server configured in your environment instead.
Can the skill automatically detect my LaunchDarkly API key?
Yes. The skill checks for LAUNCHDARKLY_API_KEY, LAUNCHDARKLY_API_TOKEN, or LD_API_KEY environment variables, and also checks the Claude MCP config at ~/.claude/config.json before prompting you for the key.
What project key format is required?
Project keys must start with a letter, use only lowercase letters, numbers, and hyphens, and cannot contain uppercase letters, underscores, or dots.
Does this skill create the projects, or just guide me?
The skill guides you through the setup process and follows reference implementations for your tech stack (Python, Node.js, Go, etc.), but you choose which reference path to execute based on your architecture.
What should I do after projects are created?
After setup, verify the project exists and SDK keys are valid, then proceed to the configs-create skill to create feature flags or the sdk skill to integrate into your application.

Generated from the current SKILL.md. These answers refresh after source changes.