What problem does it solve? Infrastructure work done without a ticket is invisible to audits, handoffs, and post-incident reconstruction. This Skill ensures every real change to servers, cloud resources, networks, or databases gets a ticket and running work notes in Zoho ServiceDesk Plus Cloud or Jira Cloud, captured while the details are still fresh. ## Core Features & Use Cases - Ticket lifecycle management: Verify existing tickets, search for duplicates, create new tickets with inferred titles and descriptions, add timestamped work notes, update status and category, and close tickets with closure comments. - Dual transport with automatic fallback: Prefers the ServiceDesk Plus MCP connector (which attributes writes to the signed-in user) and falls back to the bundled ticketctl.py CLI, which is also the only path to Jira and email notifications. - Secret scrubbing and failure recovery: Automatically redacts credentials, tokens, and keys from note text before writing, and queues failed writes locally for later retry so no record is lost. - Use Case: While diagnosing why DC02 is refusing LDAP binds, the assistant asks once whether you have a ticket, opens one titled "DC02 - LDAP binds failing after July patch cycle", logs each finding as an internal note, and closes the ticket with a verification summary when the fix is confirmed. ## Quick Start Ask the assistant to open a ticket for the server work you are about to do and log progress notes to it as you go.
