CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

launchdarkly-metric-create

Create a LaunchDarkly metric that measures what matters for an experiment or rollout. Use when the user wants to create a metric, track an event, measure page views, button clicks, conversion, latency, error rate, or any custom numeric or binary outcome. Instruments the event first when needed (including SDK setup and .env), then creates and verifies the metric.

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%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.

The body is highly actionable and models an exemplary guarded workflow — explicit confirmation gates, event-flow feedback loops, and post-creation verification — with concrete tool signatures and executable code throughout. Its weaknesses are redundancy (repeated stop directives, a duplicated measure-type table, restated context bullets) and the absence of progressive disclosure: everything, including a long SDK instrumentation guide, lives inline in SKILL.md with no reference files.

Suggestions

Move the Step 2b instrumentation sub-workflow (SDK install, .env handling, base-URL config, track() examples) into a reference file such as references/instrumentation.md, keeping a short trigger-based pointer in the main workflow — this would cut SKILL.md roughly in half and enable one-level-deep progressive disclosure.

Remove duplicated content: drop the restated confirmation directive at the top of Step 5 (the Step 4 'STOP HERE' block already covers it), and either delete the 'Measure Type Reference' section or fold its isNumeric/unitAggregationType mapping into Step 4's existing table instead of presenting both.

Trim the 'Important Context' bullets to only the facts not already stated in the workflow (keep case-sensitivity, key immutability, project scoping, and the primary/secondary metric note; drop the pageview/click preference and no-events reminders, which repeat Steps 1 and 2).

DimensionReasoningScore

Conciseness

The body is mostly domain-specific and lean, but contains real redundancy: the Step 4 'STOP HERE' directive is restated at the top of Step 5, the 'Measure Type Reference' section duplicates Step 4's table while saying twice that you never set isNumeric/unitAggregationType directly, and several 'Important Context' bullets restate earlier steps. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' better than the 'minor instances' level above.

3 / 5

Actionability

Gives exact MCP tool signatures with full parameter lists (create-metric, get-metrics, get-environment, get-sdk-key), copy-paste-ready .env variables and asyncWithLDProvider init code, decision tables for metric kind and measure type, a proposed-config template, and a verification checklist — fully executable guidance covering the common cases, with only trivial gaps (e.g., no Node server-SDK init snippet).

5 / 5

Workflow Clarity

Steps 1–6 are clearly sequenced with explicit validation checkpoints: a STOP-for-confirmation gate before any API call, a duplicate-metric check, a feedback loop that re-runs get-metric-events until events are confirmed flowing, and a post-creation verification checklist with error-recovery guidance (e.g., .env mismatch handling).

5 / 5

Progressive Disclosure

Section structure is good, but the ~290-line body is entirely inline with zero bundle files; the SDK instrumentation sub-workflow (~75 lines of install/.env/base-URL detail) and the measure-type API mapping table clearly belong in separate reference files. This matches 'some structure... content that should be separate is inline' rather than the well-split level above.

3 / 5

Total

16

/

20

Passed

Description

100%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.

The description is a strong match to the top anchors across all dimensions: it enumerates concrete actions in third person, provides an explicit 'Use when...' clause rich with natural trigger phrases, and occupies a clearly distinct LaunchDarkly-metrics niche. The only marginal weakness is the slight marketing flavor of 'measures what matters', which adds no concrete information but does not obscure the action list.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Create a LaunchDarkly metric', 'Instruments the event first when needed (including SDK setup and .env)', 'creates and verifies the metric' — covering the skill's full action set comprehensively, matching the top anchor rather than the 'minor gaps' level below it.

5 / 5

Completeness

Explicitly answers both 'what' (create metric, instrument event including SDK setup and .env, then verify) and 'when' via a concrete 'Use when...' clause with specific trigger phrases, which is the top anchor.

5 / 5

Trigger Term Quality

'create a metric, track an event, measure page views, button clicks, conversion, latency, error rate, or any custom numeric or binary outcome' comprehensively enumerates the natural phrases a user would say when needing this skill, including synonyms, so it exceeds the 'a few natural terms missing' level.

5 / 5

Distinctiveness Conflict Risk

'LaunchDarkly metric' anchors a clear niche, and the trigger terms are metric/experiment-specific, giving minimal overlap risk with other skills; it is more distinctive than the 'minor overlap risk' level.

5 / 5

Total

20

/

20

Passed

Validation

100%

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-create/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.