CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

measurable

Ensures every delivery ships the telemetry that proves its impact and surfaces its regressions — RUM events, OpenTelemetry traces, metrics, logs, and explicit error paths; modes guide, implement, audit, setup. Triggers on "is this measurable", "add telemetry", "instrument this endpoint", "will we know if this regresses", "/measurable".

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/quality/measurable/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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-orchestrated, mode-driven index with genuinely actionable delegation commands and clearly sequenced workflows, but its heavy reliance on progressive disclosure is undermined by the bundle itself: all eight referenced rule/template files are missing, so every mode's required reading points nowhere. The body is also somewhat over-justified, restating the advisory/degradation policy in four separate places.

Suggestions

Ship the referenced detail files (rules/*.md and templates/observability-profile.template.md) with the skill, or inline the essential content — every mode's Required Reading currently points to files absent from the bundle, breaking navigation and the actual instrumentation guidance.

State the advisory/companion-degradation policy once (e.g., in Core Principles) and reference it elsewhere instead of restating it in implement step 6, audit step 4, the callers section, and the anti-patterns list.

Trim multi-sentence rationale inside workflow steps (e.g., "the schema drift the registry exists to prevent, and it lands silently") to one clause so steps read as instructions rather than justifications.

DimensionReasoningScore

Conciseness

It never explains concepts Claude already knows, but the advisory/degradation policy is restated at least four times (implement step 6, audit step 4's "mirrors how critical ships non-blocking", Principle 6, the "Callers of audit mode" section), and several steps carry multi-sentence rationale ("the schema drift the registry exists to prevent, and it lands silently") that could be one line. Not 2: no padded tutorial-style explanation of OTel/RUM basics; not 4: the repetition and justification prose are real tightening targets.

3 / 5

Actionability

Concrete, executable delegation calls are given verbatim — "Skill("rum-tracking", "implement", "<target>")", "Skill("telemetry-verify", "--env local --from <start> --to <end> --no-comment")", "weaver registry check" — plus a named verdict taxonomy (missing/unlinked/pass) and precise --strict gating rules. Not 5: the actual span/metric/log specifics are entirely delegated to rule files, and the only code block is a delegation invocation rather than instrumentation guidance.

4 / 5

Workflow Clarity

Each mode has a numbered, well-sequenced workflow with a mode-detection table ("State the detected mode in one line"), an explicit verification loop ("record a window, exercise the new operation ..., then run Skill("telemetry-verify", ...)"), and per-finding checkpoints ("Cite a file path and line number for every finding"). Not 5: the implement-mode verification step is explicitly advisory and skippable, and guide mode ends with no checkpoint on its output.

4 / 5

Progressive Disclosure

The body is explicitly a thin index ("Detailed rules live in rules/*.md and load on demand") with a per-mode Required Reading table and well-signaled one-level-deep links — structurally the ideal pattern. However, none of the eight referenced files (rules/scope-detection.md, rules/frontend-rum.md, rules/backend-instrumentation.md, rules/regression-signals.md, rules/weaver-schema.md, rules/audit-checklist.md, rules/setup-profile.md, templates/observability-profile.template.md) exist in the bundle — no rules/, templates/, references/, scripts/, or assets/ directories are present — so every reference leads to a missing file. Not 4/5 because the disclosed-into content is absent; not 2 because the body itself is well structured, not a monolith.

3 / 5

Total

14

/

20

Passed

Description

83%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: it states a clear third-person capability with an enumerated signal taxonomy, four modes, and explicit natural-language trigger phrases covering both what and when. The only gaps are the policy-level verbs in place of concrete action lists and a few missing trigger synonyms (e.g., "observability", "monitoring") that leave minor overlap risk with dedicated instrumentation skills.

DimensionReasoningScore

Specificity

Enumerates concrete deliverables — "RUM events, OpenTelemetry traces, metrics, logs, and explicit error paths" — plus four named modes (guide, implement, audit, setup), giving several specific capabilities. Not 5: the operative verbs ("Ensures every delivery ships", "surfaces its regressions") describe a policy rather than listing distinct concrete actions; not 3: coverage goes well beyond 1-2 actions.

4 / 5

Completeness

Explicitly answers both halves: the "what" ("ships the telemetry that proves its impact and surfaces its regressions" with enumerated signal types and modes) and the "when" ("Triggers on 'is this measurable', 'add telemetry', ...") with concrete trigger phrases. This matches the anchor-5 example pattern exactly.

5 / 5

Trigger Term Quality

Triggers "is this measurable", "add telemetry", "instrument this endpoint", "will we know if this regresses" are natural phrases a user would actually say. Not 5: common synonyms like "observability", "monitoring", or "add metrics" are absent from the trigger list; not 3: the quoted triggers are concrete and varied, not generic keywords.

4 / 5

Distinctiveness Conflict Risk

The telemetry/regression-detection niche is clear with distinctive trigger phrasing ("will we know if this regresses"). Not 5: "add telemetry" and "instrument this endpoint" could also naturally invoke closely related dedicated OTel instrumentation skills, a minor overlap risk; not 3: the domain and triggers are far more specific than the overlap-prone anchor examples.

4 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 25 missing, 2 suspicious

Warning

Total

13

/

16

Passed

Repository

mthines/agent-skills

Path

skills/quality/measurable/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.