Name: smartroutes
Rating: 59.2 (1 reviews)
Author: membranedev

smartroutes

SmartRoutes integration. Manage Organizations, Users, Filters. Use when the user wants to interact with SmartRoutes data.

Quality

67%

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

Quality

Content

68%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 well-structured and highly actionable, anchored in concrete CLI commands and a clear setup-to-execution sequence. Its main weakness is the absence of validation/verification steps for potentially destructive proxy and action-run operations, which caps workflow clarity.

Suggestions

Add explicit validation checkpoints after risky steps, e.g., verify a connection succeeded by re-running `connection list` before running actions, and confirm proxy responses before treating data as final.

Provide one fully worked example with realistic substituted values (a sample connectionId, action id, and intent) so the flow is copy-paste ready end-to-end.

Trim minor fluff such as 'so you can focus on the integration logic rather than auth plumbing' and 'burn less tokens' to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is lean and mostly commands with a tight overview, but includes minor padding such as 'so you can focus on the integration logic rather than auth plumbing' and 'burn less tokens', fitting the anchor for efficient content with minor over-explanation that could be trimmed.	4 / 5
Actionability	Concrete, executable `npx @membranehq/cli@latest` commands and a proxy flag table cover the common cases, but placeholders like CONNECTION_ID, ACTION_ID, and QUERY require substitution and no fully worked end-to-end example is given, matching the anchor for mostly executable guidance with minor gaps.	4 / 5
Workflow Clarity	A clear sequence exists (login, connect, discover actions, run, proxy), but there are no validation or verification checkpoints, and the proxy supports destructive methods (DELETE) without a verify loop, so per the destructive-operation cap workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	With no bundle files present, the single file is organized into clear sections (Overview, Working with SmartRoutes, First-time setup, Connecting, Proxy, Best practices); minor redundancy between 'Searching for actions' and 'Popular actions' keeps it just below a 5.	4 / 5
	Total	15 / 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 cleanly names the SmartRoutes domain and includes an explicit 'Use when' trigger, giving it solid completeness and strong distinctiveness. It is held back by a single generic action verb and trigger terms limited to the product name without natural synonyms.

Suggestions

Add more concrete verbs beyond 'Manage' (e.g., 'Create, update, and query Organizations, Users, and Filters') to raise specificity.

Expand the 'Use when' clause with natural trigger phrases users would say, such as 'routes, stops, deliveries, driver assignments, or SmartRoutes data'.

Mention the core SmartRoutes objects (Routes, Stops, Optimizations, Drivers) in the description to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Users, Filters" names the SmartRoutes domain and a single concrete action (Manage) applied to three objects, but offers no other verbs, matching the anchor that lists 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It states both the what ("Manage Organizations, Users, Filters") and an explicit when ("Use when the user wants to interact with SmartRoutes data"), but the when is generic rather than concrete trigger phrases, fitting the anchor where 'when' could be more explicit.	4 / 5
Trigger Term Quality	The only natural trigger is the product name "SmartRoutes" plus the generic phrase "interact with SmartRoutes data"; common user variations like routes, stops, deliveries, or scheduling are absent, matching the anchor with some relevant keywords but missing synonyms.	3 / 5
Distinctiveness Conflict Risk	"SmartRoutes integration" targets a clearly named SaaS niche with distinct triggers and minimal overlap with other skills, matching the anchor for a clear niche with minimal conflict risk.	5 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: membranedev/application-skills
Path: skills/smartroutes/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.