support

Organize support notes into ticket-specific directories for Zendesk and GitHub workflows.

127|21|Updated Jan 11, 2016

Search Tags:#investigation #GitHub #notes #support #tickets #Zendesk

Ready to run

npx skills add https://github.com/haacked/dotfiles --skill support-haacked

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: support
Source: https://github.com/haacked/dotfiles/tree/main/ai/skills/support
Command: npx skills add https://github.com/haacked/dotfiles --skill support-haacked

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Teams often lose track of past support conversations scattered across Zendesk and GitHub tickets. This leads to duplicated work, slow resolutions, and incomplete historical context.

Core Features & Use Cases

Automated ticket-note organization: Create and maintain a centralized notes.md per ticket.
Deterministic ticket directories: Uses a script to locate or create weekly ticket folders, ensuring consistent storage.
Template-driven logs: Pre-populated investigation-notes.md to standardize documentation.

Quick Start

Use the support command to locate or create a ticket's notes directory and begin an investigation, for example: /support zendesk 40875 or /support github 12345.

Frequently Asked Questions about support

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I organize support investigation notes for Zendesk and GitHub tickets?▼

To organize support investigation notes, this Skill validates the ticket number and uses a deterministic script to locate or create weekly ticket-specific directories, maintaining a centralized notes.md file for each ticket.

What is the best way to keep track of past support ticket investigations across weeks?▼

Keeping track of past support investigations is handled by applying deterministic directory paths that group tickets by week, preventing scattered notes and preserving historical context for Zendesk and GitHub workflows.

How do I start a new investigation log for a specific ticket?▼

To start a new investigation log, issue the support command with the ticket platform and number, such as /support zendesk 40875, to validate the input and generate a template-driven notes structure.

Does the support notes automation pre-populate investigation templates?▼

Yes, the support notes automation pre-populates an investigation-notes.md file using standardized templates, ensuring consistent documentation structure every time a new ticket directory is created.

Can I use this ticket notes workflow for both GitHub and Zendesk platforms?▼

Yes, you can use this ticket notes workflow for both GitHub and Zendesk platforms by specifying the source during invocation, which validates the ticket type and applies the appropriate directory structure.