railway-troubleshooting

Railway Docker cache troubleshooting for Dr. Sophia AI deployments. Covers cache detection, force rebuild methods, version verification, deployment validation. Use when Railway shows old code after deployment, deployments not updating, Docker cache issues, or version mismatches between local and deployed code.

Quality

80%

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 ./skill-builder-package/examples/railway-troubleshooting/SKILL.md

Quality

Content

67%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 body is highly actionable with concrete commands and a verification feedback loop, but it carries redundant sections and time-sensitive version/date details that should live in a deprecated section. Progressive disclosure is sound with a real referenced script.

Suggestions

Move the "Real Example (Sep 24, 2025)" anecdote and scattered version numbers (v11.4, v13.2.8) into a clearly labeled "Past incidents / deprecated versions" section so time-sensitive data does not bloat the active guidance.

Remove the standalone "Quick Fix One-Liner" section since it duplicates Method 1's timestamp approach; keep one canonical method and point to the automated script instead.

Reference scripts/force-rebuild.sh once as a markdown link and replace the two other verbatim path repetitions with "the script above" to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	The core guidance is action-oriented, but time-sensitive details ("Sep 24, 2025", "Oct 24, 2025", v11.4/v13.2.8) are scattered outside a deprecated section, and the "Real Example" anecdote plus a redundant Quick Fix One-Liner add padding that could be tightened.	3 / 5
Actionability	Provides concrete executable commands (grep, curl\|jq, git commit/push, the force-rebuild script) with only minor gaps — Method 2 uses an ellipsis (`...`) and placeholder line numbers rather than fully complete code.	4 / 5
Workflow Clarity	A clear detect → rebuild → verify sequence exists with an explicit Deployment Verification Checklist and a feedback loop ("If wrong version, force rebuild using Method 1"), but the overall flow across sections is not ordered into one decision tree, leaving minor sequencing gaps.	4 / 5
Progressive Disclosure	Structure is good with clear section headers and a one-level-deep reference to a real bundle file (scripts/force-rebuild.sh), but the script path is repeated verbatim three times as plain text rather than a markdown link, a minor organization gap.	4 / 5
	Total	15 / 20 Passed

Description

92%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 is strong: it states what the skill does, when to use it with concrete trigger phrases, and carves out a distinct niche. Its only gap is trigger-term breadth, where a few natural synonyms would round out coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "cache detection, force rebuild methods, version verification, deployment validation" — giving comprehensive coverage of the troubleshooting domain, matching the anchor that rewards several specific concrete actions.	5 / 5
Completeness	Explicitly answers both what ("Railway Docker cache troubleshooting... Covers cache detection, force rebuild methods, version verification, deployment validation") and when ("Use when Railway shows old code after deployment...") with concrete trigger phrases, matching the top anchor exactly.	5 / 5
Trigger Term Quality	Includes natural user phrases ("Railway shows old code after deployment", "deployments not updating", "Docker cache issues", "version mismatches") with good coverage, but stops short of the synonyms/file-extensions breadth the top anchor requires and omits a few variants like "stale build" or "cache busting".	4 / 5
Distinctiveness Conflict Risk	Occupies a clear narrow niche (Railway Docker cache troubleshooting for a specific deployment) with distinct triggers, making overlap with other skills minimal.	5 / 5
	Total	19 / 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: skill-builder-package/examples/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.