Name: dispatch
Rating: 63.2 (1 reviews)
Author: membranedev

dispatch

Dispatch integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Dispatch data.

Quality

75%

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

Quality

Content

82%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 real, complete CLI commands and a state-driven connection workflow, supported by clear section structure. Its weaknesses are a broken step cross-reference, minor over-explanation, and a large inlined action table that would benefit from being split out.

Suggestions

Fix the broken workflow references: add an explicit 'Step 2' anchor (or relabel 'skip to Step 2') and renumber '#### 1b' so the connection sequence is navigable.

Trim the opening platform-description paragraph and the 'Agent Types' aside to concepts Claude cannot infer, improving conciseness.

Move the 20-row 'Popular actions' table into a references/popular-actions.md and link to it, leaving the top-level overview leaner and improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is largely lean command-driven prose, but the opening paragraph ('Dispatch is a platform for managing and automating field service operations... HVAC, plumbing, or electrical services') and the chatty 'Agent Types' line over-explain context Claude can infer, fitting anchor 4 ('Efficient; minor instances of over-explanation') rather than the fully-lean anchor 5.	4 / 5
Actionability	Concrete, copy-paste-ready `membrane` CLI commands appear throughout (install, login, connection ensure, connection get --wait, action list/run, request proxy) with flags and `--json` shown, and the popular-actions table gives real keys — matching anchor 5 ('Fully executable; copy-paste ready... covers the common cases').	5 / 5
Workflow Clarity	The connection flow has explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll feedback loop, but the cross-references are broken — it says 'skip to Step 2' with no Step 2 and introduces '#### 1b' with no 1a, leaving a navigation gap that fits anchor 4 ('clear sequence with most checkpoints; minor gaps') below the airtight anchor 5.	4 / 5
Progressive Disclosure	As a self-contained skill with no bundle files, it uses clear section headers and well-organized structure, but the 20-row 'Popular actions' table is inlined content that could live in a separate reference, and the sparse 'Dispatch Overview' tree is unclear — anchor 4 ('Good structure... minor organization gaps') rather than the reference-signaled anchor 5.	4 / 5
	Total	17 / 20 Passed

Description

67%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 niche and third-person voice, but its trigger language is thin and generic. It names several entities yet leans on one verb and an 'and more' hedge.

Suggestions

Replace the generic 'interact with Dispatch data' trigger with concrete natural phrases users would say, e.g. 'Use when the user wants to create delivery orders, track drivers and vehicles, or manage invoices in Dispatch'.

Expand the single verb 'Manage' into 2-3 concrete actions (e.g. 'create and cancel orders, assign drivers to vehicles, list invoices and manifests') to lift specificity toward 5.

Reconcile the entity list with the actual skill surface — the description cites Persons/Deals/Leads/Projects while the body covers Orders, Vehicles, Drivers, Deliveries, Invoices, and Manifests.

Dimension	Reasoning	Score
Specificity	Quotes 'Manage Persons, Organizations, Deals, Leads, Projects, Activities and more' — names the domain plus several concrete entities to act on, matching anchor 4 ('Lists several specific actions; minor gaps'), with the single verb 'Manage' and the 'and more' hedge being the gaps that keep it off 5.	4 / 5
Completeness	It states both what ('Dispatch integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more') and when ('Use when the user wants to interact with Dispatch data') explicitly, fitting anchor 4; it stays below 5 because the 'when' clause is generic and not enriched with concrete trigger phrases.	4 / 5
Trigger Term Quality	The only trigger phrase is 'Use when the user wants to interact with Dispatch data' — it has the core term 'Dispatch data' but lacks natural synonyms or task words a user would say (e.g. 'field service', 'deliveries', 'orders'), matching anchor 3 ('Some relevant keywords but missing common variations or synonyms') rather than 4's fuller coverage.	3 / 5
Distinctiveness Conflict Risk	Scoped to a named niche ('Dispatch integration' / 'Dispatch data') with distinct triggers, but the generic CRM-style entity list ('Persons, Organizations, Deals, Leads') carries minor overlap risk with other CRM/sales skills, placing it at anchor 4 rather than the conflict-free anchor 5.	4 / 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/dispatch/SKILL.md
Commit: f484c82

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