CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

zendesk-automation

Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/zendesk-automation/SKILL.md

The canonical home for this skill is zendesk-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 highly actionable — exact tool slugs, parameter enums, and a quick-reference table — and well organized as a single file. Its weaknesses are repeated pitfall content and a vacuous closing section that waste tokens, and the absence of validation/confirmation steps around the destructive, irreversible delete workflow, which caps workflow clarity.

Suggestions

Add an explicit validation step before destructive deletion, e.g., 'Before DELETE: fetch the ticket via GET_BY_ID, state the subject/status to the user, and confirm — deletion is permanent'.

Deduplicate pitfalls: state tag-replacement, safe_update, and deletion behavior once (in Known Pitfalls) and reference it from the workflows instead of repeating each 2–3 times.

Remove or replace the empty "When to Use" section ("This skill is applicable to execute the workflow or actions described in the overview.") with concrete trigger conditions or delete it entirely.

DimensionReasoningScore

Conciseness

The body is dense with API facts Claude would not know (Composio tool slugs, pagination semantics, tag-replacement behavior), but the same pitfalls are repeated three times: tag replacement appears in workflows 2 and 5 and again in "Known Pitfalls"; irreversibility of DELETE appears in workflow 2 and twice more in Known Pitfalls; safe_update is explained twice. The closing "When to Use" section ("This skill is applicable to execute the workflow or actions described in the overview.") is pure padding. This matches "Mostly efficient but includes some unnecessary explanation or could be tightened"; it is not a 4 because the duplication and filler section are more than minor.

3 / 5

Actionability

Guidance is fully executable for an MCP-orchestration skill: exact tool slugs with sequencing and [Required]/[Optional]/[Prerequisite] markers (e.g., "ZENDESK_SEARCH_ZENDESK_USERS - Find requester/assignee [Prerequisite]"), concrete parameters with enumerated values (priority: 'urgent', 'high', 'normal', 'low'), and a copy-paste-ready Quick Reference table covering all 14 tasks. Deferring exact schemas to RUBE_SEARCH_TOOLS is explicitly justified, leaving no gaps for the common cases.

5 / 5

Workflow Clarity

Sequences are well-ordered with some checkpoints (connection verified ACTIVE before workflows; GET_BY_ID as a prerequisite before replying), but the skill includes destructive operations without validation steps: permanent, irreversible ticket deletion is listed in workflow 2 with no checkpoint (no fetch-before-delete or user confirmation), and batch pagination iteration has no verification guidance. Per the rubric guideline, missing validation in destructive/batch workflows caps workflow clarity at 3 — this cap takes precedence even though the sequencing itself is 4-level.

3 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so everything is inline in a ~210-line SKILL.md. Structure is good: per-workflow sections with consistent Tool sequence / Key parameters / Pitfalls layout, a Common Patterns section, and a Quick Reference table for navigation. This matches "Good structure; most content is appropriately placed; minor organization gaps"; it is not a 5 because the per-endpoint parameter detail (roughly an API reference) could be split into a one-level-deep reference file, and not a 3 because the single file is still lean and easy to navigate at this size.

4 / 5

Total

15

/

20

Passed

Description

65%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 names a distinct niche (Zendesk automation via Rube MCP/Composio) with decent natural keywords, but it relies on object nouns rather than concrete action verbs and entirely lacks a 'Use when...' trigger clause, capping completeness. It sits solidly in the middle of the scale.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to manage, reply to, or search Zendesk support tickets, or mentions Zendesk.'

Replace generic "Automate Zendesk tasks" with concrete actions: 'Create, update, and reply to tickets; search users; manage organizations'.

Add common trigger synonyms such as 'support tickets', 'helpdesk', 'assign tickets', and 'ticket comments' for better keyword coverage.

DimensionReasoningScore

Specificity

"Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies" names the domain and its object types, but the only concrete action verbs are the generic "Automate" and "replies" — operations like create, update, search, or delete are not stated. This matches the anchor "Names domain and 1-2 concrete actions, but not comprehensive"; a 4 would require several specific actions (e.g., "create and update tickets, search users"), which the object-noun list does not provide.

3 / 5

Completeness

The "what" is clear (Zendesk automation over tickets, users, organizations, replies via Rube MCP), but there is no "Use when..." clause or equivalent explicit trigger guidance — only the procedural "Always search tools first for current schemas". Per the rubric guideline, a missing 'Use when...' clause caps completeness at 3; a 4 would require an explicit, even if brief, when-phrase.

3 / 5

Trigger Term Quality

Strong natural keywords users would say: "Zendesk", "tickets", "users", "organizations", "replies". A few common variations are missing ("support tickets", "helpdesk", "comments", "assign a ticket", "assignees"), matching "Good keyword coverage; a few natural terms missing" rather than the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

"Zendesk" is a clear niche trigger, and the "via Rube MCP (Composio)" qualifier distinguishes it from a native Zendesk API or other integration skills, so conflict risk with other skills is minimal. It clearly matches "Clear niche with distinct triggers; minimal conflict risk"; a 4 would imply meaningful overlap with a closely related skill, which is not the case.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/zendesk-automation/SKILL.md

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.