Name: railway
Rating: 60.8 (1 reviews)
Author: membranedev

railway

Railway integration. Manage data, records, and automate workflows. Use when the user wants to interact with Railway data.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/railway/SKILL.md

Quality

Content

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

The content is highly actionable with copy-paste commands and a clear connection workflow including state polling, but it carries a few unnecessary background paragraphs and odd step numbering that prevent a top score. Splitting the proxy reference into a bundle file would further improve organization.

Suggestions

Remove the background intro paragraph ('Railway is a cloud platform...') and the 'so you can focus on the integration logic' editorializing; Claude already knows what Railway is.

Fix the step numbering so 'Step 1' is explicitly labeled before '1b' and 'Step 2' references resolve cleanly.

Move the proxy request flag table and detailed action-discovery output into a separate references file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and tables, but the opening 'Railway is a cloud platform that simplifies deploying...' paragraph and editorial phrasing like 'so you can focus on the integration logic rather than auth plumbing' explain background Claude does not need, matching the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	It provides copy-paste-ready, fully executable commands throughout (npm install, membrane login, connection ensure, action run) plus a concrete proxy flag table, covering the common cases.	5 / 5
Workflow Clarity	The install→authenticate→connect→poll-state→search→run sequence is clear with an explicit state-based feedback loop (BUILDING→READY/CLIENT_ACTION_REQUIRED and 'poll again'), but the '1b' and 'Step 2' numbering without a labeled 'Step 1' introduces minor confusion.	4 / 5
Progressive Disclosure	The single SKILL.md is well-sectioned (Overview, Working with Railway, Popular actions, Best practices) with no nested references, but at over 50 lines with no bundle files some inline content like the proxy flag table could live in a separate reference, keeping it just below the fully-optimized anchor 5.	4 / 5
	Total	16 / 20 Passed

Description

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

The description correctly uses third person and provides an explicit 'Use when' trigger tied to a distinctive named platform, but the capability list is generic rather than reflecting Railway's actual deployment-focused actions. Strengthening specificity would lift the otherwise solid trigger and completeness scores.

Suggestions

Replace generic verbs with concrete Railway capabilities, e.g. 'Deploy services from Git, manage environments and variables, and monitor deployments.'

Broaden the trigger to match what users actually ask for, e.g. 'Use when the user wants to deploy, manage, or troubleshoot apps on Railway.'

Avoid framing Railway narrowly as 'data' interaction, which undersells its deployment-oriented purpose.

Dimension	Reasoning	Score
Specificity	The description names the Railway domain but its actions ('Manage data, records, and automate workflows') are generic verbs rather than concrete Railway capabilities like deploying services or managing environments, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Railway data'), but the 'what' is vague so it does not reach the fully-concrete anchor 5.	4 / 5
Trigger Term Quality	'Railway' is the key proper-noun trigger, repeated in 'Railway integration' and 'interact with Railway data', giving good natural keyword coverage, though a few natural phrases like 'deploy to Railway' are missing.	4 / 5
Distinctiveness Conflict Risk	Railway is a specific named cloud platform with a distinct trigger phrase, giving it a clear niche with minimal risk of conflicting with other skills.	5 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/railway/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.