BD renfe
Search Renfe trains in Spain (AVE, AVLO, regional and other trains sold on renfe.com) and book them for the user with the renfe CLI, paying by Bizum with the user's approval in their bank app. Use for Spanish train timetables, fares, cheapest-day questions, and buying or downloading Renfe tickets.
Search Renfe trains in Spain (AVE, AVLO, regional and other trains sold on renfe.com) and book them for the user with the renfe CLI, paying by Bizum with the…
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 298 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
Process rating: all ten parameters 48/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Inputs and preconditions. Does not say what the process needs to start
- 60Tools and files. Uses tools (bash, write) that frontmatter does not declare
- 60Consistency. The Hermes dialect needs category and tags
- 100Steps. 14 steps
- 100Execution cost. Instruction body is 1092 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low The response is described with custom markup (3 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 298: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (4 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.