Name: railsr
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

railsr

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

Quality

70%

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/railsr/SKILL.md

Quality

Content

75%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 with copy-paste commands and a clear connection workflow with validation checkpoints, but it carries marketing fluff and background explanation that hurt conciseness, and it could trim the Railsr overview.

Suggestions

Remove marketing phrasing like 'so you can focus on the integration logic rather than auth plumbing' and 'This will burn less tokens and make communication more secure' to tighten conciseness.

Shorten the opening Railsr background paragraph to one line of essential context, since Claude does not need the embedded-finance market framing.

Label the 'Step 2' target explicitly (e.g. '## Step 2: Search for actions') so the 'skip to Step 2' references resolve clearly.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes marketing padding ('focus on the integration logic rather than auth plumbing', 'burn less tokens and make communication more secure') and unnecessary Railsr background that could be tightened, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Provides copy-paste-ready commands across all common cases (install, login, connection ensure, action list/run, request proxy) with a concrete options table, matching 'fully executable; copy-paste ready code or commands'.	5 / 5
Workflow Clarity	Sequences install → auth → connect → poll state → handle CLIENT_ACTION_REQUIRED → search/run, with explicit state validation and a feedback loop (poll again after the user acts); minor gaps like the unlabeled 'Step 2' keep it just below 5.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references and no bundle files present; over 50 lines so it does not qualify for the simple-skill 5, but structure and navigation are good with only minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

66%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 answers both what and when with an explicit trigger, and the Railsr brand makes it distinct, but its capability list is generic ('manage data, records, automate workflows') and lacks concrete, specific actions or trigger synonyms.

Suggestions

Replace the generic verb list ('Manage data, records, and automate workflows') with concrete Railsr capabilities such as 'create wallets, record transactions, and manage programs'.

Add natural trigger variations users might say, e.g. 'Use when the user wants to query Railsr wallets, transactions, or program accounts.'

Tie the trigger to the entity hierarchy shown in the body (Customer, Wallet, Transaction, Program, Account) so the description previews real actions.

Dimension	Reasoning	Score
Specificity	Names the domain (Railsr) and 2-3 actions ('Manage data, records, and automate workflows'), but the actions are generic verbs rather than concrete capabilities, matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor.	3 / 5
Completeness	Provides both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Railsr data'), but the 'what' is generic so it falls short of the fully concrete anchor 5.	4 / 5
Trigger Term Quality	Includes the relevant keyword 'Railsr' / 'Railsr data' with an explicit 'Use when' trigger, but as a proper-noun brand there are no natural synonyms or variations, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The 'Railsr' brand name is a distinct trigger with a clear niche and minimal conflict risk against other skills, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	15 / 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/railsr/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.