Skip to content
Agent Orchestration
Skill

/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.

BOOST
From plugin
jdrhyne-agent-skills
24018 skills
Install
$ npx -y skills add jdrhyne/agent-skills --skill zendesk --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/zendesk

Context preview

The summary Claude sees to decide when to auto-load this skill.

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

SKILL.md

zendesk.SKILL.md
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.
Read more
Ships withjdrhyne-agent-skills

A collection of AI agent skills and prompts for OpenClaw (formerly Clawdbot), Claude Code, Codex, and other LLM-based coding assistants. 🤝 Contributions Welcome! Have a skill that makes your AI agent smarter? We'd love to include it.

Get the whole plugin

Other skills on jdrhyne-agent-skills.