CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

railway-auth

Railway authentication and token management. Use when logging into Railway, creating API tokens, setting up CI/CD authentication, or verifying Railway credentials.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is railway-auth in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

88%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, highly actionable skill body: executable commands with expected outputs, per-operation verification checkpoints, troubleshooting feedback loops, and clearly signaled bundle references. Its only real weaknesses are mild redundancy (When-to-Use sections and some inline tables duplicating reference files) that costs a little token efficiency and disclosure economy.

DimensionReasoningScore

Conciseness

The body is largely lean — commands, numbered processes, and verification outputs with almost no explanation of concepts Claude already knows. Minor trimmable padding remains: the 'When to Use' section and per-operation 'Use When' lines duplicate the description and each other, and heavy '---' separators inflate the layout.

4 / 5

Actionability

Every operation provides copy-paste-ready material: 'railway login', 'railway login --browserless', 'railway whoami', complete curl commands with exact headers and GraphQL endpoints, and full GitHub Actions and GitLab CI YAML examples. Specific expected outputs ('Logged in as: your-email@example.com') make verification concrete.

5 / 5

Workflow Clarity

Each operation is numbered and immediately followed by an explicit verification step ('railway whoami' after login, verify via API for tokens), and a troubleshooting table provides issue-to-fix feedback loops for error recovery. These are non-destructive auth operations, so no batch/destructive cap applies.

5 / 5

Progressive Disclosure

The overview-to-detail structure is good: a dedicated References section clearly signals the two real one-level-deep files (token-types.md, token-troubleshooting.md) with descriptions. Not a 5 because the inline troubleshooting table and token-type table partially duplicate content the referenced files exist to hold, and CI/CD pipeline examples could live in a reference file.

4 / 5

Total

18

/

20

Passed

Description

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

A solid, third-person description with an explicit 'Use when' trigger clause and several concrete, naturally-phrased actions in a clearly bounded domain. It sits just below top marks due to modest coverage gaps (no CLI/env-var terms like RAILWAY_TOKEN, no logout/troubleshooting mentions) and slight overlap potential with sibling Railway skills.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'logging into Railway, creating API tokens, setting up CI/CD authentication, or verifying Railway credentials' — in the specific Railway domain. Not a 5 because coverage has minor gaps (no mention of logout, troubleshooting, or the browserless/device-flow login variant).

4 / 5

Completeness

Both 'what' ('Railway authentication and token management') and an explicit 'Use when...' clause with concrete triggers are present. Not a 5 because the 'what' clause is a compact domain statement rather than enumerating the multiple specific capabilities the body actually covers.

4 / 5

Trigger Term Quality

Natural user phrases like 'logging into Railway', 'creating API tokens', and 'CI/CD authentication' are present and would be said verbatim by users. Not a 5 because common variations such as 'Railway CLI', 'RAILWAY_TOKEN', or 'deploy' are missing.

4 / 5

Distinctiveness Conflict Risk

The Railway-specific triggers ('Railway credentials', 'Railway' login) make it mostly distinct with minimal conflict risk. Not a 5 because 'setting up CI/CD authentication' has minor overlap with sibling railway-api/railway-automation skills and generic CI/CD skills.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

fernandezbaptiste/Skrillz

Path

.claude/skills/railway-auth/SKILL.md

Reviewed

Table of Contents

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.