CtrlK
BlogDocsLog inGet started
Tessl Logo

railway-api

Railway.com GraphQL API automation for projects, services, deployments, and environment variables. Use when automating Railway operations, querying project data, managing deployments, setting variables via API, or integrating Railway into workflows.

66

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/railway-api/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 well-structured, actionable API reference with strong progressive disclosure and real bundle files. Its main weaknesses are some redundant sections and the absence of explicit validation checkpoints around destructive mutation workflows.

Suggestions

Remove or consolidate the redundant 'Quick Reference' section (it restates queries already shown in 'Common Operations') and the bottom 'References'/'Learning Path' sections (already covered by the 'Progressive Disclosure Structure' section) to tighten the token budget.

Add explicit validation checkpoints to destructive operations, e.g. after variableUpsert/deploymentTrigger/serviceCreate/variableDelete, instruct Claude to inspect the response `errors` array before proceeding, forming a validate -> fix -> retry loop.

Replace the comment-only pseudocode in the 'Integration Patterns' sections with concrete, executable examples or link to the relevant scripts/query files instead of leaving placeholder comments.

DimensionReasoningScore

Conciseness

The body is mostly lean and reference-oriented with executable code, but the 'Quick Reference' section restates queries already shown and the bottom 'References'/'Learning Path' sections restate navigation already in the 'Progressive Disclosure Structure' section, adding redundant tokens.

3 / 5

Actionability

Provides concrete, mostly copy-paste-ready curl commands and GraphQL queries/mutations with full variable inputs covering common cases; minor gaps where integration-pattern sections are comment-only pseudocode rather than executable code.

4 / 5

Workflow Clarity

A numbered Quick Start and Learning Path give a rough sequence, but destructive operations (variableUpsert, deploymentTrigger, serviceCreate, variableDelete) lack explicit validate-before-proceeding checkpoints; general error-handling advice is not woven into the steps, capping this at 3.

3 / 5

Progressive Disclosure

Clear overview with a dedicated Progressive Disclosure Structure section, one-level-deep references whose paths (graphql-endpoint.md, authentication.md, common-queries.md, common-mutations.md, api-limitations.md) all exist in references/, plus scripts/ — easy to navigate.

5 / 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 clear, specific, and well-scoped to Railway.com GraphQL API automation, explicitly answering both what the skill does and when to use it. Trigger term coverage is strong with only minor synonym gaps.

DimensionReasoningScore

Specificity

Names the domain and lists multiple concrete actions (projects, services, deployments, environment variables; automating, querying, managing deployments, setting variables), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers 'what' (Railway.com GraphQL API automation for projects, services, deployments, environment variables) and 'when' (Use when automating Railway operations...) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases ('automating Railway operations', 'querying project data', 'managing deployments', 'setting variables via API'), but lacks some synonym variations; good coverage with a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

Clearly scoped to Railway.com GraphQL API with distinct, niche-specific triggers, giving minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fernandezbaptiste/Skrillz
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.