Zendesk

$npx mdskill add jdrhyne/agent-skills/Zendesk

Search Zendesk tickets to avoid duplicates and streamline support

  • Identify existing tickets before creating new ones to prevent duplication.
  • Deploys Zendesk API for ticket search operations.
  • Analyzes ticket data to determine if a new ticket is necessary or not.
  • Returns relevant results in JSON format for quick review by the user.

SKILL.md

.github/skills/ZendeskView on GitHub ↗
---
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.

More from jdrhyne/agent-skills

SkillDescription
auto-updaterAutomatically update OpenClaw and selected skills once daily. Runs via cron, checks for updates, applies them, and messages the user with a summary of what changed.
autoresearch-loopDomain-agnostic metric-driven improvement loop, generalizing Karpathy's autoresearch. Use when you want an agent to discover what to measure for a project/goal, then run a keep-or-revert experiment loop that proposes changes, measures them against an objective, keeps wins, discards regressions, and records implemented improvements. Adapts to code perf-auditing, codegen, bug-finding, ad optimization, or any artifact + measurable objective + trial. Trigger: 'autoresearch this', 'find and implement improvements to X', 'discover metrics and optimize'.
clawdbot-release-checkCheck for new OpenClaw releases and notify once per new version.
clawddocsOpenClaw documentation expert with decision tree navigation, search scripts, doc fetching, version tracking, and config snippets for all OpenClaw features
command-creatorThis skill should be used when creating a Claude Code slash command. Use when users ask to "create a command", "make a slash command", "add a command", or want to document a workflow as a reusable command. Essential for creating optimized, agent-executable slash commands with proper structure and best practices.
context-recoveryAutomatically recover working context after session compaction or when continuation is implied but context is missing. Works across Discord, Slack, Telegram, Signal, and other supported channels.
design-auditPremium UI/UX design auditor with Jobs/Ive philosophy. Use when reviewing, evaluating, or elevating existing UI — triggers on "audit my design", "review UI", "make it feel premium", "design review", "UX audit", "elevate the design", "Jobs/Ive style", or when asked to improve visual quality of an existing interface without changing functionality.
elegant-reportsGenerate beautifully designed PDF reports with a Nordic/Scandinavian aesthetic. Use when creating polished executive briefings, analysis reports, or presentation-style PDF outputs from markdown and HTML via Nutrient DWS.
ga4Query Google Analytics 4 (GA4) data via the Analytics Data API. Use when you need to pull website analytics like top pages, traffic sources, user counts, sessions, conversions, or any GA4 metrics/dimensions. Supports custom date ranges and filtering.
gallery-scraperBulk download images from login-protected gallery websites using an attached browser session. Use when asked to scrape, download, or save images from authenticated gallery pages, extract full-size images from thumbnails, or batch download from multi-page galleries.