BD railway-environment
Query, stage, and apply configuration changes for Railway environments. Use for ANY variable or env var operations, service configuration (source, build settings, deploy settings), lifecycle (delete service), and applying changes. Prefer over railway-status skill for any configuration or variable queries.
Query, stage, and apply configuration changes for Railway environments.
As a process D 48/100 · Unfinished process — References files that are not bundled: ../reference/environment-config.md, ../reference/variables.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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
- warning
missing-refreference to a missing file: ../reference/environment-config.md - warning
missing-refreference to a missing file: ../reference/variables.md - note
frontmatter-keyunknown frontmatter key "dependencies"
Process rating: all ten parameters 48/100
- 0Tools and files. 2 referenced file(s) missing: ../reference/environment-config.md, ../reference/variables.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 31 mutating operations with no state check
- 40Consistency. Frontmatter name (railway-environment) differs from the folder (environment)
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 31 steps
- 100Failures and branches. 4 branches, has a failure section
- 100Execution cost. Instruction body is 2597 tokens
- 100Progress reporting. Reports progress
- low 13 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +2Single-language instructions
- +3Description length 306: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 31 items
- +3Output format is stated explicitly
- +4Has examples (23 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.