CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/dst-transition-reference

Use for any question or task about daylight saving time in code or tests, including quick ones: what breaks on DST transition days, naive datetimes plus a duration, jobs or reports an hour off after the clocks change, cron jobs that fire zero or two times. Covers skipped and repeated hours, jurisdiction differences, the IANA tz database, billing and meetings on transition days, leap seconds and clock smearing.

Quality

82%

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

71%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 reference skill whose core value is the non-obvious library-behavior detail, bug-class catalog, and anti-patterns, with exemplary progressive disclosure into verified one-level-deep reference files. Its main weaknesses are token inefficiency from re-teaching basic DST mechanics and duplicating the description, and the absence of complete copy-paste construction code in the worked example.

Suggestions

Trim the 'DST mechanics' section to the non-obvious essentials - Claude already knows spring-forward skips an hour and fall-back repeats one - and cut the Wikipedia citation, keeping only the per-library behavior differences and PEP 495 fold semantics.

Remove the 'When to use' section: it restates the frontmatter description that is always loaded alongside the body.

Make the worked example fully copy-paste ready by showing the complete construction code (e.g., datetime(2026, 3, 8, 2, 30, tzinfo=ZoneInfo('America/New_York')) plus the assert statements) instead of instructing the reader to construct it.

DimensionReasoningScore

Conciseness

The high-value non-obvious content (library behavior table, PEP 495 fold semantics, anti-patterns) is dense, but the body re-explains well-known mechanics ('on the 2nd Sunday of March, at 02:00 local time the clock jumps to 03:00') with a Wikipedia citation, the worked example repeats those mechanics, and the 'When to use' section duplicates the frontmatter description that is always in context.

3 / 5

Actionability

Concrete guidance throughout: specific fixture timestamps (2026-03-08 02:30 America/New_York), exact library calls ('localize(dt, is_dst=None)'), and specific assertions ('dt.utcoffset() == timedelta(hours=-5)', '07:30 UTC'). Falls short of copy-paste ready because no complete code block constructs the datetimes under test.

4 / 5

Workflow Clarity

The numbered 4-step 'How to use this reference' sequence (identify transition, match bug class, turn into assertion, pick zones + refresh fixtures) is clear and demonstrated end-to-end by the worked example, with refresh-against-IANA acting as a staleness checkpoint; minor gap is the lack of an explicit verify loop after assertions are written.

4 / 5

Progressive Disclosure

The body is a clear overview with all deep material split into three real, one-level-deep reference files (jurisdictions-and-fixtures.md, leap-seconds.md, smear-strategies-and-history.md - all verified present), each link annotated with what it contains, and every reference reachable directly from SKILL.md.

5 / 5

Total

16

/

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 that explicitly covers both trigger conditions and topical scope with unusually good symptom-based phrasing that mirrors how users report DST bugs. The main gaps are the absence of action verbs describing what the skill does and a few missing natural terms like 'timezone' and 'UTC'.

DimensionReasoningScore

Specificity

Enumerates many concrete topics and symptoms ('naive datetimes plus a duration', 'cron jobs that fire zero or two times', 'billing and meetings on transition days', 'leap seconds and clock smearing'), but the only verbs are 'Use for' and 'Covers' - it describes topical coverage rather than a list of concrete actions the skill performs.

4 / 5

Completeness

Explicitly answers both: when ('Use for any question or task about daylight saving time in code or tests, including quick ones: ...cron jobs that fire zero or two times') with concrete trigger phrases, and what ('Covers skipped and repeated hours, jurisdiction differences, the IANA tz database, billing and meetings on transition days, leap seconds and clock smearing').

5 / 5

Trigger Term Quality

Strong natural phrasing users would actually say: 'daylight saving time'/'DST' synonyms, 'jobs or reports an hour off after the clocks change', 'cron jobs', 'IANA tz database'. Missing a few common variations such as 'timezone'/'time zone' and 'UTC' that a user with a DST bug would likely mention.

4 / 5

Distinctiveness Conflict Risk

Clear DST-transition niche with distinct symptom-based triggers (jobs an hour off, cron firing zero or two times), but 'leap seconds and clock smearing' coverage overlaps a dedicated leap-seconds skill and general timezone/time-handling skills could compete for the same queries.

4 / 5

Total

17

/

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.

Reviewed

On this page