CtrlK
BlogDocsLog inGet started
Tessl Logo

flag-and-release-change

Drive a pull request's change end to end: decide it's flag-worthy, create the guarding flag, wire the new code path behind it on the PR branch, and record an automated release so the change ships safely when the PR merges. A portable orchestrator that composes should-flag-change, launchdarkly-flag-create, and flag-release. Keywords: flag a PR, wrap change in a flag, dark launch, kill switch, auto-release, automated rollout, end-to-end flag workflow.

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary orchestrator skill body: lean, fully actionable, with a clearly sequenced plan→implement workflow and explicit validation and fail-closed gates. Progressive disclosure is clean, with its one unique reference verified to exist and correctly linked.

DimensionReasoningScore

Conciseness

Lean and efficient; assumes Claude's competence, does not explain feature flags or git, and explicitly delegates composed-skill mechanics, keeping only the unique PR-wrapper and plan→implement content. The brief conceptual framing ('the deploy is not the release') is load-bearing safety context, not padding.

5 / 5

Actionability

Provides concrete, executable git commands (clone, fetch, three-dot diff, add, commit, push), a concrete numbered plan→implement sequence with explicit fail-closed error rules and named hand-offs. As an instruction-only skill, the absence of application code is appropriate and unpunished.

5 / 5

Workflow Clarity

Clear two-phase sequence with explicit gates ('Never create or modify anything during the plan phase', 'Only after approval'), numbered steps, and explicit validation checkpoints ('continue only once green', fail-closed on create-flag errors, 'Report only what you verified', plus compile/lint and get-flag-OFF verification in the reference).

5 / 5

Progressive Disclosure

Well-organized sections with a clear overview; the single unique bundle file references/pr-wiring.md exists, is correctly linked inline, is one level deep, and is clearly signaled as the skill's only unique reference; composed-skill mechanics are delegated via links rather than inlined.

5 / 5

Total

20

/

20

Passed

Description

91%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, specific description that enumerates concrete end-to-end actions, names the composed skills, and supplies a rich keyword list. Its only weakness is the absence of an explicit 'Use when…' trigger clause, which caps completeness at 4.

Suggestions

Add an explicit 'Use when…' sentence stating the trigger condition (e.g., 'Use when a pull request's change should ship behind a feature flag with an automated release on merge.') to lift completeness to 5.

Consider adding one or two tool-anchored trigger terms (e.g., 'LaunchDarkly feature flag', 'PR gating') to further reinforce distinctiveness.

DimensionReasoningScore

Specificity

Lists multiple concrete end-to-end actions ('decide it's flag-worthy, create the guarding flag, wire the new code path behind it on the PR branch, and record an automated release'), giving comprehensive coverage with no real gaps.

5 / 5

Completeness

Clearly answers 'what' (the four actions plus orchestrator composition) and conveys 'when' via the keyword list and 'a pull request's change…when the PR merges', but lacks an explicit 'Use when…' clause, which the guideline caps.

4 / 5

Trigger Term Quality

A dedicated 'Keywords:' list provides natural phrases and synonyms users would say — 'flag a PR, wrap change in a flag, dark launch, kill switch, auto-release, automated rollout, end-to-end flag workflow'.

5 / 5

Distinctiveness Conflict Risk

A clear niche (flagging a PR's change behind LaunchDarkly) with distinct triggers and named composed skills; minimal overlap risk with other skills.

5 / 5

Total

19

/

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