Name: dyspatch
Rating: 58.4 (1 reviews)
Author: membranedev

dyspatch

Dyspatch integration. Manage data, records, and automate workflows. Use when the user wants to interact with Dyspatch 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/dyspatch/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 content is highly actionable with executable Membrane CLI commands and a clear connection workflow with validation checkpoints. Its weaknesses are mild verbosity in the intro and best-practices prose, inconsistent step numbering, and a monolithic structure that could offload reference material to bundle files.

Suggestions

Trim the introductory background paragraph and the promotional framing in 'Best practices' to keep the focus on actionable commands.

Fix the step numbering by labeling explicit Step 1 (connect) and Step 2 (search/run actions) sections, and add an explicit verification step after running an action (e.g. check the `output` field for errors).

Move the entity overview list and the request-flags table into a separate reference file (e.g. references/ACTIONS.md) and link to it from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands but includes unnecessary background ('Dyspatch is an email template management platform that allows marketing teams...') and mildly promotional prose ('burn less tokens and make communication more secure'), matching the 'mostly efficient but some unnecessary explanation' anchor; it is not 4 because the padding is noticeable rather than minor.	3 / 5
Actionability	It provides copy-paste-ready CLI commands throughout (install, login, connection ensure, action list/run, request) plus a flags table covering common cases, matching the 'fully executable; copy-paste ready commands' anchor.	5 / 5
Workflow Clarity	There is a clear install→authenticate→connect→poll→search→run sequence with an explicit state-polling validation checkpoint and handling of CLIENT_ACTION_REQUIRED and CONFIGURATION_ERROR states, matching the 'clear sequence with most checkpoints present' anchor; it is not 5 because step numbering is inconsistent ('skip to Step 2' with no labeled Step 1/2, and a '1b' heading) and action results lack an explicit verification step.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear sections with no nested references, matching 'good structure; most content appropriately placed'; it is not 5 because at ~165 lines it exceeds the simple-skill threshold and some reference-style material (entity overview, flags table) is inlined rather than split into separate files.	4 / 5
	Total	16 / 20 Passed

Description

61%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 correctly pairs a Use-when trigger with a named platform, giving it strong distinctiveness and adequate completeness. Its main weakness is vague, non-concrete action verbs and limited trigger-term coverage beyond the brand name.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Dyspatch actions such as 'create and localize email templates, manage draft/template versions, and send transactional emails'.

Expand trigger terms beyond the brand name to include natural phrases users say, e.g. 'email templates', 'template localization', or 'Dyspatch drafts'.

Make the 'when' clause more specific, e.g. 'Use when the user wants to create, edit, localize, or send Dyspatch email templates.'

Dimension	Reasoning	Score
Specificity	The description names the Dyspatch domain but relies on generic verbs like 'Manage data, records, and automate workflows' rather than concrete actions, matching the 'names domain but actions minimal/generic' anchor; it does not reach 3 because no specific concrete operations are listed.	2 / 5
Completeness	It states both a 'what' ('Dyspatch integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with Dyspatch data.'), but the trigger clause is generic and could be more specific, matching the 'has both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	It includes the natural proper-noun keyword 'Dyspatch' (repeated) plus generic terms like 'data' and 'records', but misses common synonyms a user might say such as 'email templates', 'localization', or file extensions, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Dyspatch' is a unique named platform giving the skill a clear niche with distinct triggers and minimal conflict risk, matching the 'clear niche with distinct triggers' anchor.	5 / 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/dyspatch/SKILL.md
Commit: f484c82

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