railway-logs

Railway log access and analysis for debugging and monitoring. Covers build logs, deploy logs, runtime logs, HTTP logs, filtering, search, and external export. Use when viewing logs, debugging Railway deployments, investigating errors, analyzing HTTP requests, filtering log output, or exporting logs to external systems.

Quality

85%

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

Quality

Content

71%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 and reasonably well-sequenced, but it is verbose for a logs skill: substantial content is inlined that already lives in the reference files, creating redundancy that competes with context. Trimming the duplicates would materially improve token efficiency.

Suggestions

Remove the Quick Reference table and the Best Practices structured-logging re-example; both duplicate content already covered in Operations 3 and 5 and in references/structured-logging.md — link instead.

Replace the inlined filter-syntax (Operation 5) and external-export (Operation 6) detail with a concise summary plus a link to references/log-filtering-syntax.md and references/external-export.md, keeping SKILL.md as an overview.

Add an explicit verification checkpoint to the export/streaming workflow (e.g., confirm the output file is non-empty or that the webhook returned 2xx before declaring success).

Dimension	Reasoning	Score
Conciseness	Mostly concrete and useful, but carries clear redundancy (Quick Reference repeats Operation commands; Best Practices re-inlines structured logging already shown in Operation 3) and some generic guidance Claude already knows (never log PII/keys).	3 / 5
Actionability	Copy-paste-ready CLI commands, filter-syntax examples, dashboard click-paths, and export script invocations cover the common cases with fully executable guidance.	5 / 5
Workflow Clarity	Prerequisites are sequenced with an explicit verify checkpoint (`railway status`) and a health-check debug loop exists, but export/streaming operations lack explicit validation checkpoints.	4 / 5
Progressive Disclosure	Real one-level-deep reference files are clearly signaled, but roughly 280 lines of filter syntax, structured logging, and external-export content are inlined in SKILL.md and duplicated in the reference files.	3 / 5
	Total	15 / 20 Passed

Description

100%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 exemplary: it concisely names concrete capabilities, uses natural trigger phrases, explicitly answers both what and when, and is clearly distinguishable from sibling skills. No changes needed.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (log access, analysis, filtering, search, external export) across four log types (build, deploy, runtime, HTTP), giving comprehensive coverage rather than vague abstraction.	5 / 5
Completeness	Clearly states what the skill does ('Covers build logs, deploy logs...') and provides an explicit 'Use when...' clause with concrete trigger phrases, answering both what and when.	5 / 5
Trigger Term Quality	Natural user-facing phrases appear throughout ('viewing logs', 'debugging Railway deployments', 'investigating errors', 'analyzing HTTP requests', 'filtering log output', 'exporting logs'), with synonym variation.	5 / 5
Distinctiveness Conflict Risk	Scoped to Railway logs with distinct triggers (Railway deployments, Railway log types), occupying a clear niche with minimal overlap risk against non-Railway skills.	5 / 5
	Total	20 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (643 lines); consider splitting into references/ and linking	Warning
relative_links	Relative link issues: 7 suspicious	Warning

	Total	14 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: skills/railway-logs/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.