CtrlK
BlogDocsLog inGet started
Tessl Logo

launchdarkly-metric-choose

Choose the right metrics for a LaunchDarkly experiment, guarded rollout, or release policy. Use when the user wants to know which metrics to use, which is the primary metric for an experiment, what guardrails to add, or which events to monitor in a rollout. Surfaces what will auto-attach from existing release policies before making additional recommendations.

91

1.16x
Quality

91%

Does it follow best practices?

Impact

92%

1.16x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%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-crafted advisory workflow: concrete tool calls, typed guidance, an explicit validation checkpoint (event health), and a strong output template. Its only weaknesses are slight redundancy between the Step 2 and Step 5 examples and edge-case detail that could be offloaded to a reference file.

DimensionReasoningScore

Conciseness

The body is efficient and assumes competence, teaching only product-specific facts (CUPED incompatibility, mid-experiment restart, context-kind matching) rather than general concepts. Minor redundancy exists — the Step 5 output example repeats the auto-attach formatting demonstrated in Step 2 — so it falls just short of 'every token earns its place'.

4 / 5

Actionability

Fully executable for an instruction-only skill: concrete MCP calls (list-release-policies(projectKey), list-metrics, list-metric-events), exact upfront questions, a typed secondary-metric table, specific numeric guidance (2-3 metrics max), and a copy-ready output template covering the common case.

5 / 5

Workflow Clarity

Five clearly sequenced steps with explicit per-path branching, gating directives ('For experiments — skip this step', 'Show this inventory before recommending'), an event-health validation checkpoint, and escalation triggers ('Raise this immediately if the user mentions they're mid-experiment').

5 / 5

Progressive Disclosure

Well-sectioned body with clear headers and one-level-deep links to related skills. However, at ~175 lines with detailed edge-case content ('Important Context') that could live in a reference file, it shows minor organization gaps rather than an appropriately split structure.

4 / 5

Total

18

/

20

Passed

Description

92%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, explicit 'Use when' triggers covering the main question forms, and concrete capability statements specific to LaunchDarkly. The only gap is a few missing synonyms (e.g., KPI, success metric) that users might naturally say.

DimensionReasoningScore

Specificity

Names the LaunchDarkly domain and multiple concrete actions — choosing the primary metric, guardrails, events to monitor, and surfacing auto-attached release-policy metrics — with no coverage gaps across the skill's scope.

5 / 5

Completeness

Explicitly answers both what ('Choose the right metrics for a LaunchDarkly experiment, guarded rollout, or release policy') and when ('Use when the user wants to know which metrics to use...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases like 'which metrics to use', 'primary metric', 'guardrails', and 'events to monitor' would be said by users, but common synonyms such as 'KPI' or 'success metric' are absent.

4 / 5

Distinctiveness Conflict Risk

A named LaunchDarkly niche with distinct triggers; metric selection is clearly separable from sibling metric-create/metric-instrument tasks, so conflict risk is minimal.

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