Name: rutter
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

rutter

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

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/rutter/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 content is a strong, executable CLI workflow with explicit connection-state validation checkpoints, held back slightly by a padded intro and minor sequencing/labeling inconsistencies rather than structural problems.

Suggestions

Trim the introductory paragraph about who uses Rutter and the "focus on integration logic rather than auth plumbing" aside to reduce unneeded explanation.

Replace the dangling "Skip to Step 2" / "1b" labels with a consistent numbered step sequence so the connection-to-action flow is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command documentation, but the intro ("Rutter is an API that provides unified access... used by developers and companies... for accounting, lending, or inventory management") and phrases like "so you can focus on the integration logic rather than auth plumbing" add explanation Claude does not need.	3 / 5
Actionability	Concrete, executable commands are provided throughout (membrane login, connection ensure, action run, request proxy) with flag tables and JSON examples; minor gaps remain where placeholders like CONNECTION_ID and <actionId> require substitution.	4 / 5
Workflow Clarity	The sequence (install, auth, connect, poll until READY, search actions, run) is clear with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but references to "Step 2" and a lone "1b" heading without a numbered step framework introduce minor gaps.	4 / 5
Progressive Disclosure	No bundle files exist and the skill is a single well-sectioned document with clear ## headings; it is over 50 lines and could arguably split the proxy flag table or action schema details into reference files, but the organization is solid.	4 / 5
	Total	15 / 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 is well-formed with both a what and an explicit Use-when trigger tied to a distinctive named API, but its capability wording is generic and the trigger lacks concrete scenario synonyms.

Suggestions

Replace generic verbs ("Manage data, records") with concrete Rutter actions such as "fetch orders, sync products, and query customer records".

Expand the Use-when clause with natural trigger scenarios, e.g. "Use when the user wants to query Rutter orders, products, subscriptions, or e-commerce data."

Dimension	Reasoning	Score
Specificity	Phrases "Manage data, records, and automate workflows" name the Rutter domain and a few actions, but the actions are generic ("manage", "records") rather than concrete capabilities like fetching orders or syncing products.	3 / 5
Completeness	It states a clear "what" ("Rutter integration. Manage data, records, and automate workflows.") and an explicit "when" ("Use when the user wants to interact with Rutter data."), but the when clause could be more specific about triggering scenarios.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Rutter data" surfaces the core term "Rutter" and "data", but it lacks synonyms or scenario variations a user might naturally say (e.g. orders, products, e-commerce sync).	3 / 5
Distinctiveness Conflict Risk	"Rutter" is a specific named API giving a clear niche with low conflict risk, but the generic "manage data, records, automate workflows" phrasing leaves minor overlap with general data-management skills.	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
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/rutter/SKILL.md
Commit: f484c82

Reviewed: 4 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.