observability-railway-deploy

Deploy LGTM observability stack to Railway cloud. Use when deploying cloud-hosted observability with team access.

Quality

61%

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/observability-railway-deploy/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.

The content is a compact, well-structured overview of a deployment workflow, but it lacks inline executable commands and has a verification step that is too vague plus a missing referenced script.

Suggestions

Inline the actual Railway CLI commands (login, template deploy, volume attach, status) instead of only naming the steps, so guidance is copy-paste ready.

Strengthen the verify step into a concrete feedback loop (run specific healthcheck commands, expected output, and what to fix on failure).

Either add the missing scripts/get-railway-urls.sh or remove its reference so the Scripts section points only at files that exist.

Dimension	Reasoning	Score
Conciseness	The body is lean with a concise intro, compact numbered workflow, and a short cost estimate; the only minor trim is the intro restating the frontmatter description, keeping it just below a 5.	4 / 5
Actionability	Steps name concrete targets (Template 8TLSQD, service names) and point at scripts, but no actual Railway CLI commands are inline and one referenced script (get-railway-urls.sh) is missing, so guidance is incomplete rather than copy-paste ready.	3 / 5
Workflow Clarity	Seven steps are clearly sequenced and step 7 is an explicit verify step, but the verification ("health checks, telemetry flow") is vague with no error-recovery feedback loop, leaving checkpoints implicit.	3 / 5
Progressive Disclosure	Sections are well-organized and script references are one level deep in a dedicated Scripts section, but the dangling reference to the nonexistent get-railway-urls.sh is a minor organization gap below a 5.	4 / 5
	Total	14 / 20 Passed

Description

62%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 covers what and when with a specific cloud niche, but relies on a single trigger phrase and jargon (LGTM) while omitting common synonym terms users might actually say.

Suggestions

Add natural synonyms and component names (e.g., Grafana, Loki, monitoring, metrics, logs) to the trigger clause so it matches more phrasings users would actually say.

List 1-2 more concrete actions (e.g., configure retention, expose OTLP endpoint) to lift specificity beyond a single deploy verb.

Expand the "Use when" clause with a couple of concrete scenarios rather than one to push completeness toward a 5.

Dimension	Reasoning	Score
Specificity	"Deploy LGTM observability stack to Railway cloud" names the domain plus one concrete action (deploy), but offers no further specific actions, matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It states both a clear "what" (deploy the LGTM stack to Railway) and an explicit "when" ("Use when deploying cloud-hosted observability with team access"), but the trigger phrase is a single scenario rather than multiple concrete triggers, keeping it just below a 5.	4 / 5
Trigger Term Quality	"cloud-hosted observability", "Railway", and "team access" give some natural keywords, but common synonyms users would say (Grafana, monitoring, metrics, logs) are missing, so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	The Railway + LGTM stack niche is mostly distinct with minimal conflict risk, though it could still overlap slightly with a generic observability-deployment skill, placing it just below a 5.	4 / 5
	Total	14 / 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

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