bama
BAMA: 모든 Mac 앱을 만들 수 있습니다
launchdarkly/ai-tooling에서 제공하는 54가지 에이전트 스킬
54 agent skills from launchdarkly/ai-tooling — including onboarding, launchdarkly-flag-discovery, launchdarkly-flag-create. Install with npx skills add launchdarkly/ai-tooling.
스킬JavaScript · TypeScriptGitHub @launchdarkly온라인운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기LaunchDarkly's official AI tooling
저장소 README에서 가져옴
README 전체를 불러오는 중입니다.
README 전문 보기 ↗LaunchDarkly's public collection of agent skills and playbooks. These skills encode repeatable workflows for working with LaunchDarkly, so coding agents can execute common tasks safely and consistently.
Agent Skills are modular, text-based playbooks that teach an agent how to perform a workflow. This repo is designed to be a public, open-source home for LaunchDarkly skills and to align with the emerging Agent Skills Open Standard.
| Skill | Description |
|---|---|
feature-flags/launchdarkly-flag-command | Resolve /flag style requests into fast flag lookup, detail, and disambiguation |
feature-flags/should-flag-change | Advisory, read-only call on whether a code change (diff/PR) should ship behind a feature flag |
feature-flags/launchdarkly-flag-discovery | Audit flags, find stale/launched flags, and assess removal readiness |
feature-flags/launchdarkly-flag-create | Create new feature flags in a way that fits existing codebase patterns |
feature-flags/launchdarkly-flag-targeting | Control targeting, rollouts, rules, and cross-environment config |
feature-flags/launchdarkly-flag-cleanup | Safely remove flags from code using LaunchDarkly as the source of truth |
feature-flags/launchdarkly-flag-drift | Detect and reconcile drift between an in-code SDK fallback default and the LaunchDarkly default rule |
feature-flags/launchdarkly-guarded-rollout | Configure guarded rollouts with progressive traffic, metric monitoring, and rollback |
feature-flags/flag-release | Record a flag's automated release for a PR, honoring release intent and per-environment release policies |
feature-flags/flag-and-release-change | End-to-end PR orchestrator: decide → create + wire the flag → record its release (composes the skills above) |
feature-flags/launchdarkly-flag-qualitative-feedback-setup | Add a qualitative user feedback widget tied to a flag, adapting to the project's framework and design system |
| Skill | Description |
|---|---|
release-autopilot/launchdarkly-release-autopilot-settings | Turn on GitHub App auto-flagging / auto-releasing, map owner/name repos, or diagnose why a PR was not classified (confirm before every write) |
| Skill | Description |
|---|---|
agentcontrol/configs-create | Create configs with variations for agent or completion mode |
agentcontrol/migrate | Migrate an app with hardcoded LLM prompts to AgentControl in five stages (extract, wrap, tools, tracking, evals) |
agentcontrol/configs-update | Update and delete configs, manage lifecycle |
agentcontrol/configs-variations | Manage config variations for A/B testing |
agentcontrol/tools | Create and attach tools for function calling |
agentcontrol/projects | Create and manage projects to organize configs |
agentcontrol/online-evals | Attach LLM-as-a-judge evaluators to configs |
agentcontrol/configs-targeting | Configure targeting rules for config rollouts |
agentcontrol/snippets | Create and manage reusable prompt snippets across configs |
agentcontrol/agent-graphs | Create and manage multi-agent graphs with routing and handoffs |
| Skill | Description |
|---|---|
experiments/launchdarkly-experiment-guide | Guided experiment setup: find what to test, propose a hypothesis and metric, wire the flag, then draft and create the experiment |
experiments/launchdarkly-experiment-setup | Set up experiments with metrics, treatments, and data collection |
| Skill | Description |
|---|---|
metrics/launchdarkly-metric-choose | Select the right metric type for an experiment |
metrics/launchdarkly-metric-create | Create metrics and instrument tracking events |
metrics/launchdarkly-metric-instrument | Add tracking calls to code for existing metrics |
| Skill | Description |
|---|---|
aws-devops-agent/experiment-orchestration | Take a product goal through a LaunchDarkly experiment and a rollout (guarded, if the plan has it) in AWS DevOps Agent. ldcli aws-devops-agent setup installs it with the experiment-orchestrator custom agent. See skills/aws-devops-agent. |
This repo is a Claude Code plugin. Installing it gives you all the skills above plus the LaunchDarkly MCP server.
/plugin marketplace add launchdarkly/ai-tooling
/plugin install launchdarkly@launchdarkly-ai-tooling
Once installed, skills are available as /launchdarkly:<skill-name> across all your projects, and the MCP server can read and modify your flags directly.
| Skill | Description |
|---|---|
onboarding | End-to-end LaunchDarkly setup: quiet scripted flow, SDK install, first flag with a live reveal, MCP offered afterwards |
onboarding/mcp-configure | Configure the LaunchDarkly hosted MCP server (OAuth, no API keys needed) |
onboarding/sdk-install | Install and initialize the correct SDK via detect, plan, and apply sub-steps |
This repo is a Cursor plugin. Installing it gives you all the skills above plus the LaunchDarkly MCP server, so the agent can read and modify your flags directly.
https://github.com/launchdarkly/ai-tooling
Once installed, the skills and MCP server are available across all your projects.
# Clone the repo
git clone https://github.com/launchdarkly/ai-tooling.git
cd ai-tooling
# If your agent supports skills.sh installs:
npx skills add launchdarkly/ai-tooling
# Or manually copy a skill into your agent's skills path:
cp -r skills/feature-flags/launchdarkly-flag-cleanup <your-agent-skills-dir>/
Then ask your agent something like:
Which feature flags are stale and should be cleaned up?
Create a feature flag for the new checkout flow
Roll out dark-mode to 25% of users in production
Remove the `new-checkout-flow` feature flag from this codebase
npx skills add <owner/repo>
See CONTRIBUTING.md for how to add new skills and the conventions we follow.
Apache-2.0