Name: vision-helpdesk
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

vision-helpdesk

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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/vision-helpdesk/SKILL.md

Quality

Content

56%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 skill delivers strong, executable CLI guidance with a well-sequenced connection workflow, but it is dragged down by a massive padded bullet list of generic verbs that inflates token cost without adding value. Progressive disclosure is weak because that reference list is inlined rather than split out.

Suggestions

Remove or collapse the 107-line bullet list of generic verbs (Add/Edit/Delete/etc.) — Claude already knows these CRUD operations; instead show how to discover real actions via `membrane action list --intent`.

Move any genuine entity/action reference into a separate `references/` file and link to it from a short overview, keeping SKILL.md as a lean entry point.

Add an explicit validation/verification checkpoint after destructive actions (e.g. confirm a ticket was closed or a record deleted) to strengthen feedback loops.

Dimension	Reasoning	Score
Conciseness	A ~107-line bullet list of generic CRUD verbs (Add, Edit, Delete, List, Get, Send, with duplicates such as Report, Group, Import, Export) restates concepts Claude already knows and is heavily padded, though the CLI sections themselves are reasonably efficient.	2 / 5
Actionability	Concrete, copy-paste-ready commands appear throughout (npm install, membrane login, connection ensure, action run, request) plus a proxy flags table, with only minor gaps such as placeholder IDs the agent must first discover.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (poll until not BUILDING, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and error handling, with only minor validation gaps.	4 / 5
Progressive Disclosure	Section headers provide structure, but with no bundle files present the 258-line body inlines a 107-line entity/action reference list that clearly belongs in a separate file or should be omitted, so organization could be improved.	3 / 5
	Total	13 / 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 specific product niche and includes an explicit 'Use when' trigger, but its capability list leans on generic verbs ('Manage data, records') rather than concrete actions. Trigger-term coverage is adequate but lacks synonyms or variations.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete capability phrases such as 'create and update tickets, manage customers and agents, run reports and SLAs'.

Expand the 'Use when' clause with natural trigger phrases a user would say, e.g. 'when the user mentions Vision Helpdesk tickets, customer support requests, or helpdesk workflows'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Vision Helpdesk') and a couple of actions ('Manage data, records, and automate workflows'), but 'Manage data, records' is generic rather than a comprehensive list of concrete capabilities.	3 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Vision Helpdesk data') are present, though the trigger phrasing could be more specific.	4 / 5
Trigger Term Quality	The product name 'Vision Helpdesk' is a strong natural trigger and appears repeatedly, but the supporting terms ('data', 'records', 'workflows') are generic and no synonyms or variations are offered.	3 / 5
Distinctiveness Conflict Risk	'Vision Helpdesk' is a named product niche with a distinct trigger, giving it minimal overlap risk with other skills.	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/vision-helpdesk/SKILL.md
Commit: f484c82

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