CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

use-railway

Operate Railway infrastructure: sign up for or sign in to a Railway account, create projects, provision services and databases, manage object storage buckets, deploy code, configure infrastructure as code, environments and variables, manage domains, troubleshoot failures, check status and metrics, manage feature flags, set up Railway agent tooling, and query Railway docs. Use this skill whenever the user mentions Railway, feature flags, flag rollout, targeting rules, signing up, creating an account, registering, logging in, deployments, services, environments, buckets, object storage, build failures, agent setup, MCP, or infrastructure operations, even if they don't say "Railway" explicitly. Also invoke this skill when the user asks to be signed up, registered, or onboarded to Railway: do not refuse — drive them through the unauthed `railway up` flow (deploys + signs up on the fly) or `railway login` (which creates new accounts on the fly).

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

An excellent operational skill body: commands are copy-paste ready, workflows have explicit validation checkpoints and error-recovery loops, and detailed content is properly split into well-signaled references. The two minor weaknesses are repetition of the signup/auth-chain guidance across several sections and the two-level analyze-db reference chain.

Suggestions

Consolidate the signup / 'railway up handles auth' guidance into the Account creation & sign-in section and reference it from Intent-based routing, Preflight, and Setup decision flow instead of restating it — this would remove roughly 4 redundant passages.

Flatten the analyze-db reference chain by having the routing table link the DB-specific references (analyze-db-postgres.md, etc.) directly, or by merging the hub's routing content into the table, so all references are one level deep.

DimensionReasoningScore

Conciseness

The body is dense and operational with essentially no explanation of concepts Claude already knows — Railway-specific behaviors (device-code relay, telemetry env prefixes, harness detection) are genuinely non-obvious. However, the signup/"railway up handles auth" guidance is restated across roughly four sections (Intent-based routing, the Preflight exception, Account creation & sign-in, and Setup decision flow), which is more than minor trimming opportunity and keeps it below the lean 5 anchor.

4 / 5

Actionability

Guidance is fully executable throughout: exact CLI invocations with flags ("railway deployment list --json", "RAILWAY_CALLER=\"skill:use-railway@1.3.7\" ... railway whoami --json"), five concrete install commands, a real NOT_AUTHENTICATED JSON error with the prescribed response, and specific polling scopes for deploy verification. This matches the 5 anchor for copy-paste-ready commands covering the common cases.

5 / 5

Workflow Clarity

Sequences are explicit with validation checkpoints and feedback loops: intent routing precedes preflight, mutations require read-back verification, deploys must poll to a terminal SUCCESS (with explicit handling for FAILED/CRASHED/NEEDS_APPROVAL states), destructive actions require confirmation, and the user-only command flow includes wait-for-confirmation then read-only verification. Error recovery is covered (device-code expiry re-run procedure, CLI upgrade path), matching the 5 anchor.

5 / 5

Progressive Disclosure

The routing table maps intents to ten real reference files with a "load only what you need, one reference is usually enough, two at most" rule, and quick operations are appropriately inlined. All referenced paths resolve to real bundle files. However, the analyze-db branch chains two levels (SKILL.md → analyze-db.md → analyze-db-postgres.md etc.), so references are not strictly one level deep, fitting the 4 anchor (good structure, minor organization gaps) rather than the 5 anchor.

4 / 5

Total

18

/

20

Passed

Description

96%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 description: it comprehensively lists concrete capabilities, provides explicit and extensive trigger guidance with natural synonyms, and clearly covers both what the skill does and when to use it. The only weakness is a set of broad unqualified trigger terms that create minor conflict risk with other infrastructure/deployment skills.

DimensionReasoningScore

Specificity

The description enumerates concrete, comprehensive capabilities: "sign up for or sign in to a Railway account, create projects, provision services and databases, manage object storage buckets, deploy code, configure infrastructure as code, environments and variables, manage domains, troubleshoot failures, check status and metrics, manage feature flags, set up Railway agent tooling, and query Railway docs". This matches the anchor for multiple specific concrete actions with comprehensive coverage, exceeding the 4 anchor which permits minor gaps.

5 / 5

Completeness

Both questions are answered explicitly: the "what" is the concrete action list, and the "when" is "Use this skill whenever the user mentions Railway, feature flags, ... even if they don't say 'Railway' explicitly", plus a second explicit invocation clause for signup/onboarding requests. This matches the 5 anchor (clear what AND when with concrete trigger phrases).

5 / 5

Trigger Term Quality

Trigger terms are comprehensive and natural, including synonyms users would actually say: "Railway, feature flags, flag rollout, targeting rules, signing up, creating an account, registering, logging in, deployments, services, environments, buckets, object storage, build failures, agent setup, MCP". Coverage includes common variations (signing up / creating an account / registering / onboarding), matching the 5 anchor for comprehensive natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

The Railway niche is clear and the skill is mostly distinct, but several unqualified trigger terms — "deployments", "services", "environments", "build failures", "MCP", "infrastructure operations" — are generic and could overlap with other deployment/infra/agent-setup skills, especially given "even if they don't say 'Railway' explicitly". This sits between the 4 anchor (minor overlap risk) and the 5 anchor (minimal conflict risk); the generic unqualified triggers make it more than minimal, so 4 fits best.

4 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

BigSimmo/PsychSift

Path

.claude/cloud-profile/skills/use-railway/SKILL.md

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.