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

Blog Docs Log in Get started

optimoroute

OptimoRoute integration. Manage Organizations. Use when the user wants to interact with OptimoRoute data.

Quality

68%

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/optimoroute/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 an efficient, actionable CLI reference with a strong connection-state workflow and clear navigation. The main gaps are missing validation checkpoints around action execution and proxy calls, plus a couple of lightly padded sections.

Suggestions

Add a validation/verification step after running actions or proxy requests (e.g., check the output/error field and retry guidance) to satisfy the destructive/batch feedback-loop expectation.

Trim the orienting intro paragraph and the thin Overview bullet list ("Use action names and parameters as needed") to tighten conciseness.

Flesh out the Popular actions section with a concrete example or remove the redirect duplication with the Searching for actions section.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with direct executable CLI commands and a useful flag table; minor over-explanation (the orienting intro paragraph and the thin Overview bullet list) could be trimmed.	4 / 5
Actionability	Provides concrete, copy-paste-ready membrane commands (login, connection ensure, action list/run, request proxy) with real flags; minor gaps like the redirect-only Popular actions section and unexplained CONNECTION_ID resolution keep it just below 5.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a polling feedback loop, but the action-running and proxy paths lack validation checkpoints for batch/destructive calls.	4 / 5
Progressive Disclosure	A single well-organized file with clear section headers and no nested references; good structure overall, though some inline material (flag table, state machine) is longer than the simple-skill threshold that would warrant a 5.	4 / 5
	Total	16 / 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 covers both what and when with a clear named niche, but is thin on concrete capabilities and natural trigger synonyms. Expanding the action list and trigger keywords would lift specificity and trigger-term quality.

Suggestions

Replace the single "Manage Organizations" action with several concrete capabilities (e.g., manage Orders, Drivers, Vehicles, Planning, Realtime Tracking) to raise specificity.

Add natural trigger keywords users actually say — routes, route optimization, scheduling, delivery dispatch, field-service routing — alongside "OptimoRoute".

Make the when-clause more concrete, e.g., "Use when the user wants to manage OptimoRoute orders, drivers, vehicles, or schedules."

Dimension	Reasoning	Score
Specificity	Names the OptimoRoute domain and one concrete action ("Manage Organizations"), matching the anchor for 1-2 concrete actions without being comprehensive.	3 / 5
Completeness	Explicitly states both what ("OptimoRoute integration. Manage Organizations.") and when ("Use when the user wants to interact with OptimoRoute data"), though the when-clause is somewhat generic.	4 / 5
Trigger Term Quality	Includes the explicit trigger phrase and the "OptimoRoute" keyword, but misses common natural variations a user might say (routes, scheduling, deliveries, orders).	3 / 5
Distinctiveness Conflict Risk	OptimoRoute is a named niche product, making the skill mostly distinct with only minor overlap risk; not a 5 because the trigger phrasing is not comprehensive enough to be fully niche-distinct.	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/optimoroute/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.