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.
93
92%
Does it follow best practices?
Impact
92%
1.16xAverage score across 3 eval scenarios
Passed
No known issues
Experiment metric recommendation with typed secondaries and CUPED warning
Hypothesis framing
60%
100%
Single primary metric
100%
100%
Primary success direction
100%
100%
Guardrail metric present
100%
100%
Counter-metric present
0%
100%
Supporting signal present
62%
100%
Event health check
100%
100%
CUPED + percentile warning
100%
100%
No release policy fetch
100%
100%
Next steps guidance
87%
100%
Advisory only
100%
100%
Guarded rollout metric selection with release policy surfacing
Release policy fetch
40%
70%
Auto-attached metrics surfaced
91%
91%
Reliability bias
90%
100%
Metric count limit
0%
100%
Domain-specific metric
100%
100%
Pushback on product metrics
100%
100%
Event health check
40%
90%
Recommendation format
87%
100%
No experiment workflow
100%
100%
Next steps guidance
90%
100%
Release policy metric selection with context kind mismatch and scope guidance
Existing policy surfaced
70%
100%
Max 3 metrics recommended
100%
100%
Pushback on 5 metrics
58%
58%
Stable event history requirement
20%
50%
Context kind mismatch warning
100%
100%
Scope condition explanation
100%
100%
Recommends reliable candidates
100%
30%
Next steps guidance
37%
87%
Advisory only
100%
100%
No experiment workflow applied
100%
100%
24e9c7e
Table of Contents
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.