Name: launchdarkly-metric-instrument
Rating: 80 (1 reviews)
Author: launchdarkly

launchdarkly-metric-instrument

Instrument a LaunchDarkly metric event in a codebase by adding a track() call. Use when the user wants to wire up an event, instrument an action for a metric, add tracking to a feature, or confirm that an event is flowing to LaunchDarkly.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-crafted workflow skill: concise, executable, with an explicit verification checkpoint and error-recovery checklist, and a single well-signaled reference file that genuinely exists. It scores at the top anchor across all four dimensions.

Dimension	Reasoning	Score
Conciseness	The body is lean and domain-specific, assuming Claude's competence without explaining basic concepts; the 'Important Context' bullets convey non-obvious LaunchDarkly behavior (flush semantics, experiment correlation) rather than padding.	3 / 3
Actionability	It provides executable, copy-paste-ready code ('ldClient.track(\'checkout-completed\', context);', 'list-metric-events(projectKey, environmentKey)') plus concrete search patterns and a server/client-side signature table.	3 / 3
Workflow Clarity	Five clearly sequenced steps culminate in an explicit verify step with a feedback loop — a troubleshooting checklist table keyed to specific failure modes for when the event key is absent.	3 / 3
Progressive Disclosure	The body is an overview that repeatedly signals the one-level-deep, verified reference 'references/sdk-track-patterns.md' for per-language detail, keeping the main file navigable.	3 / 3
	Total	12 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 names concrete actions, includes explicit 'Use when' triggers with natural phrasing, and occupies a clear, low-conflict niche. It satisfies all four dimensions at the top anchor.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'adding a track() call', 'wire up an event', 'instrument an action for a metric', 'add tracking to a feature', and 'confirm that an event is flowing' — rather than vague language.	3 / 3
Completeness	It states both what the skill does ('Instrument a LaunchDarkly metric event in a codebase by adding a track() call') and an explicit 'Use when...' clause with concrete triggers.	3 / 3
Trigger Term Quality	It uses natural phrasings a user would actually say ('wire up an event', 'add tracking to a feature', 'event is flowing to LaunchDarkly') with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The LaunchDarkly-specific, track()-based metric instrumentation niche is distinct and unlikely to trigger for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: launchdarkly/ai-tooling
Path: skills/metrics/launchdarkly-metric-instrument/SKILL.md
Commit: 4fdba42

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.