Name: routable
Rating: 48.8 (1 reviews)
Author: membranedev

routable

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

Quality

53%

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

Quality

Content

48%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 CLI workflow guidance is concrete and well-sequenced with good state validation, but the body is undermined by a massive, irrelevantly-padded 'Routable Overview' bullet list (including unrelated software design patterns) that wastes the context window and is internally inconsistent with the stated accounts-payable purpose.

Suggestions

Remove or drastically trim the 'Routable Overview' bullet list, especially the unrelated design-pattern and generic-role entries that have nothing to do with Routable's AP domain.

Resolve the 'Popular actions' section by listing actual high-value Routable actions (e.g. create invoice, approve payment) instead of repeating the generic search command.

Move any retained entity/reference catalog to a separate references file and link to it from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The 'Routable Overview' is a ~150-item bullet list of generic nouns including unrelated GoF design patterns (Adapter, Bridge, Composite, Decorator, Facade, Flyweight, Proxy, Command, Visitor) and generic roles (Apprentice, Trainee, Intern) — severely padded content Claude already knows, matching the 'severely verbose; heavily padded' anchor.	1 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands (npm install, membrane login, connection ensure, action list/run, request) with a documented flags table, but relies on unresolved placeholders (CONNECTION_ID, QUERY) and the 'Popular actions' section merely repeats the search command without listing actual actions, fitting anchor 4.	4 / 5
Workflow Clarity	The connection flow is a clear sequence (install -> login -> connection ensure -> poll until READY) with explicit state-based checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-act-poll feedback loop, fitting anchor 4; not a 5 because there is no explicit validate-fix-retry checklist.	4 / 5
Progressive Disclosure	Section headers provide structure, but the ~150-line inlined 'Routable Overview' list is bulk content that should be split into a separate reference file (no bundle files exist), fitting 'some structure but content that should be separate is inline'.	3 / 5
	Total	12 / 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 correctly identifies the product and includes a 'Use when' trigger, but its capability language is generic ('manage data, records, automate workflows') rather than reflecting Routable's actual accounts-payable domain, and it lacks concrete trigger terms like invoices or payments.

Suggestions

Replace generic actions with concrete AP capabilities, e.g. 'Process invoices, manage approvals, and send payments via Routable.'

Add natural trigger terms users would say: 'Use when the user wants to manage invoices, approvals, payments, or accounts payable in Routable.'

Align the description with the body's stated purpose (accounts payable automation) to avoid the current mismatch.

Dimension	Reasoning	Score
Specificity	It names the domain ('Routable integration') but the actions are generic ('Manage data, records, and automate workflows') rather than concrete AP tasks like invoice processing or payments, matching the 'names the domain but actions are minimal or generic' anchor; not a 3 because no concrete actions are listed.	2 / 5
Completeness	Both 'what' (Routable integration; manage data/records; automate workflows) and 'when' ('Use when the user wants to interact with Routable data') are present, but the 'when' could be more explicit with concrete triggers, matching anchor 4 rather than 5.	4 / 5
Trigger Term Quality	It includes the product name and 'data', 'records', 'workflows' as in 'interact with Routable data', but misses natural synonyms users would say (invoices, payments, accounts payable, AP), fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Routable' gives it a distinct trigger with minimal conflict risk, though the generic 'manage data, records, automate workflows' phrasing leaves minor overlap with other integration skills, fitting anchor 4.	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/routable/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.