git:20260529.4c73f52 to git:20260606.348f874

---

name: halopsa

description: "Use when the user asks to triage their HaloPSA queue, audit SLA breaches, build a per-client situational-awareness card, reconcile contract hours, check agent workload, or run any cross-client analytic question against HaloPSA, HaloITSM, or HaloCRM. Wraps the full HaloPSA REST API plus a local SQLite mirror so cross-entity queries the live API can't return in one shot are fast and offline. Trigger phrases: `triage my Halo queue`, `check SLA breaches in HaloPSA`, `who's overloaded in Halo`, `client card for Acme`, `Halo contract burn-down`, `what changed in Halo since this morning`, `HaloPSA + ChatGPT`, `HaloPSA + Claude`, `use halopsa`, `run halopsa`."

author: "Damien Stevens"

license: "Apache-2.0"

vendor: "HaloPSA"

argument-hint: "<command> [args] | install cli|mcp"

allowed-tools: "Read Bash"

metadata:

openclaw:

requires:

bins:

- halopsa-cli

---

# HaloPSA Claude Code Skill

## Prerequisites: Install the CLI

This skill drives the `halopsa-cli` binary. **You must verify the CLI is installed before invoking any command from this skill.** If it is missing, install it first:

1. macOS / Linux:

```bash

bash <(curl -fsSL https://raw.githubusercontent.com/servosity/msp-skills/main/skills/halopsa/install.sh)

```

2. Windows (PowerShell):

```powershell

iwr -useb https://raw.githubusercontent.com/servosity/msp-skills/main/skills/halopsa/install.ps1 | iex

```

3. Verify: `halopsa-cli --version`

4. Ensure `~/.local/bin` (macOS / Linux) or `%LOCALAPPDATA%\Programs\msp-skills` (Windows) is on `$PATH`.

If `--version` reports "command not found" after install, the install step did not put the binary on `$PATH`. Do not proceed with skill commands until verification succeeds.

Wraps the full Halo REST API (952 endpoints across tickets, clients, assets, contracts, time, KB, and workflows) with offline-first search, agent-native JSON output, and cross-entity commands like `triage`, `client card`, and `contracts burn` that join tables Halo's UI scatters across five tabs.

## When to Use This CLI

Reach for halopsa-cli when an agent needs to triage, dispatch, or report against a HaloPSA / HaloITSM / HaloCRM tenant without clicking through the web UI. It is the right tool for cross-entity questions ("who's overloaded", "which tickets are about to breach", "which client is burning their contract"), bulk operations (stale-ticket close, batch action posts, batch time entries), and ETLs that previously required hand-rolled scripts. It is NOT the right tool for end-user portal browsing or for tenants you don't have API credentials to.