CtrlK
BlogDocsLog inGet started
Tessl Logo

oebb-scotty

Austrian rail travel planner (ÖBB Scotty). Use when planning train journeys in Austria, checking departures/arrivals at stations, or looking for service disruptions. Covers ÖBB trains, S-Bahn, regional trains, and connections to neighboring countries.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable, well-structured API reference with executable examples and useful lookup tables. The main efficiency gain available is de-duplicating the repeated auth block, and a clearer error-recovery loop would round out workflow clarity.

Suggestions

Factor the repeated auth/client JSON block into a single shared snippet referenced by each request example to reduce token cost and maintenance burden.

Expand the Error Handling section into a short validate/retry loop (check 'err', surface 'errTxt', retry or advise) to strengthen workflow clarity.

Move the Common Station IDs and Product Classes tables into a separate reference file and link from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly efficient with tight tables and executable examples, but the full auth/client block is repeated verbatim in every request example and could be factored out; no padding with basic-concept explanations.

4 / 5

Actionability

Fully executable, copy-paste-ready curl commands for all four methods, real response structures, a worked jq filter, station ID table, and product-filter bitmask table covering the common cases.

5 / 5

Workflow Clarity

Each method's request/response is clearly laid out and the LocMatch→TripSearch handoff (lid) is explicit; the error-handling section lists codes but lacks a validate/retry feedback loop, though the skill is read-only so no destructive-operation cap applies.

4 / 5

Progressive Disclosure

A single well-organized file with clear section headers and a quick-reference table; no bundle files exist. The reference-heavy material (product classes, station IDs) is inlined rather than split into separate files, which is acceptable but keeps it just below the top anchor.

4 / 5

Total

17

/

20

Passed

Description

87%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, well-targeted description that clearly states the domain, lists multiple concrete capabilities, and provides explicit 'Use when...' trigger guidance. Minor keyword synonym coverage could be expanded.

DimensionReasoningScore

Specificity

Names the domain (Austrian rail travel) and lists several concrete actions — 'planning train journeys', 'checking departures/arrivals', 'looking for service disruptions' — with only minor coverage gaps (no mention of ticket/price lookup).

4 / 5

Completeness

Explicitly answers both 'what' ('Austrian rail travel planner (ÖBB Scotty)') and 'when' ('Use when planning train journeys... checking departures/arrivals... service disruptions') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ('planning train journeys in Austria', 'checking departures/arrivals', 'service disruptions') plus synonyms (S-Bahn, regional trains); a few common variations like 'train times' or 'ÖBB app' are missing.

4 / 5

Distinctiveness Conflict Risk

A clearly defined niche (ÖBB / Austrian rail) with distinct, specific triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mitsuhiko/agent-stuff
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.