CtrlK
BlogDocsLog inGet started
Tessl Logo

Zendesk

Manage Zendesk tickets, users, and support workflows through the Zendesk API. Use when searching tickets, updating support state, checking users, or exporting queue data.

68

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

79%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, actionable API reference skill with excellent conciseness and fully executable examples. The main weaknesses are the lack of error handling/validation guidance for API operations and the monolithic structure that could benefit from splitting detailed reference content into separate files.

Suggestions

Add a brief error handling section showing how to check for common failures (401 auth errors, rate limit responses, empty results) and how to recover

Consider moving the Endpoints Reference table and Search Query Syntax to a separate REFERENCE.md file, keeping SKILL.md focused on the most common operations

DimensionReasoningScore

Conciseness

The skill is lean and efficient, providing only necessary information. No explanations of what Zendesk is or how APIs work—it jumps straight to actionable content with minimal prose.

3 / 3

Actionability

Every operation includes complete, copy-paste ready curl commands with jq processing. Examples cover the full range of common operations with specific, executable code.

3 / 3

Workflow Clarity

The setup and authentication flow is clear, but there are no validation checkpoints or error handling guidance. For API operations that could fail (rate limits, auth errors), there's no feedback loop or verification steps.

2 / 3

Progressive Disclosure

Content is well-organized with clear sections and a reference table, but the file is quite long (~150 lines of examples). Some content like the full endpoints reference or search syntax could be split into separate reference files.

2 / 3

Total

10

/

12

Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-crafted skill description that clearly identifies its purpose and when to use it. The explicit 'Use when' clause with natural trigger terms makes it easy for Claude to select appropriately. The only weakness is that the capability list could be more comprehensive (e.g., does it also create/update tickets?).

Suggestions

Consider expanding the action list to include other operations if supported (e.g., 'create tickets', 'update ticket status', 'add comments') to improve specificity

DimensionReasoningScore

Specificity

Names the domain (Zendesk Support API) and lists some actions (searching tickets, organizations, users), but doesn't comprehensively describe all capabilities like creating, updating, or managing tickets.

2 / 3

Completeness

Clearly answers both what (Zendesk Support API for searching tickets, organizations, users) and when (working with support tickets, customer issues, or correlating with Salesforce) with explicit 'Use when' clause.

3 / 3

Trigger Term Quality

Includes natural keywords users would say: 'support tickets', 'customer issues', 'Zendesk', 'organizations', 'users', and the cross-reference to 'Salesforce accounts' adds useful context for correlation tasks.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with clear niche - specifically Zendesk Support API with explicit mention of Salesforce correlation, making it unlikely to conflict with generic support or CRM skills.

3 / 3

Total

11

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata' field is not a dictionary

Warning

license_field

'license' field is missing

Warning

body_output_format

No obvious output/return/format terms detected; consider specifying expected outputs

Warning

Total

13

/

16

Passed

Repository
jdrhyne/agent-skills
Reviewed

Table of Contents

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.