Name: logistia-route-planner
Rating: 58.4 (1 reviews)
Author: membranedev

logistia-route-planner

Logistia Route Planner integration. Manage Routes, Vehicles, Drivers, Depots, OptimizationProfiles. Use when the user wants to interact with Logistia Route Planner 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/logistia-route-planner/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 an actionable, well-structured guide built around concrete CLI commands and a clearly explained connection state machine, with only minor verbosity and a lack of verification steps for destructive data operations.

Suggestions

Add a verification step after running data-mutating actions (e.g., re-query the resource or check the response `state`/`error` field before reporting success) to satisfy the destructive-operation workflow cap.

Trim the opening paragraph about what a route-planning SaaS is and who uses it, since it explains concepts not needed to operate the CLI.

Show one fully-substituted end-to-end example (a concrete connectionId, actionId, and intent) so the placeholders are unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands plus genuinely non-obvious state-machine detail (BUILDING/READY/CLIENT_ACTION_REQUIRED); the only trimmable padding is the opening sentence describing what a route-planning SaaS is and who uses it.	4 / 5
Actionability	It provides concrete, copy-pasteable commands for the full flow (install, login, connection ensure, action list/run, request proxy) with a flags table, but common placeholders like CONNECTION_ID, actionId, and QUERY still require substitution.	4 / 5
Workflow Clarity	The connection sequence is well-ordered with polling and state-based branching checkpoints, but the skill manages Routes/Vehicles/Drivers (potentially destructive CRUD) and the "running actions" step has no verify/validate feedback loop, so the destructive-operation cap holds at 3.	3 / 5
Progressive Disclosure	The single file is well-organized into clear sections (Overview, Install, Authentication, Connecting, Searching, Actions, Proxy, Best practices) with no monolithic wall of text and no content that clearly belongs in a separate reference file.	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 clearly identifies a distinct named application and gives an explicit use-when clause, but its action vocabulary is limited to a single generic verb ("Manage") and its trigger terms lack synonyms users would naturally say.

Suggestions

Replace or supplement the generic "Manage" with specific verbs the skill supports (e.g., "Create, update, and delete Routes; assign Vehicles and Drivers; apply OptimizationProfiles").

Add natural trigger synonyms to the "Use when" clause, such as delivery routes, route optimization, vehicle routing, or dispatch planning.

Make the "when" clause enumerate concrete user intents (e.g., "Use when the user wants to plan or optimize delivery routes, assign drivers/vehicles, or manage depots in Logistia").

Dimension	Reasoning	Score
Specificity	It names the domain and five concrete resource types ("Routes, Vehicles, Drivers, Depots, OptimizationProfiles"), but the only action verb is the generic "Manage", so it does not list multiple distinct concrete actions as the 4- and 5-anchors require.	3 / 5
Completeness	Both "what" (manage Routes, Vehicles, Drivers, Depots, OptimizationProfiles) and "when" ("Use when the user wants to interact with Logistia Route Planner data") are present, but the "when" clause is generic rather than enumerating concrete trigger phrases.	4 / 5
Trigger Term Quality	The trigger relies on the app name ("Use when the user wants to interact with Logistia Route Planner data"), which is a relevant natural term, but it omits common synonyms a user might say such as "delivery routes", "route optimization", or "vehicle routing".	3 / 5
Distinctiveness Conflict Risk	The named vertical SaaS "Logistia Route Planner" carves a clear niche with a distinct trigger unlikely to fire for unrelated skills, matching the minimal-conflict anchor.	5 / 5
	Total	15 / 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/logistia-route-planner/SKILL.md
Commit: f484c82

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