Name: zendesk
Rating: 56.8 (1 reviews)
Author: membranedev

zendesk

Zendesk integration. Manage customer success and ticketing data, records, and workflows. Use when the user wants to interact with Zendesk data.

Quality

65%

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

Quality

Content

61%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 action-oriented with executable Membrane CLI commands and a solid connection-setup workflow including state checkpoints, but it opens with redundant background and lacks validation guidance around destructive operations. Splitting the action catalog into a reference file would improve progressive disclosure.

Suggestions

Remove or condense the introductory paragraph explaining what Zendesk is and who uses it — Claude already knows this.

Add an explicit validation/verification checkpoint before destructive actions (e.g. confirm ticket ID and warn the user before running delete-ticket).

Consider moving the 'Popular actions' catalog into a separate reference file and keeping a short pointer in SKILL.md.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command examples and tables, but the opening paragraph explains what Zendesk is and who uses it — background Claude already knows — and could be trimmed.	3 / 5
Actionability	Provides concrete, copy-paste-ready CLI commands for install, login, connection, action search/run, and proxying, with only minor gaps (placeholders like CONNECTION_ID and a generic --input example rather than a fully worked call).	4 / 5
Workflow Clarity	The connect→search→run sequence has state-based checkpoints (polling for READY, handling CLIENT_ACTION_REQUIRED and CONFIGURATION_ERROR), but destructive actions (delete-ticket, delete-organization) appear with no validation/verification step, capping this dimension at 3.	3 / 5
Progressive Disclosure	Well-organized with clear section headers and no nested external references (no bundle files exist); the large inline 'Popular actions' table is the one chunk that could arguably live in a separate reference file.	4 / 5
	Total	14 / 20 Passed

Description

70%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 includes an explicit 'Use when' trigger with a well-defined Zendesk niche, but it leans on the generic verb 'Manage' instead of enumerating concrete ticketing/customer-success actions. Tightening the 'what' with specific operations would lift specificity and completeness.

Suggestions

Replace the generic 'Manage ... data, records, and workflows' with concrete actions, e.g. 'Create and update tickets, list users and organizations, search Zendesk records'.

Add common synonyms such as 'support tickets' or 'help desk' to broaden natural trigger coverage.

Make the 'what' more specific to push completeness from a clear what+when toward fully concrete trigger phrases.

Dimension	Reasoning	Score
Specificity	Names the domain ('customer success and ticketing') and enumerates objects ('data, records, and workflows') but relies on a single generic verb ('Manage') rather than listing multiple concrete actions like create/update/list tickets, so coverage is not comprehensive.	3 / 5
Completeness	Explicitly answers both what ('Manage customer success and ticketing data, records, and workflows') and when ('Use when the user wants to interact with Zendesk data'), though the 'what' could be more specific about concrete operations.	4 / 5
Trigger Term Quality	Includes natural terms users would say — 'Zendesk', 'customer success', 'ticketing', 'data' — but omits common synonyms such as 'support tickets' or 'help desk'.	4 / 5
Distinctiveness Conflict Risk	The Zendesk niche is clearly distinct with low conflict risk, but the generic 'data, records, and workflows' phrasing leaves minor overlap with adjacent CRM/support skills.	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/zendesk/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.