Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →automateyournetwork/halo-ticket-context
Review a HaloPSA / HaloITSM ticket for resolution context — its detail, action/note history, linked assets, and related KB runbooks — read-only.
Passed 11 of 16 test cases with the skill, and 3 of 16 without it.
and 9 more in the full report
11 fixed4 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
After searching the Halo KB for 'firewall rule change' and getting back article ID 314, what is the exact function call to pull the complete text body of that runbook?
| Checked | Without skill | With skill |
|---|---|---|
| calls halo_get_kb_article with article parameter set to 314 | Missed | Passed |
The instructions your model reads when the skill loads.
Review a ticket in Halo to gather everything needed to understand and resolve it — the ticket detail, its full action/note history, the assets it touches, and related knowledge-base runbooks. Entirely read-only. Halo is HaloPSA / HaloITSM (the same product and REST API); tickets are called "Faults" in Halo's API vocabulary.
halo-mcp (NetClaw-authored, mcp-servers/halo-mcp/)python3 -u mcp-servers/halo-mcp/halo_mcp_server.py (stdio transport)HALO_CLIENT_ID / HALO_CLIENT_SECRET against HALO_BASE_URLfastmcp, httpx, python-dotenvhalo_create_change_request, in the halo-change-request skill). Every tool in this skill is read-only.| Tool | Parameters | What It Does |
|---|---|---|
halo_get_ticket | ticket (numeric id) | Read one ticket ("Fault") — summary, details, status, priority, client/site/user, and linked assets |
halo_get_ticket_actions | ticket (numeric id) | The ticket's actions/notes history (the investigation timeline) |
halo_list_tickets | ticket_type?, customer?, asset_id?, status?, open_only?, search? | Find a ticket by type, customer, asset, status, or free text |
halo_get_asset | asset (name / inventory-number / id) | Read a linked asset surfaced on the ticket |
halo_list_kb_articles | search? | Search the Halo knowledge base for related runbooks |
halo_get_kb_article | article (numeric id) | Read one KB article, including its body |
halo_list_tickets (by customer, asset_id, status, or search) first.customer param (a client name or id).halo_get_ticket_actions returns the note/action timeline — the richest source of what has already been tried and what remains.halo_get_ticket returns linked assets; read them with halo_get_asset (or pivot to the halo-asset-context skill).halo_list_kb_articles, then read the full body with halo_get_kb_article for resolution/runbook context.Assemble resolution context for a ticket:
halo_list_tickets(customer="<client>", search="<keywords>", open_only=true)
test cases passed, vs 3 / 16 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.