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.