CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

flag-release

Record an automated rollout for an existing LaunchDarkly flag that guards a pull request's change, so the change releases safely when the PR merges. Honors a stated release intent (release now / hold / notBefore / segment / prerequisite) and defers per-environment to the project's release policies. Use as the release step once the guarding flag exists and its code is wired. Keywords: record release, automated rollout, release policy, guarded rollout, staged rollout, immediate vs policy, release intent, hold release, dark launch.

Quality

88%

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

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

Excellent actionability, workflow clarity, and progressive disclosure: exact tool calls, a worked JSON example, validation checkpoints with feedback loops, and a clean one-level reference split. The one weakness is conciseness — the hold-vs-policy warning, while the skill's key failure mode, is restated five times across sections and could be consolidated.

Suggestions

State the hold-vs-policy rule once, in the intro blockquote, and cross-reference it ("see the hold rule above") from the bucket table, Implement steps, and Edge Cases instead of restating the full explanation each time.

Trim the duplicated worked-example narration: Implement step 2's prose ("if you catch yourself wanting to add holdUntil...") largely repeats the bucket table; keep one formulation.

Merge overlapping Edge Cases rows ('User wants to hold, or set a notBefore date' duplicates guidance already in the hold rule and What NOT to Do) into a single row pointing at the hold rule.

DimensionReasoningScore

Conciseness

The body is domain-specific with no generic padding, but the critical hold warning ("policy is NOT a manual gate", "omit it from the environments array entirely") is repeated in the intro blockquote, the bucket table, Implement steps 1 and 2, Edge Cases, and What NOT to Do. That is meaningful redundancy that could be consolidated into one authoritative statement plus one cross-reference, matching the 3 anchor ("mostly efficient but could be tightened") rather than 4.

3 / 5

Actionability

Fully executable guidance: exact MCP tool names with parameters (`match-release-policies` with `projectKey`, `flagKey`, `environmentKey`), a copy-paste-ready JSON example for `create-automated-rollout-config`, a bucket table specifying exact entry shapes, and a verify step naming the returned fields (`created`, `config_id`). This covers the common cases concretely, matching the 5 anchor for an instruction-only skill.

5 / 5

Workflow Clarity

Clear Plan/Implement sequencing with explicit validation checkpoints: confirm the flag exists and is OFF via `get-flags`, preview each environment's policy before proposing, "Present the per-environment plan and stop" for confirmation with "revise on feedback", read back the `environmentKey`s before sending, verify the response, and a fail-closed rule ("if an environment's intent is unclear, it's HOLD"). Error recovery and edge cases are tabulated, matching the 5 anchor.

5 / 5

Progressive Disclosure

The body is a well-sectioned overview, and the full release model is appropriately split into a real one-level-deep reference (references/auto-release.md, verified to exist, ~100 lines, no nested content references), clearly signaled each time with a description of its contents. Navigation is easy, matching the 5 anchor.

5 / 5

Total

18

/

20

Passed

Description

88%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: third-person voice, concrete and comprehensive about capabilities, with an explicit use-when clause and a rich keyword list. The only gaps are a few missing natural trigger phrasings and minor keyword overlap with sibling LaunchDarkly skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Record an automated rollout for an existing LaunchDarkly flag", "Honors a stated release intent (release now / hold / notBefore / segment / prerequisite)", "defers per-environment to the project's release policies" — covering the skill's capabilities comprehensively. It exceeds the 4 anchor because no meaningful capability of the skill is left out.

5 / 5

Completeness

Both what ("Record an automated rollout for an existing LaunchDarkly flag ... honors a stated release intent ... defers per-environment to release policies") and when ("Use as the release step once the guarding flag exists and its code is wired") are explicitly stated with concrete trigger keywords. The when-clause is specific rather than generic, matching the 5 anchor.

5 / 5

Trigger Term Quality

"Keywords: record release, automated rollout, release policy, guarded rollout, staged rollout, immediate vs policy, release intent, hold release, dark launch" gives good natural-term coverage with synonyms (staged/guarded rollout, dark launch). It falls short of 5 because common user phrasings like "roll out my flag" or "release my feature flag" are absent.

4 / 5

Distinctiveness Conflict Risk

"existing LaunchDarkly flag" and the release-step positioning create a clear niche distinct from generic flag skills, but terms like "guarded rollout" and "release policy" have minor overlap risk with closely related sibling skills (e.g., launchdarkly-guarded-rollout). Not 5 due to that overlap; not 3 since the existing-flag framing strongly disambiguates.

4 / 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: 5 suspicious

Warning

Total

15

/

16

Passed

Repository

launchdarkly/ai-tooling

Path

skills/feature-flags/flag-release/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.