SKILLEMALL.ai

AC railway-status

Check current Railway project status for this directory. Use when user asks "railway status", "is it running", "what's deployed", "deployment status", or about uptime. NOT for variables or configuration queries - use railway-environment skill for those.

davila7/claude-code-templates Agent Skills author: davila7 MIT 1 file body ≈ 505 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Check current Railway project status for this directory.

As a process C 56/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, consistency

ProcedureAI and agentsOperations and projectsInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
98/100
safety, quality, tests
Safety 60%
100
Quality 40%
96
Run on models
none yet
Process rating
C
56/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

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-key unknown frontmatter key "dependencies"

    Process rating: all ten parameters 56/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 11 mutating operations with no state check
    • 40Consistency. Frontmatter name (railway-status) differs from the folder (status)
    • 50When it triggers. No condition that starts the skill
    • 60Result and completion. Output format stated, no completion criterion
    • 85Steps. 14 steps, 2 vague phrases
    • 100Tools and files. Tools declared in frontmatter
    • 100Execution cost. Instruction body is 505 tokens

    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

    • +2Single-language instructions
    • +5Description quotes 4 example trigger phrases
    • +4Description says when NOT to use the skill
    • +3Description length 253: enough signal without eating the budget
    • +4Structure: 9 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: 96.