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.
git clone --depth 1 https://github.com/jdrhyne/agent-skills /tmp/zendesk && cp -r /tmp/zendesk/skills/zendesk ~/.claude/skills/zendeskSKILL.md
# 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.
Automatically 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.
Check for new OpenClaw releases and notify once per new version.
OpenClaw documentation expert with decision tree navigation, search scripts, doc fetching, version tracking, and config snippets for all OpenClaw features
Bulk 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.
Three-Layer Memory System — automatic fact extraction, entity-based knowledge graph, and weekly synthesis. Manages life/areas/ entities with atomic facts and living summaries.
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Claude ('No, that's wrong...', 'Actually...'), (3) User requests a capability that doesn't exist, (4) An external API or tool fails, (5) Claude realizes its knowledge is outdated or incorrect, (6) A better approach is discovered for a recurring task. Also review learnings before major tasks.
Sync skills between local installation and the GitHub source-of-truth repository. Use when asked to install, update, list, or push skills.
Persistent TODO scratch pad for tracking tasks across sessions. Use when user says "add to TODO", "what's on the TODO", "mark X done", "show TODO list", "remove from TODO", or asks about pending tasks. Also triggers on heartbeat to remind about stale items.