CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

launchdarkly-guarded-rollout

Configure guarded rollouts with progressive traffic increases, metric monitoring, and automatic rollback. Use when releasing features gradually with safety thresholds.

Quality

83%

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

82%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 strong, highly actionable skill body: executable JSON examples, exact tool parameters, and a well-sequenced workflow with pre-checks and a verify step. Remaining gaps are minor — some trimmable generic prose, no explicit recovery loop after verification, and reference material inlined in a single file.

Suggestions

Add an explicit feedback loop after Step 5 (e.g., "If verification fails or a regression notification arrives, call stop-guarded-rollout and report").

Trim the opening paragraph and the generic Core Principles items in favor of the concrete stage/metric tables that follow.

Consider moving the unit-conversion tables and tool parameter details into a single references file linked from SKILL.md.

DimensionReasoningScore

Conciseness

The body is dominated by domain-specific facts Claude would not know (thousandth-based rollout weights, millisecond monitoring windows, exact tool parameters), which is efficient — but the "You're using a skill that will guide you" intro and the partly generic "Core Principles" section ("Start Small", "Monitor What Matters") are minor over-explanations that could be trimmed. This places it at 4 rather than 5, and well above 3 since nearly all content is non-obvious.

4 / 5

Actionability

Fully executable, copy-paste-ready JSON payloads for `start-guarded-rollout` and `stop-guarded-rollout` cover the common cases, with exact tool names, required/optional tool lists, and concrete arguments in the edge-case table (`on: true`, `confirm: true`). Placeholder variation IDs are unavoidable since they are environment-specific, so no gap is charged.

5 / 5

Workflow Clarity

A clear five-step sequence (Prepare → Design Stages → Configure Metrics → Start → Verify) with pre-flight checks (flag on, no active rollout) and a verification step. It misses 5 because there is no explicit error-recovery loop if Step 5 verification fails or a regression notification arrives mid-rollout — the recovery path (stop, then what) is only implicit in the Edge Cases and Stopping sections.

4 / 5

Progressive Disclosure

No bundle files exist, and the single ~150-line document is well-sectioned with clear headers, a logical flow, and no buried or nested references. At 4 rather than 5 because the reference material (weight units, monitoring-window conversions, tool parameter details) is long enough that it could be split into a one-level-deep reference file to keep SKILL.md leaner.

4 / 5

Total

17

/

20

Passed

Description

75%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 solid description with an explicit "Use when..." clause and several concrete capabilities. Its main weaknesses are the missing platform/domain keywords (LaunchDarkly, feature flags, canary) that users would most naturally say, and a trigger clause that could name more concrete scenarios.

Suggestions

Add domain keywords users would naturally say, e.g. "Use when performing gradual or canary releases with LaunchDarkly feature flags"

Make the when-clause more concrete by naming the platform and artifacts, e.g. "Use when releasing a feature flag variation gradually in LaunchDarkly"

Optionally mention designing rollout stages and stopping rollouts to round out capability coverage

DimensionReasoningScore

Specificity

Lists several concrete actions — "Configure guarded rollouts", "progressive traffic increases", "metric monitoring", and "automatic rollback" — matching the several-specific-actions-with-minor-gaps anchor. It stays at 4 rather than 5 because the body also covers designing stages and halting rollouts, which the description omits.

4 / 5

Completeness

Both parts are present: the what ("Configure guarded rollouts with progressive traffic increases, metric monitoring, and automatic rollback") and an explicit when ("Use when releasing features gradually with safety thresholds"). The when-clause is generic, lacking concrete trigger phrases like "feature flags" or "LaunchDarkly", so it does not reach 5.

4 / 5

Trigger Term Quality

"releasing features gradually", "rollout", "safety thresholds", and "automatic rollback" are phrases a user would plausibly say, giving good keyword coverage. It falls short of 5 because natural terms like "LaunchDarkly", "feature flag", and "canary" are absent.

4 / 5

Distinctiveness Conflict Risk

"Guarded rollouts" plus "automatic rollback" carves a fairly distinct niche, but since the description never names LaunchDarkly or feature flags, it could overlap with generic canary/progressive-delivery skills — mostly distinct with minor overlap risk, hence 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

launchdarkly/ai-tooling

Path

skills/feature-flags/launchdarkly-guarded-rollout/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.