CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

79%

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 router skill with clear scope boundaries, named MCP tools, and explicit branch handling. The main weakness is redundancy: the removal routing message and no-verdict constraints are repeated multiple times, inflating token cost without adding guidance.

Suggestions

State the removal-routing message once (e.g., in a single 'Removal questions' section) and reference it from Step 3/Step 4 instead of duplicating it verbatim.

Consolidate the repeated 'no verdict / no analysis' warnings into the single Hard constraints list and cut the restatements in Step 3, Step 4, and Important Context.

Add one example get-flags call (with query, project, and environment parameters) and a sample summary-table output to make Step 3 copy-paste concrete.

DimensionReasoningScore

Conciseness

The removal-routing message is duplicated verbatim in Scope Boundary and Step 3, and the "no verdict / no analysis" constraint is repeated about four times ("That's it. No analysis. No bullet points. No verdict.", "Do not add a verdict...", "Never improvise removal..."). Mostly efficient but noticeably tightenable — anchor 3, not 4, because a full paragraph duplication is more than a minor trim.

3 / 5

Actionability

Concrete, executable guidance throughout: named MCP tools ("get-flags", "get-flag-status-across-envs"), equivalent command forms, branch-by-match-count resolution, a copy-paste routing message, and a routing table. Minor gaps: no example get-flags invocation (parameters, project/environment) or sample summary-table output, keeping it just below anchor 5.

4 / 5

Workflow Clarity

Steps 1-4 are clearly sequenced with decision checkpoints in Step 2 (one match → resolve; multiple → disambiguation list; none → suggest broader query) and explicit routing rules in Step 4. This is a read-only lookup, so the destructive-operation validation cap does not apply; the remaining gap is no error-recovery guidance if MCP calls fail — anchor 4.

4 / 5

Progressive Disclosure

Well-organized sections with all router-appropriate content inline and one-level-deep, clearly signaled links to sibling skills (e.g., ../launchdarkly-flag-discovery/SKILL.md). No bundle files exist, and at ~105 lines with some duplicated content that could be consolidated, it fits anchor 4 rather than the well-split anchor 5.

4 / 5

Total

15

/

20

Passed

Description

83%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 with an explicit "Use when" clause and concrete, natural trigger phrases covering the /flag entrypoint. Minor improvements possible: mention the routing-to-deeper-workflows capability and add a few more natural search phrasings.

DimensionReasoningScore

Specificity

Lists several concrete actions — "quickly find a flag by name/key", "direct flag detail summary", "fast disambiguation between similar flags" — but the lead phrase "resolve ... into the right LaunchDarkly flag lookup flow" is abstract and the routing-to-deeper-workflows capability from the body is omitted. Fits anchor 4 (several specific actions, minor gaps) better than 5 (comprehensive) and clearly above 3 (only 1-2 actions).

4 / 5

Completeness

Explicitly answers both: what ("Resolve /flag style requests ... find a flag by name/key, direct flag detail summary, fast disambiguation") and when ("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"). Matches the anchor-5 pattern of concrete trigger phrases paired with explicit capabilities.

5 / 5

Trigger Term Quality

Includes natural terms users would say: "/flag", "find a flag by name/key", "similar flags". A few common variations are missing (e.g., "search flags", "show me the flag", "feature flag"), matching anchor 4 rather than 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The "/flag" command trigger carves a clear niche, but "asks to quickly find a flag" could overlap with closely related sibling skills (flag discovery, flag cleanup) in the same LaunchDarkly suite — anchor 4 (mostly distinct, minor overlap with closely related skills).

4 / 5

Total

17

/

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

Warning

Total

15

/

16

Passed

Repository

launchdarkly/ai-tooling

Path

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