Name: mojo-helpdesk
Rating: 60 (1 reviews)
Author: membranedev

mojo-helpdesk

Mojo Helpdesk integration. Manage Tickets, Users, Organizations, Reports. Use when the user wants to interact with Mojo Helpdesk data.

Quality

70%

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

Quality

Content

67%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 a solid, executable guide to the Membrane CLI integration with strong command examples and a well-validated connection workflow. It loses points for some unnecessary explanatory padding and minor structural inconsistencies in the workflow numbering.

Suggestions

Trim the introductory paragraph and motivational asides (e.g. 'so you can focus on the integration logic rather than auth plumbing') since Claude does not need Mojo Helpdesk explained.

Fix the workflow numbering: replace the dangling 'Step 2' reference and '1b' with a consistent numbered sequence so the connection flow is unambiguous.

Make the 'Popular actions' section actually list common Mojo Helpdesk actions (e.g. list tickets, create ticket, search users) rather than only restating the discovery command.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph explaining what Mojo Helpdesk is and asides like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary padding Claude does not need.	3 / 5
Actionability	It provides concrete, copy-pasteable commands throughout (install, login, connection ensure, action list/run, request) plus a flags table, but the 'Popular actions' section only shows a discovery command and does not enumerate actual popular actions.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state-based validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-after-action feedback loop, but numbering is inconsistent (a dangling 'Step 2' reference and a '1b' with no '1a'/'2').	4 / 5
Progressive Disclosure	The single SKILL.md is well organized with clear section headers and no nested external references, but at ~140 lines with all content inlined (proxy flags, agent types, best practices) some material could be split out for a leaner overview.	4 / 5
	Total	15 / 20 Passed

Description

73%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 well-formed, third-person, and clearly identifies a distinct branded niche with an explicit 'Use when' trigger. Its main weakness is that the action verb ('Manage') is generic and the 'when' clause could name more specific user intents.

Suggestions

Replace the generic verb 'Manage' with more concrete actions, e.g. 'Create, update, and query Tickets, Users, Organizations, and Reports'.

Expand the 'when' clause with concrete user intents, e.g. 'Use when the user wants to create or update support tickets, look up users or organizations, or pull Mojo Helpdesk reports'.

Dimension	Reasoning	Score
Specificity	Names the domain (Mojo Helpdesk) and lists four concrete entities ('Tickets, Users, Organizations, Reports'), but the single verb 'Manage' is generic, so coverage is moderate rather than comprehensive.	3 / 5
Completeness	It explicitly answers both 'what' ('Manage Tickets, Users, Organizations, Reports') and 'when' ('Use when the user wants to interact with Mojo Helpdesk data'), though the 'when' clause is somewhat generic and could be more specific.	4 / 5
Trigger Term Quality	Natural trigger phrases like 'Mojo Helpdesk', 'Tickets', and 'interact with Mojo Helpdesk data' are present and would be said by users; a few synonyms or variations are missing but coverage is good.	4 / 5
Distinctiveness Conflict Risk	It targets a clearly named, branded product (Mojo Helpdesk) with distinct triggers, so overlap with other skills is minimal and conflict risk is low.	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/mojo-helpdesk/SKILL.md
Commit: f484c82

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