CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

metric-test

Author and validate a metric spec for the data-path suite (tests/datapath/metrics/<class>/<name>.test.yaml fixture + test_<name>.py module, run against a compose test-stand instance). Use when asked to write/scaffold/validate a test for a metric, seed bronze data for a test, add a fixture for a dashboard metric, or check a spec. Covers schemas/, templates/, $ref+sibling composition, bronze records with duplicates, account bindings, POST /v1/metric-results, and the assertion helpers (row/equals/contains, one/some over a view, approx).

Quality

92%

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

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

An exceptionally actionable and well-sequenced skill body: every phase of authoring, validating, and running a metric spec carries executable commands, complete examples, and hard-won operational gotchas, with almost no filler. Its one structural weakness is that it is a single long file — the assertion API, date-window design, and CI details are reference material that would be better split into one-level-deep bundle files.

Suggestions

Move the assertion-helper API (r.row/equals/contains/nonempty/check, one/some selectors, approx, the per-view required-field list) into a references/assertions.md and keep only 2–3 representative examples inline in SKILL.md.

Split the 'Date-window test design' BVA/equivalence-partition guidance and the 'New bronze table for a not-yet-seeded connector' procedure into references/ files, linked from a short 'when a metric is date-windowed' / 'when the connector isn't seeded' pointer in the body.

Trim knowledge Claude already has, e.g. 'A record is a field map' and the textbook definition of an even-sample median, keeping only the repo-specific rule (quantileExactInclusive vs quantilesExact) that the test must compute with.

DimensionReasoningScore

Conciseness

The body is dense with genuinely non-obvious, repo-specific knowledge (isolation ledger semantics, cohort resolution via department string, MIN_PEER_N rule, shared-venv conflict) and almost never explains things Claude already knows. A few statements could be trimmed, e.g. "A record is a field map" and the textbook aside "A `median` is the textbook one … an even sample averages its two middles", which puts it at the efficient-with-minor-trimmables anchor rather than the every-token-earns-its-place anchor.

4 / 5

Actionability

Guidance is fully executable: a complete worked YAML fixture (templates + bronze with $ref, overrides and a duplicate row), a complete copy-paste-ready pytest module, exact commands (uv run --project tests --frozen --group datapath …, ./dev-compose.sh test-stand … with flags), and runnable validation snippets including the schema-coverage diff loop. The common cases (scaffold a new test, validate without a stand, run one shard) are each covered by a specific command.

5 / 5

Workflow Clarity

The workflow is clearly sequenced as phases — "Scaffolding a new test" (numbered steps 1–6), "Validating a test (no stand needed)" with runnable checks, "Running" with per-command semantics, and the coverage gate — and the Gotchas section supplies explicit error-recovery guidance (SeededWarehouseError → raise a minimal instance; mid-run edit → let the run finish, then re-run; ruff only outside a running suite). This matches the anchor with explicit validation steps, feedback loops, and checklists; the level-4 anchor's "minor validation gaps" understates how thorough the validation section is.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the SKILL.md is a ~460-line monolith that inlines substantial reference material — the full assertion-helper API (~40 lines), the date-window BVA/equivalence design, the CI shard topology, and the new-bronze-table procedure — that the rubric rationale says belongs one level deep. Structure and signaling are good (clear headers, an explicit "Source of truth (reference — open only if you need the detail)" pointer to the library), which keeps it above the level-2 anchor, but the bulk of inline detail places it at "some structure; content that should be separate is inline" rather than level 4's "most content is appropriately placed".

3 / 5

Total

17

/

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.

A model description: it states the concrete artifact pair it produces, the runtime target, an explicit and varied 'Use when' clause covering all entry points, and a closing inventory of the sub-topics it covers. Every capability named is concrete and domain-anchored, with no fluff or over-claim.

DimensionReasoningScore

Specificity

The description names multiple concrete actions with concrete artifacts: "Author and validate a metric spec", "write/scaffold/validate a test for a metric, seed bronze data for a test, add a fixture for a dashboard metric, or check a spec", plus named mechanics like "POST /v1/metric-results" and "the assertion helpers (row/equals/contains, one/some over a view, approx)". This matches the comprehensive-coverage anchor, and the level-4 anchor ("minor gaps in coverage") fits worse since every listed capability of the skill carries an action verb.

5 / 5

Completeness

It explicitly answers both questions: what ("Author and validate a metric spec for the data-path suite (tests/datapath/metrics/<class>/<name>.test.yaml fixture + test_<name>.py module, run against a compose test-stand instance)") and when ("Use when asked to write/scaffold/validate a test for a metric, seed bronze data for a test, add a fixture for a dashboard metric, or check a spec"). An explicit Use-when clause with four concrete triggers is the level-5 pattern; the level-4 anchor requires a weaker 'when', which is not the case here.

5 / 5

Trigger Term Quality

The "Use when" clause lists natural phrasings a repo user would actually say ("write/scaffold/validate a test for a metric", "seed bronze data for a test", "add a fixture for a dashboard metric", "check a spec") with synonyms (test/fixture/spec, write/scaffold/validate) and file formats (.test.yaml, test_<name>.py). Coverage is comprehensive rather than merely good, so it fits the level-5 anchor better than level 4.

5 / 5

Distinctiveness Conflict Risk

The niche is sharply delimited by repo-specific artifacts (tests/datapath/metrics/, compose test-stand instance, POST /v1/metric-results, bronze/schemas/templates), so no other skill would plausibly trigger on these phrases and this skill would not fire for unrelated test-writing requests. Clear niche with distinct triggers is the level-5 anchor; level 4's "minor overlap risk with closely related skills" does not apply.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

constructorfabric/insight

Path

.claude/skills/metric-test/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.