CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

built-in-metrics

Instrument an existing codebase with LaunchDarkly config tracking. Walks the four-tier ladder (managed runner → provider package → custom extractor + trackMetricsOf → raw manual) and picks the lowest-ceremony option that still captures duration, tokens, and success/error.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/agentcontrol/built-in-metrics/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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, highly actionable instruction skill: the four-tier ladder, availability matrix, and guardrails give exact executable guidance, and the workflow has explicit validation and troubleshooting loops. Weaknesses are moderate verbosity (inline pre-0.20 migration details, runId digression) and one orphaned bundle file (metrics-api.md) not referenced from the overview.

Suggestions

Move the pre-0.20 migration details ('aiclient.config(...)' → 'completion_config(...)', AIConfig default variants, tuple-unpacking) into an 'Old patterns' / 'Deprecated surface' section or a reference file so version-sensitive content is quarantined from the mainline workflow.

Trim the runId paragraph in 'Quick reference: tracker methods' to the essential reuse rule, dropping the digression about Monitoring-tab aggregation and at-most-once guard keying.

Link references/metrics-api.md from the body (e.g. from the Verify step or Related skills) so every bundle file is discoverable from the overview.

DimensionReasoningScore

Conciseness

Mostly efficient (tier table, availability matrix, method table, checklists), but the version-sensitive pre-0.20 migration guidance sits inline in the workflow rather than in an 'old patterns'/'deprecated' section, the paragraph after the ladder table re-explains what the table already shows, and the tracker-factory paragraph digresses into runId/Monitoring-tab aggregation details. Fits anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened'), not 4 because these digressions are more than minor.

3 / 5

Actionability

Concrete, executable guidance throughout: exact package names, a per-framework availability matrix, dual-language signatures ('tracker.trackMetricsOf(Provider.getAIMetricsFromResponse, () => providerCall())'), numbered guardrails with specific calls ('Call ldClient.flush()... await it'), and a verify checklist ('Force an error (bad API key, zero max_tokens)'). Not 5 because the body itself contains no complete copy-paste-ready code example — those are delegated to the reference files.

4 / 5

Workflow Clarity

A clear four-step sequence (Explore → Look up Tier-2 → Implement → Verify) with an explicit exploration checklist, tier-selection decision rules ('Walk from the top and stop at the first tier that fits'), and a verification step that includes forcing an error and a troubleshooting feedback loop for missing TTFT ('you probably wrapped the stream creation with trackMetricsOf but didn't add the manual trackTimeToFirstToken call — see streaming-tracking.md'). Matches anchor 5: explicit validation steps, feedback loop for error recovery, and checklists.

5 / 5

Progressive Disclosure

Good structure: the SKILL.md is an overview with a decision matrix linking seven real one-level-deep reference files (openai-tracking.md, langchain-tracking.md, bedrock-tracking.md, anthropic-tracking.md, gemini-tracking.md, strands-tracking.md, streaming-tracking.md — all verified present in references/). Not 5 because references/metrics-api.md exists in the bundle but is never linked or signaled from the body, leaving it undiscoverable, and the 'Vercel AI SDK' row points to external docs with no local path.

4 / 5

Total

16

/

20

Passed

Description

70%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 specific, distinctive, third-person description that clearly states what the skill does and names the concrete mechanism (four-tier ladder, tracked metrics). Its main weakness is the absence of any 'Use when...' trigger clause, which caps completeness, and it leans on internal jargon ('four-tier ladder', 'lowest-ceremony') over natural user-spoken trigger terms.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when adding LaunchDarkly metrics/monitoring to an existing AI provider call or when the user asks for agent observability, token tracking, or config monitoring.'

Include natural trigger synonyms users would actually say — 'monitoring', 'observability', 'telemetry', 'agent metrics' — alongside the SDK jargon.

Mention scope coverage such as streaming/TTFT and both Python and Node to round out the capability list.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Instrument an existing codebase with LaunchDarkly config tracking', 'Walks the four-tier ladder', 'picks the lowest-ceremony option that still captures duration, tokens, and success/error' — with named tiers and metrics. Not 5 because coverage has minor gaps (no streaming/TTFT or language mention); not 3 because it goes well beyond 1-2 actions.

4 / 5

Completeness

The 'what' is clear and specific (instrument a codebase with LaunchDarkly config tracking via a four-tier ladder), but there is no 'Use when...' clause or equivalent explicit trigger guidance — 'when' is only weakly implied by 'an existing codebase'. Per the rubric guideline, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good keyword coverage ('LaunchDarkly', 'config tracking', 'instrument', 'duration', 'tokens') that users of this SDK would naturally say. Not 5 because natural synonyms like 'monitoring', 'observability', 'telemetry', or 'agent metrics' are missing, and phrases like 'four-tier ladder' and 'lowest-ceremony' are internal jargon rather than user-spoken terms.

4 / 5

Distinctiveness Conflict Risk

'LaunchDarkly config tracking' carves out a clear niche with distinct triggers (SDK names, tracker API terms); it is unlikely to fire for unrelated skills. This matches the anchor 'Clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

16

/

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/agentcontrol/built-in-metrics/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.