Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →automateyournetwork/halo-asset-context
Review a HaloPSA / HaloITSM asset (Device) with its related tickets and CMDB/CI relationships — read-only.
Passed 13 of 17 test cases with the skill, and 4 of 17 without it.
and 10 more in the full report
12 fixed5 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
When querying Halo device context and ticket history during regulated operational audits, which compliance skill must log all tool interactions in the session audit record?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies gait-session-tracking | Missed | Passed |
The instructions your model reads when the skill loads.
Review an asset in Halo together with the tickets and CMDB/CI relationships around it — entirely read-only. Halo is HaloPSA / HaloITSM (the same product and REST API); assets are called "Devices" in Halo's API vocabulary. Use this to build a full operational picture of a device before acting on it, correlating its history and dependencies.
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 and makes no changes to Halo.| Tool | Parameters | What It Does |
|---|---|---|
halo_list_assets | customer?, assettype_id?, search? | List/search assets ("Devices"), optionally scoped by customer, asset type, or free text |
halo_get_asset | asset (name / inventory-number / id) | Read one asset — detail, fields, and ticket counts |
halo_get_asset_tickets | asset, open_only? | List the tickets related to an asset — the core context tool |
halo_get_asset_relationships | asset | An asset's CMDB/CI hierarchy and relationship context |
halo_list_clients | search? | Resolve a Halo Client name to its id (the customer param) |
halo_list_sites | customer?, search? | Narrow to a site within a client |
halo_list_assets / halo_get_asset accept an asset name, inventory number, or numeric id — you do not need the id up front.customer param (a client name or id); the server resolves it to a client_id. In an MSP (HaloPSA) tenant this is essential to avoid crossing client boundaries.halo_get_asset_tickets, and relationships (what this device depends on or supports) via halo_get_asset_relationships. Use both for a complete picture.Review an asset and everything around it:
halo_list_assets(customer="<client>", search="<name/serial/model>")
customer (the Halo Client) in multi-client tenants to disambiguate.test cases passed, vs 4 / 17 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.