Zendesk · jdrhyne — Claude Code skill: features and setup
Work with Zendesk tickets and users through the API, or export queue data on request. Configure the required environment variables before connecting.
MIT ★ 239 updated 2026-08-30
npx skills add jdrhyne/agent-skills --skill zendesk -a claude-codeWhat Zendesk does
The skill searches tickets by status, priority, assignee, or subject, then can create or update them. It also looks up users by email and saves queue exports when asked. Searching first helps avoid duplicate tickets.
Set ZENDESK_SUBDOMAIN, ZENDESK_EMAIL, and ZENDESK_TOKEN for access. Requests go to the authenticated Zendesk API, and file exports happen only when requested. The skill favors targeted searches or views over scanning a whole queue.
Closing, merging, deleting, or publicly replying to a ticket requires explicit confirmation. Status or ownership changes get an internal note, and bulk work must respect Zendesk rate limits.
What it helps with
- find tickets by status, priority, or subject
- check for duplicates before creating a ticket
- change ticket status and add an internal explanation
- look up a user by email before editing ticket ownership
- save a requested queue export for analysis
Example prompts for the agent
- Find open high-priority tickets and summarize the current support state.
- Look up this user by email, then change the ticket owner and add an internal note.
- Search for similar requests first, then create a ticket with this description and priority.
How to install Zendesk
1Skills CLI (Vercel)
npx skills add jdrhyne/agent-skills --skill zendesk -a claude-code2Manually: put the files in place
~/.claude/skills/zendesk/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/zendesk/
1Skills CLI (Vercel)
npx skills add jdrhyne/agent-skills --skill zendesk -a codex2Manually: put the files in place
.agents/skills/zendesk/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jdrhyne/agent-skills --skill zendesk -a cursor2Manually: put the files in place
.cursor/skills/zendesk/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jdrhyne/agent-skills skills/zendesk2Manually: put the files in place
.github/skills/zendesk/SKILL.md1Skills CLI (Vercel)
npx skills add jdrhyne/agent-skills --skill zendesk -a gemini-cli2Platform CLI
gemini skills install https://github.com/jdrhyne/agent-skills --path skills/zendeskManually: put the files in place
.devin/skills/zendesk/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about Zendesk
How do I install Zendesk in Claude Code?
Run npx skills add jdrhyne/agent-skills --skill zendesk -a claude-code. The skill file is at ~/.claude/skills/zendesk/SKILL.md.
What does the Zendesk skill do?
It uses the Zendesk API to find and update tickets, look up users, create tickets, and export queue data when requested.
What do I need to connect to Zendesk?
Set ZENDESK_SUBDOMAIN, ZENDESK_EMAIL, and ZENDESK_TOKEN as environment variables. The skill checks access before handling tickets.
Source text
SKILL.md · MIT
---
name: Zendesk
slug: zendesk
version: 1.0.0
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.
changelog: Initial release with ticket management, user lookup, and workflow automation.
metadata: {"clawdbot":{"emoji":"🎫","requires":{"bins":[],"env":["ZENDESK_SUBDOMAIN","ZENDESK_EMAIL","ZENDESK_TOKEN"]},"os":["linux","darwin","win32"]}}
permissions:
- 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_SUBDOMAIN`
- `ZENDESK_EMAIL`
- `ZENDESK_TOKEN`
Build the Zendesk auth context from those variables and confirm access before trying ticket operations.
## Workflow Rules
1. Search before creating a ticket to avoid duplicates.
2. Use views or targeted search instead of listing entire queues.
3. Add internal notes when changing status or ownership.
4. Confirm destructive or customer-visible actions before sending them.
5. 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.
© jdrhyne · MIT · jdrhyne/agent-skills
Similar skills
All skills for Backend and APIs →Zendesk by other authors comes first.