Name: detrack
Rating: 62.4 (1 reviews)
Author: membranedev

detrack

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

Quality

73%

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

Quality

Content

76%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 highly actionable with concrete, copy-paste commands and a clear connection-state feedback loop, organized into clean sections. Its weaknesses are mild over-explanation in the intro and a lack of validation checkpoints for destructive operations, plus an undefined 'Step 2' reference.

Suggestions

Add a validation/confirmation checkpoint before destructive actions (e.g. 'Confirm the D.O. with the user before running delete-job') to lift workflow clarity above the destructive-op cap.

Define the referenced 'Step 2' explicitly or remove the dangling cross-reference so the connection workflow is unambiguous.

Trim the opening descriptive paragraph about what DeTrack is, since Claude and the user already know the product when invoking this skill.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and tables, but the opening paragraph ("DeTrack is a delivery management software...") and the Agent Types note explain context Claude largely already knows, fitting 'efficient; minor instances of over-explanation that could be trimmed'.	4 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run with --input, request with flags) plus a popular-actions table, fully covering the common cases per the top anchor.	5 / 5
Workflow Clarity	The connection setup has a real feedback loop (poll BUILDING -> handle CLIENT_ACTION_REQUIRED -> poll again), but 'Step 2' is referenced without being defined and destructive operations (delete-job, update-job) lack validation checkpoints; the destructive-op cap holds this at 3.	3 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is organized into clear, navigable sections (Overview, Auth, Connecting, Searching, Popular actions, Proxy, Best practices); the inlined action and proxy-flag tables could be separate references, but inline placement is reasonable for a CLI skill.	4 / 5
	Total	16 / 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.

The description is clear and distinct, naming a specific product and several managed entities with an explicit use-when clause. Its main weakness is trigger-term richness: it relies on a single generic trigger rather than concrete, varied trigger phrases.

Suggestions

Add concrete trigger phrases users would naturally say, e.g. 'Use when the user mentions DeTrack jobs, deliveries, vehicles, drivers, or fleet tracking.'

Replace the generic verb 'Manage' with more specific operations (e.g. 'Create, list, update, and delete jobs, vehicles, and contacts') to lift specificity.

Include common synonyms/file or field references (e.g. D.O. numbers, delivery orders) to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Users, Goals, Filters" names the domain and lists several specific actions, fitting the 'several specific actions; minor gaps' anchor; it stops short of 5 because the single verb 'Manage' is generic rather than fully comprehensive.	4 / 5
Completeness	It has both a clear "what" (DeTrack integration; manage Organizations, Users, Goals, Filters) and an explicit "when" ("Use when the user wants to interact with DeTrack data"), but the trigger is generic, so it does not reach 5's requirement for concrete multi-trigger phrases.	4 / 5
Trigger Term Quality	The only natural trigger term is "DeTrack" / "DeTrack data", matching 'some relevant keywords but missing common variations or synonyms'; it is not 4 because there are no additional natural phrases or synonyms beyond the product name.	3 / 5
Distinctiveness Conflict Risk	"DeTrack" is a specific named product with a distinct trigger ("interact with DeTrack data"), giving it 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/detrack/SKILL.md
Commit: f484c82

Reviewed: ~16 hours 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.