Name: route4me
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

route4me

Route4Me integration. Manage Users, Addresses, Routes, Territories, Geofences, Contacts. Use when the user wants to interact with Route4Me data.

Quality

63%

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

Quality

Content

56%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 Membrane CLI workflow guidance is concrete and well-sequenced with real state-machine handling, but the skill is dragged down by a large, mostly-irrelevant keyword list that bloats the file and adds no navigable structure or progressive disclosure.

Suggestions

Remove or relocate the ~180-item action list (lines 21-200); most entries (Donate, Invest, Podcast, Webinar, Weather) are unrelated to Route4Me and exist only as keyword padding.

Move any retained action discovery guidance into a separate reference file and link to it from the body so the overview stays lean and one level deep.

Resolve the undefined "Step 2" reference and fix the 1b numbering so the connection workflow reads as a single coherent sequence with explicit validation checkpoints.

Dimension	Reasoning	Score
Conciseness	Lines 21-200 are a ~180-item keyword list ("Donate", "Invest", "Trade", "Podcast", "Webinar", "Ebook", "Whitepaper", "Weather", "Traffic") mostly unrelated to route optimization, which is noticeable padding that wastes the context budget; the CLI sections themselves are reasonably tight.	2 / 5
Actionability	Provides concrete, copy-paste-ready commands for the core workflow ("npm install -g @membranehq/cli@latest", "membrane connection ensure", "membrane action run", "membrane request") with a thorough proxy flag table; minor gaps remain since run examples use placeholders rather than a fully populated end-to-end example.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state handling (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-then-retry feedback loop; minor gaps exist such as the undefined "Step 2" reference and slightly broken 1b numbering.	4 / 5
Progressive Disclosure	Sections are organized with headers, but no bundle files exist and the large inline action/resource list is content that should either be split into a separate reference or removed; structure is present but not well organized for discovery.	3 / 5
	Total	13 / 20 Passed

Description

71%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.

A focused, third-person description that names the product and concrete resources and includes an explicit "Use when" trigger. It is distinct and reasonably specific, but the trigger phrasing is generic and could enumerate real-world scenarios for stronger completeness.

Suggestions

Expand the "Use when" clause with concrete trigger phrases (e.g., planning delivery routes, optimizing stops, managing territories/geofences) instead of the generic "interact with Route4Me data".

Vary the single "Manage" verb to reflect distinct actions per resource (e.g., optimize routes, manage addresses, configure geofences) for more specific capability coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete resource types ("Manage Users, Addresses, Routes, Territories, Geofences, Contacts") but relies on a single generic verb ("Manage"), leaving minor coverage gaps relative to the comprehensive anchor.	4 / 5
Completeness	It answers both "what" (manage the listed resources) and "when" ("Use when the user wants to interact with Route4Me data"), but the "when" is broad and could be more explicit with concrete trigger scenarios.	4 / 5
Trigger Term Quality	Relevant keywords appear ("Route4Me", the resource names) and there is a "Use when" clause, but the trigger phrase is generic ("interact with Route4Me data") and misses common natural variations or synonyms users would say.	3 / 5
Distinctiveness Conflict Risk	"Route4Me" is a named, specific platform with distinct triggers, so it occupies a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	16 / 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/route4me/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.