CtrlK
BlogDocsLog inGet started
Tessl Logo

launchdarkly-flag-drift

Detect and reconcile drift between a feature flag's in-code SDK fallback default and its LaunchDarkly default rule (fallthrough). Use when a flag's default rule changed, when the user asks to detect flag drift, check whether a hardcoded default still matches LaunchDarkly, sync an in-code default, or open a PR reconciling a fallback value, without removing the flag or its evaluation.

76

Quality

96%

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

92%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.

The body is a well-structured, actionable workflow with clear validation checkpoints and proper progressive disclosure to real reference files. Its only weakness is moderate redundancy around the cross-environment divergence case, which slightly inflates the token budget.

Suggestions

Consolidate the cross-environment divergence guidance so it is stated once authoritatively (e.g. in the Edge Cases table) and merely referenced elsewhere, reducing repetition across the Core Concept, Step 2, Step 4, and What NOT to Do sections.

Consider moving the repeated 'do not remove the flag / change evaluation logic' prohibitions into a single canonical list rather than restating them in the Core Concept, Step 5, and What NOT to Do.

DimensionReasoningScore

Conciseness

Dense, expert-grade prose that assumes Claude's competence and avoids explaining basic SDK/LaunchDarkly concepts, but the cross-environment divergence point is repeated across the Core Concept, Step 2, Step 4, Edge Cases, and What NOT to Do sections and could be tightened.

4 / 5

Actionability

Provides concrete MCP tool names (get-flag, get-environments), an executable before/after TypeScript example, decision tables mapping results to actions, and a precise structured-summary schema — fully actionable.

5 / 5

Workflow Clarity

Eight clearly sequenced steps with explicit validation checkpoints (Step 6 hard-stop, Step 4 decision matrix with feedback loops) covering an edit operation, satisfying the validation requirement for destructive changes.

5 / 5

Progressive Disclosure

SKILL.md acts as a concise overview with well-signaled one-level-deep references to real bundle files (references/sdk-default-patterns.md, references/pr-template.md) and two sibling-skill links, keeping the main body navigable.

5 / 5

Total

19

/

20

Passed

Description

100%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.

The description is precise, complete, and clearly scoped, naming concrete actions alongside explicit "Use when" triggers and a scope constraint. It is among the strongest examples in the rubric.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete actions — "Detect and reconcile drift", "sync an in-code default", and "open a PR reconciling a fallback value" — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both "what" (detect and reconcile drift between fallback default and fallthrough) and "when" via a concrete "Use when..." clause with multiple triggers, plus a scope constraint.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ("detect flag drift", "sync an in-code default", "default rule changed", "open a PR reconciling a fallback value") with good synonym coverage.

5 / 5

Distinctiveness Conflict Risk

Highly specific to LaunchDarkly fallback-default drift with a clear niche and distinct triggers, minimizing overlap with sibling flag-cleanup or flag-targeting skills.

5 / 5

Total

20

/

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: 2 suspicious

Warning

Total

15

/

16

Passed

Repository
launchdarkly/ai-tooling
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.