CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/timezone-test-matrix-builder

Builds a timezone, daylight saving time (DST), and leap year / leap second test matrix from wherever a codebase reads or formats dates and times. Finds time-handling code (grep for datetime / Date / Instant / time.time / timezone), sorts each spot into storage, business-logic, display, cron, or billing, picks the edge cases that matter (DST spring-forward / fall-back, ambiguous local time, leap day Feb 29, ISO 8601 / RFC 3339 round-trip, zone-database updates), and emits per-spot test stubs wired to the language's fake-clock (mock-time) library. Use when a codebase needs timezone, DST, and leap-year test coverage derived from its own date/time usage.

75

Quality

94%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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 skill body with executable code, a clear sequenced workflow, and an explicit validate-fix-retry loop. The only weakness is mild redundancy between the numbered steps and the worked example.

Suggestions

Tighten the 'Worked example' section so it illustrates a non-obvious decision rather than re-walking Steps 1, 3, 5, 6, and 7 that are already fully specified above.

Consider trimming the inline Python block in Step 5 to one representative stub and pointing the rest to the matrix.yaml pattern, since the catalog reference already enumerates the cases.

DimensionReasoningScore

Conciseness

The body is dense and free of concept-padding, but the 'Worked example' section re-narrates the Step 1→7 flow already laid out in the numbered steps, which is redundant and could be tightened per the verbosity penalty.

2 / 3

Actionability

Provides copy-paste-ready grep commands, a category→test-needs table, a per-language harness table, a YAML matrix schema, and fully executable freezegun Python stubs with real assertions.

3 / 3

Workflow Clarity

Seven clearly sequenced steps with an explicit validation feedback loop in Step 6 ('run... assert every DST and leap-day case... If a case errors... fix the harness mapping... re-run until the matrix is green'), appropriate for a batch test-generation operation.

3 / 3

Progressive Disclosure

The body is an overview that offloads the per-category test catalog to a clearly signaled one-level-deep reference (references/test-catalog.md, verified present), with companion catalogs and harnesses named but kept out of the main flow.

3 / 3

Total

11

/

12

Passed

Description

100%

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, specific description that names concrete actions, includes natural trigger terms, provides an explicit 'Use when' clause, and occupies a clear niche. Voice is correctly third person.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Finds time-handling code (grep for...)', 'sorts each spot into storage, business-logic, display, cron, or billing', 'picks the edge cases that matter', and 'emits per-spot test stubs' — matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (builds a test matrix via find/sort/pick/emit) and when via the explicit 'Use when a codebase needs timezone, DST, and leap-year test coverage derived from its own date/time usage' clause.

3 / 3

Trigger Term Quality

Natural terms a user would say are present — 'timezone', 'DST', 'leap year', 'test coverage', 'date/time usage' — giving good coverage of the keywords users would naturally invoke the skill with.

3 / 3

Distinctiveness Conflict Risk

The niche — a timezone/DST/leap-year test matrix derived from a codebase's own date/time usage — is distinctive with triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents