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.

76

Quality

96%

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

92%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 well-structured and highly actionable, with an explicit validation feedback loop and clean progressive disclosure to a single real reference file. Only minor conciseness slack from the redundant worked example keeps it from a perfect score.

DimensionReasoningScore

Conciseness

Mostly lean with compact tables and focused code, but the 'Worked example' re-narrates Steps 1/3/5/6/7 already detailed above — a minor instance of over-explanation that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready grep commands, a complete executable Python test file with imports and assertions, and concrete run commands covering the common cases.

5 / 5

Workflow Clarity

Seven clearly sequenced steps with Step 6 as an explicit validation checkpoint and feedback loop ('fix the harness mapping... re-run until the matrix is green'), plus an anti-patterns checklist.

5 / 5

Progressive Disclosure

Overview in SKILL.md with a well-signaled one-level-deep reference to references/test-catalog.md (a real file); per-language harness detail is appropriately deferred to the sibling fake-clock-testing skill.

5 / 5

Total

19

/

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 exemplary: it states comprehensive concrete actions, includes a clear 'Use when' trigger with natural synonyms, and occupies a distinct niche. Both what and when are explicit and specific.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — builds a test matrix, finds time-handling code via grep, sorts spots into named categories, picks edge cases, and emits per-spot test stubs — giving comprehensive coverage of capabilities.

5 / 5

Completeness

Explicitly answers both what (the five concrete verbs) and when ("Use when a codebase needs timezone, DST, and leap-year test coverage derived from its own date/time usage").

5 / 5

Trigger Term Quality

Comprehensive natural terms with synonyms — timezone, daylight saving time (DST), leap year, leap second, test coverage, date/time — matching what a user would say when they need this skill.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — timezone/DST/leap-year test-matrix generation — with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 8 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents