halo-ticket-context

Review HaloPSA tickets with action history, linked assets, and KB runbooks.

650|182|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/automateyournetwork/netclaw --skill halo-ticket-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: halo-ticket-context
Source: https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/halo-ticket-context
Command: npx skills add https://github.com/automateyournetwork/netclaw --skill halo-ticket-context

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires fastmcp, httpx, python-dotenv.

What problem does it solve?

Investigating an ITSM ticket requires manually digging through ticket details, note history, linked assets, and knowledge-base articles across HaloPSA/HaloITSM, which is slow and error-prone. This Skill gathers all resolution context for a Halo ticket in one read-only workflow.

Core Features & Use Cases

  • Ticket Detail & Timeline: Read a ticket's full detail and its complete action/note history to reconstruct what has been diagnosed and tried.
  • Linked Asset & KB Lookup: Inspect assets attached to the ticket and search Halo knowledge-base articles for applicable runbooks.
  • Ticket Discovery: Find ticket IDs by customer, asset, status, or free-text search when only a description is known.
  • Use Case: An engineer is assigned an open fault about a switch outage. The Skill locates the ticket by customer and keyword, reads its note timeline, inspects the linked switch asset, and pulls the relevant KB runbook to recommend the next step.

Quick Start

Use the halo-ticket-context skill to gather full resolution context for Halo ticket 1234, including its note history, linked assets, and related KB runbooks.

Frequently Asked Questions about halo-ticket-context

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

FAQPage Schema
How do I read a HaloPSA ticket's note history?

Use the halo_get_ticket_actions tool with the ticket's numeric ID to retrieve the full action and note timeline. This history shows what has been diagnosed, what was tried, and the current state of the investigation.

How do I find a Halo ticket ID without knowing the number?

Use halo_list_tickets with filters like customer, asset_id, status, or free-text search to locate the ticket. Halo tickets are addressed by numeric ID only and are not name-resolvable, so this lookup step is required first.

Does this skill work with both HaloPSA and HaloITSM?

Yes, HaloPSA and HaloITSM are the same product with the same REST API, so all tools behave identically for both editions. Tickets are called Faults in Halo's API vocabulary.

Can this skill modify or close Halo tickets?

No, every tool in this skill is strictly read-only. The only write operation in the halo-mcp server is halo_create_change_request, which belongs to the separate halo-change-request skill with a preview-confirm-submit flow.

What credentials are required to connect to Halo?

You need HALO_BASE_URL, HALO_CLIENT_ID, and HALO_CLIENT_SECRET for OAuth2 client-credentials authentication. Optional variables cover tenant, scope, custom auth URL, TLS verification, timeouts, pagination, and rate limiting.