Zendesk
Manage Zendesk tickets, users, and support workflows through the Zendesk API.
How to use it
Claude Code
- Run the line below. It pulls the whole folder into
~/.claude/skills/zendesk. - Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit jdrhyne/agent-skills/skills/zendesk#main ~/.claude/skills/zendeskFor one project only, change the path to .claude/skills/zendesk.
Claude (web or desktop app)
- On this page open ⋯ → Download .md.
- Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
- Pick the file and Save. Claude shows the name and description and runs a security scan.
- Check the skill is switched on.
- Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
- ChatGPT: make a Project and paste it into Instructions.
- Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
- Check which app you pasted it into — the steps above name the right one.
- Some skills need the paid tier of Claude or ChatGPT.
Paste into Claude, ChatGPT or Cursor.
Source of Zendesk
Show the full text57 lines
| name | slug | version | description | changelog | metadata | permissions |
|---|---|---|---|---|---|---|
| Zendesk | zendesk | 1.0.0 | Manage Zendesk tickets, users, and support workflows through the Zendesk API. Use when searching tickets, updating support state, checking users, or exporting queue data. | Initial release with ticket management, user lookup, and workflow automation. | {"clawdbot":{"emoji":"🎫","requires":{"bins":[],"env":["ZENDESK_SUBDOMAIN","ZENDESK_EMAIL","ZENDESK_TOKEN"]},"os":["linux","darwin","win32"]}} | - network: "Calls the authenticated Zendesk API for ticket, user, and search operations. - file_write: "Writes exports only when the user asks for a saved report or dump. |
Zendesk
Manage Zendesk tickets, users, and support workflows through the authenticated Zendesk API.
When to Use
- search tickets or support history
- create or update tickets
- inspect user details
- export queue data for analysis
- summarize current support state
Setup
Use these environment variables:
ZENDESK_SUBDOMAINZENDESK_EMAILZENDESK_TOKEN
Build the Zendesk auth context from those variables and confirm access before trying ticket operations.
Workflow Rules
- Search before creating a ticket to avoid duplicates.
- Use views or targeted search instead of listing entire queues.
- Add internal notes when changing status or ownership.
- Confirm destructive or customer-visible actions before sending them.
- Respect Zendesk rate limits during bulk work.
Common Operations
- Search tickets by status, priority, assignee, or subject before creating a new one.
- Create tickets with a clear subject, customer-visible comment, and correct priority.
- Update status with an internal note that explains what changed and why.
- Look up users by email before editing ownership, organization, or requester fields.
- Export queue data only when the user explicitly asked for a saved report.
Safety Boundaries
- Do not read credentials from ad hoc files, memory stores, or chat history; use only the documented environment variables.
- Do not close, merge, delete, or publicly reply to tickets without explicit confirmation.
- Do not export ticket or user data to files unless the user asked for a saved artifact.
- Do not send Zendesk data to any service other than the authenticated Zendesk API.
| 1 | |
| 2 | name Zendesk |
| 3 | slug zendesk |
| 4 | version 1.0.0 |
| 5 | description Manage Zendesk tickets, users, and support workflows through the Zendesk API. Use when searching tickets, updating support state, checking users, or exporting queue data. |
| 6 | changelog Initial release with ticket management, user lookup, and workflow automation. |
| 7 | metadata {"clawdbot":{"emoji":"🎫","requires":{"bins":[],"env":["ZENDESK_SUBDOMAIN","ZENDESK_EMAIL","ZENDESK_TOKEN"]},"os":["linux","darwin","win32"]}} |
| 8 | permissions |
| 9 | - network: "Calls the authenticated Zendesk API for ticket, user, and search operations." |
| 10 | - file_write: "Writes exports only when the user asks for a saved report or dump." |
| 11 | |
| 12 | |
| 13 | # Zendesk |
| 14 | |
| 15 | Manage Zendesk tickets, users, and support workflows through the authenticated Zendesk API. |
| 16 | |
| 17 | ## When to Use |
| 18 | |
| 19 | search tickets or support history |
| 20 | create or update tickets |
| 21 | inspect user details |
| 22 | export queue data for analysis |
| 23 | summarize current support state |
| 24 | |
| 25 | ## Setup |
| 26 | |
| 27 | Use these environment variables: |
| 28 | |
| 29 | `ZENDESK_SUBDOMAIN` |
| 30 | `ZENDESK_EMAIL` |
| 31 | `ZENDESK_TOKEN` |
| 32 | |
| 33 | Build the Zendesk auth context from those variables and confirm access before trying ticket operations. |
| 34 | |
| 35 | ## Workflow Rules |
| 36 | |
| 37 | Search before creating a ticket to avoid duplicates. |
| 38 | Use views or targeted search instead of listing entire queues. |
| 39 | Add internal notes when changing status or ownership. |
| 40 | Confirm destructive or customer-visible actions before sending them. |
| 41 | Respect Zendesk rate limits during bulk work. |
| 42 | |
| 43 | ## Common Operations |
| 44 | |
| 45 | Search tickets by status, priority, assignee, or subject before creating a new one. |
| 46 | Create tickets with a clear subject, customer-visible comment, and correct priority. |
| 47 | Update status with an internal note that explains what changed and why. |
| 48 | Look up users by email before editing ownership, organization, or requester fields. |
| 49 | Export queue data only when the user explicitly asked for a saved report. |
| 50 | |
| 51 | ## Safety Boundaries |
| 52 | |
| 53 | Do not read credentials from ad hoc files, memory stores, or chat history; use only the documented environment variables. |
| 54 | Do not close, merge, delete, or publicly reply to tickets without explicit confirmation. |
| 55 | Do not export ticket or user data to files unless the user asked for a saved artifact. |
| 56 | Do not send Zendesk data to any service other than the authenticated Zendesk API. |
| 57 |
Discussion
Browse more free Claude skills.