railway-troubleshooting

Railway debugging and issue resolution. Use when deployments fail, builds error, services crash, performance degrades, or networking issues occur.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

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

A well-structured troubleshooting skill with a useful decision tree, executable CLI commands, and real one-level-deep references. Its weaknesses are redundant trigger/reference restatements across multiple sections and missing validation feedback loops around the destructive rebuild and database-recovery operations.

Suggestions

Add explicit validation checkpoints to destructive workflows, e.g. after force-rebuild verify the service is healthy before proceeding, and after a database restart confirm connectivity with `railway run psql $DATABASE_URL -c "SELECT 1"`.

Collapse the redundant trigger listings: keep the decision tree and either the per-operation "When to use" lines or the "When to Use This Skill" section, not all three.

Merge the inline "See: references/..." pointers and the "Additional Resources" section into a single consolidated reference block to remove duplication.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of beginner-concept padding, but it carries redundant structure: the top decision tree, the per-operation "When to use" lines, the standalone "When to Use This Skill" section, and the "Additional Resources" list all restate the same triggers and reference paths.	3 / 5
Actionability	Provides concrete executable commands (railway status, railway logs --tail 500, railway run psql $DATABASE_URL -c "SELECT 1", ./scripts/force-rebuild.sh), with only minor gaps where steps are comment-only placeholders (e.g. "# Check private networking enabled" with no actual command).	4 / 5
Workflow Clarity	Each operation is numbered into a clear sequence, but destructive/batch operations (force-rebuild with --no-cache, database restart in Emergency Recovery) lack explicit validate-then-proceed feedback loops, which caps this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	Good one-level-deep structure: a decision-tree overview plus five operations, each clearly signaling real bundle files (references/.md, scripts/.sh) that all exist on disk; minor gap is that inline "See" links and the trailing "Additional Resources" list duplicate each other rather than being consolidated.	4 / 5
	Total	14 / 20 Passed

Description

73%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 cleanly states a niche domain and pairs it with an explicit, concrete "Use when" trigger clause covering five failure modes. Its main weakness is a generic "what" that says "debugging and issue resolution" rather than naming the specific diagnostic and recovery actions the skill performs.

Suggestions

Replace the generic "Railway debugging and issue resolution" with concrete actions, e.g. "Diagnose Railway deployment failures, debug runtime crashes, troubleshoot networking, and run recovery procedures."

Add a couple of natural trigger synonyms (e.g. "build failed", "deploy failed", "service won't start") to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("Railway debugging and issue resolution") with concrete trigger scenarios, but the stated actions ("debugging", "issue resolution") remain generic rather than enumerating specific capabilities like log analysis or recovery procedures.	3 / 5
Completeness	Both "what" (Railway debugging and issue resolution) and "when" (explicit "Use when..." with five concrete conditions) are present; the "what" half is somewhat terse and could be more specific about what the skill actually does.	4 / 5
Trigger Term Quality	"deployments fail, builds error, services crash, performance degrades, networking issues occur" are natural phrases users would say, giving good coverage, though a few common variants (e.g. "deploy", "build failed") are absent.	4 / 5
Distinctiveness Conflict Risk	"Railway debugging" carves a clear platform-specific niche with distinct triggers, making conflict with other skills unlikely.	5 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: fernandezbaptiste/Skrillz
Path: skills/railway-troubleshooting/SKILL.md
Commit: 93ed392

Reviewed: 1 day 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.