Name: navigatr
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

navigatr

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

Quality

61%

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

Quality

Content

61%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 highly actionable with concrete Membrane CLI commands and a well-sequenced connection flow including state-based feedback loops. Its main gaps are padded prose, lack of result verification after destructive proxy/action calls, and minor section redundancy.

Suggestions

Add a validation/verification step after action runs and proxy requests (e.g., re-fetch the affected record or check the response status) to lift workflow clarity past the destructive-operations cap.

Trim motivational prose ("so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection") to improve token efficiency.

De-duplicate the "Searching for actions" and "Popular actions" sections, and provide one fully worked concrete example (real connection id, a named action) instead of placeholder-only commands.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands, but includes several padded prose bits ("so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection") that could be trimmed, fitting "mostly efficient but some unnecessary explanation" rather than the minor-instances bar at 4.	3 / 5
Actionability	Concrete, copy-paste-ready CLI commands with real flags dominate (install, login, connection ensure/get, action list/run, request with a full flags table), but examples rely on placeholders (CONNECTION_ID, QUERY, <actionId>) rather than a fully worked concrete case, matching anchor 4 rather than the cover-common-cases bar at 5.	4 / 5
Workflow Clarity	The connection flow is well sequenced with state checkpoints and a re-poll feedback loop, but the proxy supports destructive methods (DELETE, PUT) and action runs modify data with no validation/verification step, so the destructive-operations cap holds at 3.	3 / 5
Progressive Disclosure	Content is well organized into clear sections with no bundle files to reference, but there is redundancy between "Searching for actions" and "Popular actions" (both show action list) and minor organization gaps, fitting anchor 4 rather than the cleanly-split bar at 5.	4 / 5
	Total	14 / 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 answers both what and when with a clear product-specific trigger, but its capability language is generic ("manage data, records, automate workflows") rather than concrete. It is distinct thanks to the Navigatr product name yet could sharpen its action list and trigger phrasing.

Suggestions

Replace generic verbs with concrete Navigatr actions (e.g., "plan and optimize delivery routes, manage driver assignments, track shipments") instead of "Manage data, records, and automate workflows".

Expand the trigger clause with natural user phrasings and synonyms, e.g., "Use when the user wants to plan routes, optimize deliveries, or interact with Navigatr data."

Add file-format or object-level triggers (route plans, stops, driver schedules) to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	It names the domain (Navigatr) and a few action categories ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete, fitting "names domain and 1-2 actions but not comprehensive" rather than the several-specific-actions bar at 4.	3 / 5
Completeness	Both "what" (Navigatr integration; manage data/records; automate workflows) and an explicit "when" ("Use when the user wants to interact with Navigatr data") are present, but the "when" could be more specific, matching anchor 4 rather than the concrete-trigger-phrase bar at 5.	4 / 5
Trigger Term Quality	Relevant keywords appear ("Navigatr", "data", "records", "interact with Navigatr data") but coverage lacks common variations or synonyms, landing at "some relevant keywords but missing variations" rather than the good-coverage bar at 4.	3 / 5
Distinctiveness Conflict Risk	The product name "Navigatr" creates a clear niche with a distinct trigger, but the generic action language ("Manage data, records") carries minor overlap risk with other data-management skills, fitting "mostly distinct; minor overlap risk" rather than the minimal-conflict bar at 5.	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/navigatr/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.