AB railway-metrics
Query resource usage metrics for Railway services. Use when user asks about resource usage, CPU, memory, network, disk, or service performance like "how much memory is my service using" or "is my service slow".
Query resource usage metrics for Railway services.
As a process B 67/100 · Nearly there — weak spots: when it triggers, consistency, running it twice
ProcedureAI and agentsData and analyticstype and topics are labelled automatically from the skill text
How to improve
For the model run — optional
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "dependencies"
Process rating: all ten parameters 67/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 8 mutating operations with no state check
- 40Consistency. Frontmatter name (railway-metrics) differs from the folder (metrics)
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 14 steps
- 100Execution cost. Instruction body is 1394 tokens
- low 11 top-level sections: this looks like several domains in one skill
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
- +4Description does not say when NOT to use the skill (false activations)
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 210: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 14 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.