CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

joeholdcroft/rail-commute-watch

Calendar-gated UK rail monitoring before departure and during the journey, with configurable hours, useful alternatives and meaningful arrival-change alerts.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

88%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-crafted instruction-only skill: a gated, validated check workflow with concrete match criteria, record fields, and an example alert, supported by four real, shallow reference files. The only notable costs are mild cross-section repetition and a body that carries more inline API-semantics detail than a minimal overview would.

DimensionReasoningScore

Conciseness

The body is dense prescriptive rules with no explanations of concepts Claude already knows — every sentence adds a domain-specific rule ("Never infer arrival by adding a departure delay to the normal journey time", "Absence from a filtered board is not proof of cancellation"), assuming Claude's competence. It is not score 5 because there are minor instances that could be trimmed: rules repeated across sections (e.g., "Do not promise ongoing monitoring without an active schedule" restating setup-boundary rules, private-data boundaries appearing in both "Configure privately" and "Boundaries") and some convoluted exception sentences; it is above score 3 because the over-explanation is minor relative to the density of earned tokens.

4 / 5

Actionability

For an instruction-only skill the guidance is fully executable: exact match criteria ("Match today's service by origin, scheduled departure, operator when known"), a concrete record field list ("Record scheduled and expected departure/arrival, cancellation, part cancellation, changed calling points, platform..."), specific check counts ("Check at least two preceding and two following usable direct trains"), a cadence starting point ("15 minutes is a reasonable starting point"), and a copy-paste-ready example alert template covering the main case (cancelled service with next-best option and source link). It matches the fully-executable anchor with specific examples covering common cases; it is not score 4 because there are no material gaps — failure cases (missing train, cutoff reached, rejected cadence) each have concrete responses.

5 / 5

Workflow Clarity

"Run one bounded check" is a numbered 7-step sequence with explicit validation gates: read the calendar "before fetching rail data", fetch rail data only "when travel is supported by the calendar gate", verify reads before scheduling ("Successfully perform harmless reads of the required calendar and live-data sources before scheduling"), and "At the first eligible run verify data retrieval and preserve the result". Error-recovery paths are explicit ("If the requested cadence is rejected... Explain the supported alternative and ask", "On unresolved calendar access or ambiguity... send at most one concise coverage warning", "If the hard cutoff is reached... give one useful, nonduplicate notice"). This matches the clear-sequence-with-explicit-validation anchor; it is not score 4 because checkpoints are present at every stage and failure paths are handled, and the destructive/batch cap does not apply since the skill is read-only with validation.

5 / 5

Progressive Disclosure

Scored against the actual bundle: all four referenced files exist (references/configuration.md, sources.md, apis.md, state-and-alerts.md), each is one level deep and well-signaled with purpose context ("See [configuration.md](references/configuration.md) for fields and a shareable setup example"); sources.md's link to apis.md is not a hidden chain since SKILL.md links apis.md directly. It is not score 5 because the ~68-line body carries substantial inline domain detail (e.g., API forecast semantics like "A provider's estimate derived by carrying forward the latest movement delay is not a station-specific forecast either") that overlaps content belonging in the reference files, making the body heavier than a lean overview; it is above score 3 because the split is deliberate and navigation is easy.

4 / 5

Total

18

/

20

Passed

Description

92%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: concrete, third-person action coverage of the whole workflow plus an explicit "Use for..." trigger clause naming two invocation modes. The only weakness is trigger-term coverage — users most often say "train" ("is my train on time?", "train delays"), which never appears.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in third person — "Monitor a configured UK rail commute before departure and during the journey", "use the user's calendar to check whether travel is planned", "compare alternatives", "send one verified initial status", "alert only on meaningful delays, calling-pattern changes or arrival implications" — covering the full workflow comprehensively with no vague filler. This matches the anchor for multiple specific concrete actions with comprehensive coverage; it is not score 4 because there are no minor coverage gaps across pre-departure, in-journey, and alerting behavior.

5 / 5

Completeness

Explicitly answers both questions: the "what" is the concrete action list (monitor commute, calendar check, compare alternatives, send verified status, alert on meaningful changes) and the "when" is an explicit trigger clause — "Use for a requested commute check or an authorized recurring rail watch" — with concrete trigger phrases. This matches the anchor that clearly and explicitly answers both what AND when; it is not score 4 because the when-clause is already explicit and specific rather than merely present.

5 / 5

Trigger Term Quality

Good natural keywords: "UK rail commute", "commute check", "recurring rail watch", "delays", "calling-pattern changes", "departure", "arrival" — phrases a user requesting this skill would plausibly say. It falls short of score 5 because the most common user phrasings — "train", "train times", "is my train delayed", "live train" — are absent, leaving a few natural synonyms missing; it is above score 3 because the included terms are specific and varied rather than generic.

4 / 5

Distinctiveness Conflict Risk

"UK rail commute", "commute check", and "authorized recurring rail watch" carve out a clear niche with distinct triggers, so the risk of this description firing for an unrelated skill is minimal. It matches the clear-niche anchor; it is not score 4 because there is no meaningful overlap with a closely related skill category — the domain (UK rail commuting with calendar gating) is narrowly and unambiguously scoped.

5 / 5

Total

19

/

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