halopsa

Plugin halopsa from marketplace msp-claude-plugins in WYRE-AI/msp-claude-plugins. Commands read from the repo's manifest — yesterday.

Skills (7)

• HaloPSA Agents

  HaloPSA agents (technicians) and teams as a read-only MCP surface: listing technicians, retrieving agent detail, listing team structures, and the inactive-agent filter. Agent IDs resolved here are what ticket assignment needs. When assigning HaloPSA tickets, gauging team capacity, or looking up a te

• HaloPSA API Patterns

  HaloPSA REST API fundamentals: OAuth 2.0 client-credentials authentication, authorization vs. resource server URLs, the tenant query parameter, filtering and pagination conventions, array-wrapped POST bodies, rate-limit behavior, scopes, and error codes. When authenticating to or calling the HaloPSA

• HaloPSA Assets

  HaloPSA asset/CMDB data model: asset (configuration item) fields, device types and statuses, links to clients, sites, users, tickets, and contracts, plus parent-child asset relationships. Covers the Asset API surface, hardware lifecycle workflows, RMM auto-sync and device matching, and validation er

• HaloPSA Clients

  HaloPSA CRM data model: client records and their billing/contact fields, sites (locations), contacts (Users), client classification, and parent-child client hierarchy. Covers the Client/Site/Users API surface, onboarding and deactivation workflows, duplicate prevention, and common validation errors.

• HaloPSA Contracts

  HaloPSA contract management: contract types (recurring, prepaid hours, ad-hoc, project, warranty), statuses, billing and coverage fields, recurring invoice items, prepaid hour balances and deduction, SLA association, renewal and billing-reconciliation workflows. When managing service agreements, rec

• HaloPSA Invoices

  HaloPSA invoices as a read-only MCP surface: listing by client or date range, filtering by payment and send status, retrieving line-item detail on a single invoice, and the reporting and reconciliation workflows built on them. When an MSP finance task needs HaloPSA invoice data — tracking billing, c

• HaloPSA Tickets

  HaloPSA service desk tickets: ticket fields, statuses, priorities and ticket types, actions (notes and time entries), attachments, SLA behaviour, and the creation and status-transition workflows with their validation rules.

Slash commands (10)

• /halopsa:add-action

  Add an action (note, update, or response) to an existing HaloPSA ticket

• /halopsa:contract-status

  Check contract status, service entitlements, and billing information for a client

• /halopsa:create-ticket

  Create a new service ticket in HaloPSA

• /halopsa:kb-search

  Search the HaloPSA knowledge base for articles and solutions

• /halopsa:search-assets

  Search for configuration items/assets by name, serial number, type, or client

• /halopsa:search-clients

  Search for HaloPSA clients by name, domain, or other attributes

• /halopsa:search-tickets

  Search for tickets in HaloPSA by various criteria

• /halopsa:show-ticket

  Display comprehensive ticket information including history, actions, and related entities

• /halopsa:sla-dashboard

  View SLA status across tickets, including approaching breaches and at-risk tickets

• /halopsa:update-ticket

  Update fields on an existing HaloPSA ticket including status, priority, and assignment

Subagents (2)

• service-desk-ops

  Use this agent when an MSP dispatcher, team lead, or service manager needs to triage and manage the HaloPSA ticket queue. Trigger for: ticket triage, SLA monitoring, dispatch suggestions, recurring issues, queue review, halo service desk, halopsa queue. Examples: "Which tickets are closest to breach

• sla-performance-reporter

  Use this agent when an MSP service manager, operations lead, or account manager needs SLA compliance reporting and trend analysis in HaloPSA — not live ticket triage, but retrospective reporting on how well the team has met SLA commitments by client, by technician, and by ticket category. Trigger fo

Similar plugins