halo-asset-context

Review HaloPSA assets with related tickets and CMDB relationships via read-only API queries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Investigating a device in HaloPSA/HaloITSM requires manually correlating asset records, ticket history, and CMDB relationships across multiple screens. This Skill gathers that full operational context in one read-only workflow before anyone acts on the device.

Core Features & Use Cases

  • Asset Discovery and Detail: Search assets ("Devices") by name, inventory number, or id, scoped by Halo Client to respect MSP tenant boundaries.
  • Ticket History Correlation: Pull all tickets related to an asset, or filter to open-only, to spot recurring faults and active issues.
  • CMDB/CI Relationship Mapping: Read an asset's dependency hierarchy to understand upstream and downstream impact before a change.
  • Use Case: Before decommissioning a switch, an engineer reviews its Halo asset record, finds three open tickets and a downstream server dependency, then hands off to the halo-change-request skill instead of making an unplanned change.

Quick Start

Ask the agent to review the Halo asset for a given device name, including its open tickets and CI relationships, scoped to the appropriate client.

Frequently Asked Questions about halo-asset-context

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

FAQPage Schema
How do I look up an asset in HaloPSA by name?

Use halo_list_assets with a search string, optionally scoped by customer, then halo_get_asset with the asset's name, inventory number, or numeric id. You do not need to resolve the numeric id first; the server accepts any of the three identifiers.

How to see all tickets related to a device in HaloITSM?

Call halo_get_asset_tickets with the asset identifier to list its full ticket history, or pass open_only=true to see only active issues. This is the core context tool for spotting recurring faults and recent changes on a device.

Does this skill work with both HaloPSA and HaloITSM?

Yes. HaloPSA and HaloITSM are the same product with the same REST API, so every tool behaves identically for both editions. Assets are called Devices in Halo's API vocabulary regardless of edition.

Can this skill create or modify tickets in Halo?

No. Every tool in this skill is read-only and makes no changes to Halo. The only write operation in the halo-mcp server is halo_create_change_request, which lives in the separate halo-change-request skill.

What credentials does the Halo MCP server need?

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

Why scope Halo asset queries by customer in an MSP tenant?

The Halo Client represents the customer organization, and passing it via the customer param keeps queries inside client boundaries. In multi-client HaloPSA tenants this prevents accidentally reading or correlating assets across different customers.