CtrlK
BlogDocsLog inGet started
Tessl Logo

launchdarkly-flag-cleanup

Safely remove a feature flag from code while preserving production behavior. Use when the user wants to remove a flag from code, delete flag references, or create a PR that hardcodes the winning variation after a rollout is complete.

72

Quality

91%

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-engineered workflow: concrete tools, explicit safety gates, a real code transformation example, and proper offloading of SDK patterns and the PR template to reference files. Only minor conciseness trims are available, mostly redundancy between the intro, Core Principles, and What NOT to Do.

DimensionReasoningScore

Conciseness

The body is lean — it never explains what feature flags or LaunchDarkly are and offloads detail to reference files — but has minor trimmable redundancy: the intro paragraph re-states the description, and "What NOT to Do" repeats Core Principles 3 and 4. Fits anchor 4 rather than 5 because of these few redundant sentences.

4 / 5

Actionability

Fully concrete guidance throughout: named MCP tools ("check-removal-readiness", "get-flag"), a forward-value decision table mapping exact env states to actions, a copy-paste before/after TypeScript transformation, and named SDK search patterns. Matches anchor 5's fully-executable coverage of the common boolean-flag case.

5 / 5

Workflow Clarity

Seven clearly sequenced steps with explicit validation gates for this destructive operation: a readiness verdict (safe/caution/blocked), NOT-SAFE stop conditions in the forward-value table, a hard user-confirmation checkpoint ("Do not proceed with code changes until the user explicitly confirms"), and a Verify step covering build, lint, tests, and a final re-search. Full feedback loops match anchor 5.

5 / 5

Progressive Disclosure

SKILL.md is a clear overview and the bulk detail ("See [SDK Patterns](references/sdk-patterns.md)", the PR template) is split into well-signaled reference files that are one level deep and exist on disk. Matches anchor 5's clear-overhead, one-level-deep structure.

5 / 5

Total

19

/

20

Passed

Description

87%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 strong: it answers both what and when explicitly, uses natural trigger phrasing, and carves out a distinct niche. Its only weakness is trigger-term breadth — "LaunchDarkly" and "feature toggle" never appear, which slightly limits discoverability.

DimensionReasoningScore

Specificity

"Safely remove a feature flag from code while preserving production behavior", "delete flag references", and "create a PR that hardcodes the winning variation" name several concrete actions, with minor gaps (no mention of querying the flag service or archiving). Beyond anchor 3 (only 1-2 actions) but short of anchor 5's comprehensive coverage.

4 / 5

Completeness

"Safely remove a feature flag from code while preserving production behavior" answers what, and "Use when the user wants to remove a flag from code, delete flag references, or create a PR that hardcodes the winning variation after a rollout is complete" explicitly answers when with concrete triggers — the anchor-5 pattern.

5 / 5

Trigger Term Quality

"remove a flag from code", "delete flag references", and "after a rollout is complete" are natural user phrasings, but obvious terms like "LaunchDarkly" and synonyms such as "feature toggle" are missing. Good coverage without being comprehensive, matching anchor 4.

4 / 5

Distinctiveness Conflict Risk

Post-rollout flag removal is a clear niche with distinct triggers ("hardcodes the winning variation after a rollout is complete"), with minimal overlap risk against generic code-cleanup or sibling flag-targeting skills. Matches anchor 5.

5 / 5

Total

18

/

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: 3 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.