What problem does it solve?
Raising a change request in HaloPSA/HaloITSM is error-prone because a change request is not a fixed object type — it is a per-organization ticket type whose id and custom fields vary, and orgs often define several change types (customer, internal, emergency). This Skill discovers the correct type, confirms it with a human, and gates the single write behind explicit approval so no unreviewed change ticket is ever submitted.
Core Features & Use Cases
- Ticket Type Discovery & Caching: Lists creatable request types, asks the operator to confirm the right change type per category, and caches the confirmed catalog per tenant in Memory MCP.
- Schema Learning: Reads the authoritative field schema via halo_get_ticket_type and inspects a real populated ticket to learn how fields are actually filled.
- Gated Single Write: halo_create_change_request previews the exact /api/Tickets POST body with submit=false and only writes after explicit per-change operator approval.
- Use Case: An engineer needs to file a customer-facing network change in Halo. The Skill recalls the cached customer change type, previews the full ticket payload, waits for approval, submits, and logs the decision and ticket id to the GAIT audit trail.
Quick Start
Ask the agent to open a change request in Halo for a planned network change and let it discover the ticket type, preview the ticket, and wait for your approval before submitting.