Name: railz
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

railz

Railz integration. Manage data, records, and automate workflows. Use when the user wants to interact with Railz data.

Quality

62%

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/railz/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 a solid, executable CLI guide with a well-instrumented connection workflow and good command coverage. Its main weaknesses are rhetorical padding, a thin/redundant "Popular actions" section, and a dangling "Step 2" reference that breaks the sequence.

Suggestions

Trim rhetorical padding such as "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection".

Resolve the dangling "skip to Step 2" reference by labeling the action-search/run section as Step 2 or removing the cross-reference.

Move the connection-state machine and proxy flag table into a reference file (e.g. CONNECTION_STATES.md) and keep SKILL.md as an overview.

Dimension	Reasoning	Score
Conciseness	The body is largely command-focused and useful, but retains rhetorical padding ("so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection") and background on Railz's fintech use that Claude does not strictly need.	3 / 5
Actionability	It provides copy-paste-ready CLI commands with real flags for install, login, connection, action search/run, and proxy requests, with only minor necessary placeholders (CONNECTION_ID, <actionId>).	4 / 5
Workflow Clarity	The connect→poll→state-check flow has explicit feedback loops for READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, but a dangling "Step 2" reference and no verification of action or proxy results leave minor gaps.	4 / 5
Progressive Disclosure	The single file is well-organized into clear headers with no nested references, but at ~140 lines the detailed connection state machine and proxy flag table could be split into one-level-deep reference files.	4 / 5
	Total	15 / 20 Passed

Description

57%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 third-person, includes an explicit Use-when clause, and is anchored to a distinct brand, so it clears the core bars. It loses points for generic action verbs and thin trigger-term coverage that omits the accounting/QuickBooks/Xero vocabulary users actually employ.

Suggestions

Replace generic verbs with concrete Railz capabilities, e.g. "Query accounting data, fetch financial reports, and automate reconciliation workflows."

Add natural trigger terms users say, such as "accounting data", "QuickBooks", "Xero", or "financial statements".

Make the Use-when clause more specific, e.g. "Use when the user wants to access or analyze accounting data through Railz (QuickBooks, Xero, etc.)."

Dimension	Reasoning	Score
Specificity	The description names the Railz domain but its actions ("Manage data, records, and automate workflows") are generic abstractions rather than concrete operations like fetch, extract, or create.	2 / 5
Completeness	Both a "what" (manage data, records, automate workflows) and an explicit "when" ("Use when the user wants to interact with Railz data") are present, though the trigger clause is generic rather than concrete.	4 / 5
Trigger Term Quality	It surfaces the brand keyword "Railz" and "Railz data" but omits natural synonyms a user would say (accounting data, QuickBooks, Xero, financial data) that the body itself references.	3 / 5
Distinctiveness Conflict Risk	The distinct "Railz" niche keeps conflict risk low, but the generic "manage data, records" phrasing could overlap with broader data-management skills.	4 / 5
	Total	13 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/railz/SKILL.md
Commit: f484c82

Reviewed: 5 days 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.