Fähigkeiten zendesk-automation
🎫

zendesk-automation

Sicher ⚙️ Externe Befehle🌐 Netzwerkzugriff

Automate Zendesk Support Workflows

Eliminate repetitive Zendesk tasks by automating ticket management, user lookup, and organization updates through natural language commands. Streamline your support workflow without leaving your development environment.

Unterstützt: Claude Codex Code(CC)
🥉 75 Bronze
1

Die Skill-ZIP herunterladen

2

In Claude hochladen

Gehe zu Einstellungen → Fähigkeiten → Skills → Skill hochladen

3

Einschalten und loslegen

Teste es

Verwendung von "zendesk-automation". Show me all open tickets assigned to Sarah sorted by priority

Erwartetes Ergebnis:

Found 12 open tickets assigned to Sarah:

1. [HIGH] Ticket #4521 - API integration failing
Status: open | Created: 2 hours ago

2. [NORMAL] Ticket #4518 - Password reset not working
Status: open | Created: 5 hours ago

3. [NORMAL] Ticket #4515 - Billing question
Status: open | Created: 1 day ago

Showing 3 of 12 results. Would you like to see more?

Verwendung von "zendesk-automation". Create a new ticket for urgent server outage

Erwartetes Ergebnis:

Created new ticket successfully:

Ticket ID: #4530
Subject: Urgent server outage
Priority: urgent
Status: new
Requester: current_user@example.com

Next steps: Assign to an agent or update with details.

Sicherheitsaudit

Sicher
v1 • 2/25/2026

All 158 static analysis detections are false positives from Markdown documentation. The backtick-enclosed tool names (e.g., ZENDESK_LIST_ZENDESK_TICKETS) were incorrectly flagged as Ruby/shell commands and weak cryptography. This skill contains only instructional documentation with no executable code. The single hardcoded URL is the legitimate Rube MCP server endpoint required for setup.

1
Gescannte Dateien
221
Analysierte Zeilen
3
befunde
1
Gesamtzahl Audits
Probleme mit niedrigem Risiko (1)
SKILL.md:22
External MCP Dependency
Skill requires connecting to external Rube MCP service at https://rube.app/mcp. This is a documented third-party dependency, not a security vulnerability. Users should review Rube's privacy and security policies before connecting.

Risikofaktoren

⚙️ Externe Befehle (3)
SKILL.md:17 SKILL.md:37 SKILL.md:58
🌐 Netzwerkzugriff (1)
SKILL.md:22
Auditiert von: claude

Qualitätsbewertung

38
Architektur
100
Wartbarkeit
87
Inhalt
50
Community
100
Sicherheit
100
Spezifikationskonformität

Was du bauen kannst

Support Triage Automation

Quickly search, filter, and categorize incoming tickets by priority, status, or assignee to optimize agent workflows.

Bulk Ticket Management

Create multiple tickets, update statuses, or add internal notes across tickets without using the Zendesk interface.

User and Organization Administration

Look up user details, create new accounts, and manage organization associations directly from development tools.

Probiere diese Prompts

List Recent High-Priority Tickets 
List all high-priority tickets from the last 7 days, sorted by newest first. Show me the subject, status, and requester for each.
Create Ticket with Assignment 
Create a new Zendesk ticket with subject 'Login issue for customer account', priority 'high', and assign it to user John Doe (john@example.com). Set the status to 'open'.
Add Internal Note to Ticket 
Add an internal note to ticket #12345 with the text 'Customer confirmed they are using Chrome browser on Windows 11. Awaiting screenshots.'
Update Multiple Ticket Tags 
For ticket #67890, add the tags 'billing' and 'refund-request' while preserving existing tags. Update the status to 'pending'.

Bewährte Verfahren

  • Always call RUBE_SEARCH_TOOLS first to get the current tool schemas, as they may change
  • Use ZENDESK_SEARCH_ZENDESK_USERS to find user IDs before assigning tickets to agents
  • Set public=false when adding internal notes that should only be visible to support agents
  • Fetch current tags before updating to avoid losing existing tags

Vermeiden

  • Do not delete tickets unless absolutely necessary, as deletion is permanent and irreversible
  • Do not update closed tickets; create a follow-up ticket instead
  • Do not skip the connection verification step, as inactive connections will cause all operations to fail
  • Do not assume ticket IDs are sequential; always use the IDs returned by API responses

Häufig gestellte Fragen

Do I need a Zendesk API key?
No API key is required. This skill uses the Rube MCP service which handles OAuth authentication with Zendesk. You only need to authenticate through the Rube connection management flow.
Can I work with tickets in bulk?
Yes, you can list up to 100 tickets per page and iterate through pages. However, each create/update/delete operation must be done individually. Be mindful of the 400 requests per minute rate limit.
What happens when I update ticket tags?
Tag updates replace all existing tags on the ticket. To preserve existing tags, first fetch the current ticket details, merge the new tags with the existing ones, then update with the complete tag list.
Can I reopen closed tickets?
No, closed tickets cannot be modified. If you need to continue working on a closed issue, create a follow-up ticket that references the original closed ticket number.
What is the difference between public replies and internal notes?
Public replies (public=true) are sent to the customer via email and visible in the ticket thread. Internal notes (public=false) are only visible to agents and used for internal collaboration.
Why does the skill require Rube MCP?
Rube MCP provides the integration layer with Composio's Zendesk toolkit. This service handles authentication, rate limiting, and provides a unified interface for Zendesk API operations.

Entwicklerdetails

Autor

sickn33

Lizenz

MIT

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/zendesk-automation

Ref

main

Dateistruktur

📄 SKILL.md