CtrlK
BlogDocsLog inGet started
Tessl Logo

launchdarkly-flag-command

Resolve `/flag` style requests into the right LaunchDarkly flag lookup flow. Use when the user types `/flag`, asks to quickly find a flag by name/key, wants a direct flag detail summary, or needs fast disambiguation between similar flags.

64

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/feature-flags/launchdarkly-flag-command/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-structured, actionable instruction-only routing skill with concrete tools, an exact routing message, and clear workflow branching. Its main weakness is redundancy — the anti-removal-verdict boundary is reinforced to the point of repetition, which inflates the token budget without adding guidance.

Suggestions

Consolidate the removal/staleness routing guidance: state the exact routing message once in the Scope Boundary section and reference it from Step 3/Step 4 rather than repeating it near-verbatim.

Add a brief concrete example of the expected flag summary table so Step 3's output format is unambiguous and copy-paste ready.

Trim repeated "no verdict / no bullet points / no analysis" clauses into a single explicit list of forbidden outputs.

DimensionReasoningScore

Conciseness

Mostly efficient and free of concept over-explanation, but the removal/staleness routing message is restated near-verbatim three times (Scope Boundary, Step 3, Step 4) and the "no verdict" injunction is repeated multiple times, adding tokens that could be consolidated.

3 / 5

Actionability

Provides concrete MCP tool names (list-flags, get-flag), an exact routing message to emit, a routing table with explicit sibling-skill paths, and a specific summary field list — minor gap is the absence of a concrete example of the summary table format.

4 / 5

Workflow Clarity

A clearly sequenced 4-step workflow with explicit branching (single match → resolve, multiple → disambiguate, none → suggest broader query) and a routing checkpoint after the summary; the read-only, non-destructive nature means the destructive-validation cap does not apply.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with one-level-deep references to sibling skills via a routing table; no bundle files exist, and content is appropriately split across the sibling skills rather than inlined.

4 / 5

Total

15

/

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.

A strong, third-person description that clearly states both the capability and its trigger conditions with concrete, natural phrasing. Minor trigger-term breadth is the only thing keeping specificity and trigger quality at 4 rather than 5.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Resolve `/flag` style requests", "quickly find a flag by name/key", "direct flag detail summary", "fast disambiguation between similar flags" — with only minor gaps (no mention of what the summary contains).

4 / 5

Completeness

Explicitly answers both what ("Resolve `/flag` style requests into the right LaunchDarkly flag lookup flow") and when ("Use when the user types `/flag`, asks to quickly find a flag by name/key...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural triggers — "types `/flag`", "quickly find a flag by name/key", "flag detail summary", "disambiguation between similar flags" — though a few common phrasings (e.g. "show me this flag") are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (LaunchDarkly `/flag` read-only lookup) with distinct triggers and minimal overlap risk versus sibling create/targeting/cleanup skills.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 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.