What problem does it solve? Answering support tickets well requires reading the full ticket history, checking the codebase or database for facts, and writing a reply that matches the requester's technical level — all without accidentally posting a public response before a human reviews it. This Skill automates that investigation and drafting workflow while keeping everything read-only. ## Core Features & Use Cases - Ticket Analysis: Loads the ticket with all comments and attachments, identifies the unanswered question, the requester's profile, and open gaps before drafting. - Grounded Drafting: Gathers codebase, database, and documentation context so every technical claim in the reply traces to a file:line citation or query result, with unverifiable claims flagged as [NEEDS-REVIEW]. - Private Note Posting: Posts the draft plus an internal supporting-context section as a single private note on the ticket, never as a public reply. - Use Case: A customer asks on a ticket why their export job fails. The Skill reads the ticket, inspects the relevant code and live database state, drafts a plain-language explanation, and posts it as a private note for a support engineer to review and send. ## Quick Start Draft a reply for the ticket at this URL and post it as a private note for my review.
