CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

launchdarkly-flag-create

Create and configure LaunchDarkly feature flags in a way that fits the existing codebase. Use when the user wants to create a new flag, wrap code in a flag, add a feature toggle, or set up an experiment. Guides exploration of existing patterns before creating.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable instruction-only skill: a clear five-step workflow with an explicit verification checklist, concrete decision tables and update instructions, and appropriate use of two real one-level-deep reference files. It is held back slightly by duplicated MCP-tool listings, a missing inline create-flag example, no error-recovery loop in the verify step, and cross-references to a sibling skill that is absent from this bundle.

Suggestions

Add a short error-recovery loop to the Verify step (e.g., "If the build/lint fails or get-flags shows wrong configuration, fix and re-check before proceeding") to reach explicit feedback-loop coverage.

Include a minimal inline `create-flag` example payload (or a one-line pointer with the exact shape) in Step 3, mirroring the concrete `update-flag` instruction table.

Fix the duplicated `get-flags` entry under both Required and Optional MCP tools, and either include the `launchdarkly-flag-targeting` bundle or clearly mark its references as depending on a sibling skill so navigation does not dead-end.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — no space is spent explaining what feature flags or LaunchDarkly are — with concrete detail like search strings ("launchdarkly", "ldclient") and file names ("package.json", "go.mod"). A few trimmable instances remain: the meta intro "You're using a skill that will guide you through…", filler like "This is a safety feature", and `get-flags` duplicated under both Required and Optional MCP tools. Minor over-explanation, matching anchor 4 rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Mostly executable guidance: a user-intent-to-flag-kind decision table, a key-generation example ("New Checkout Flow" -> `new-checkout-flow`), and copy-paste-ready update instructions like `{kind: "updateName", value: "New Name"}`. The main gap is that Step 3's creation step only says "Use `create-flag` with the configuration determined in Step 2" with no example payload inline, so it falls just short of anchor 5's fully copy-paste-ready coverage of common cases.

4 / 5

Workflow Clarity

A clear five-step sequence (explore → determine type → create → add evaluation code → verify) with an explicit four-item verification checklist ("Run the project's build or lint step", "Use `get-flags` to confirm", both code paths, safe default). However, there is no error-recovery feedback loop (no "if verification fails, fix and re-run" guidance), which anchor 5 requires — matching anchor 4's 'clear sequence with most checkpoints, minor validation gaps'.

4 / 5

Progressive Disclosure

Good structure against the actual bundle: detail is split into two real, one-level-deep references (`references/flag-types.md` and `references/sdk-evaluation-patterns.md`, both present and relevant), each clearly signaled at point of use and again in a References section with descriptions. The minor organization gap is the three references to `../launchdarkly-flag-targeting/` (SKILL.md and context-availability.md), which do not resolve in this bundle, keeping it below anchor 5's 'easy navigation'.

4 / 5

Total

16

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description in third-person voice: it states concrete capabilities, includes an explicit 'Use when…' clause with natural trigger phrases, and carves out a distinct LaunchDarkly niche. Its only weaknesses are a few missing natural synonyms (kill switch, rollout) and slight overlap risk with the sibling flag-targeting skill.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Create and configure LaunchDarkly feature flags", "wrap code in a flag", "add a feature toggle", "set up an experiment" — with only minor coverage gaps (verification and metadata updates are unmentioned). It exceeds the 1-2 actions of anchor 3 but lacks the comprehensive coverage of anchor 5.

4 / 5

Completeness

Explicitly answers both questions: the "what" is "Create and configure LaunchDarkly feature flags in a way that fits the existing codebase" and the "when" is a concrete "Use when the user wants to create a new flag, wrap code in a flag, add a feature toggle, or set up an experiment." This directly matches the anchor-5 pattern of clear what-and-when with concrete trigger phrases; anchor 4's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ("create a new flag", "add a feature toggle", "set up an experiment"), plus "feature flags" and "LaunchDarkly". A few natural terms are missing (e.g., "kill switch", "rollout", "feature switch"), so it fits anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"LaunchDarkly feature flags" establishes a clear niche that most skills would not collide with, but triggers like "set up an experiment" and "add a feature toggle" have minor overlap risk with closely related flag-targeting/rollout skills (this skill family includes a separate targeting skill). Mostly distinct with minor overlap, matching anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 suspicious

Warning

Total

15

/

16

Passed

Repository

launchdarkly/ai-tooling

Path

skills/feature-flags/launchdarkly-flag-create/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.