🧪 Community ✓ Claude Code ✓ Claude Desktop Standalone • Ops-pack
Ops Pack
MSP Operations — cross-vendor service-desk board health, dispatch prioritization, SLA monitoring, and shift handoffs across whatever PSA/RMM you have connected.
Installation
Install this plugin individually:
/plugin marketplace add wyre-technology/msp-claude-plugins --plugin ops-pack Or install all MSP plugins at once:
/plugin marketplace add wyre-technology/msp-claude-plugins Features
- Board Hygiene
- Dispatch Prioritization
- Sla Escalation Playbooks
Skills
This plugin provides 3 skills that teach Claude about Ops Pack:
| Skill | Description |
|---|---|
board-hygiene | Board-wide ticket maintenance, distinct from working any single ticket: stale-ticket detection with per-status staleness thresholds, the Waiting-on-Client rot case and its three valid resolutions, duplicate/related-ticket detection signals and safe linking, and technician queue-balance assessment weighted by more than raw ticket count. |
dispatch-prioritization | Priority scoring and assignment for an unassigned PSA ticket queue: the scoring factors (SLA proximity, client tier, ticket age, technician load, skill/category match), how to combine them into an explainable ranked order rather than a black-box formula, and the tool-discovery pattern for finding which PSA and RMM connectors are actually live before calling any vendor's tools. |
sla-escalation-playbooks | A cross-PSA escalation framework for SLA pressure: how each PSA family (Autotask, HaloPSA, ConnectWise Manage, Syncro, Kaseya BMS) models SLA/priority state and where breach risk lives in each, a normalized breach-risk state model (healthy, at risk, breached-response, breached-resolution) with the default escalation action per state, how notification audience shifts by contract tier, and the evidence to gather before paging anyone. |
Agents
This plugin provides 3 agents for autonomous task execution:
| Agent | Description |
|---|---|
board-health-auditor | Use this agent when a service manager, dispatcher, or team lead needs a full cross-board health read on the connected PSA — unassigned aging, SLA-at-risk count, technician load balance, stale/stuck tickets, and duplicate clusters, rolled into a single scored report. |
dispatch-coordinator | Use this agent when the unassigned ticket queue needs to be triaged and assigned to technicians, factoring in SLA pressure, client tier, ticket age, and current technician load. |
stale-ticket-chaser | Use this agent when tickets have gone quiet and someone needs to figure out why and what to do about each one — not just that they're stale. |
Commands
Available slash commands:
| Command | Description |
|---|---|
/eod-handoff | Generate an end-of-day handoff summary - open high-priority tickets, items awaiting next-shift action, and overnight on-call context if available |
/morning-huddle | Daily kickoff report - SLA-at-risk count, unassigned queue size, yesterday's closed vs. opened, and any overnight escalations |
/sla-breaches | List tickets currently breaching or about to breach SLA within a time window, sorted by urgency |
API Reference
| Base URL | |
| Authentication | |
| Rate Limit | |
| Documentation |
Example Usage
Generate an end-of-day handoff summary - open high-priority tickets, items awaiting next-shift action, and overnight on-call context if available
/eod-handoffDaily kickoff report - SLA-at-risk count, unassigned queue size, yesterday's closed vs. opened, and any overnight escalations
/morning-huddleList tickets currently breaching or about to breach SLA within a time window, sorted by urgency
/sla-breachesUsing Skills
/skill ops-pack:board-hygiene
Board-wide ticket maintenance, distinct from working any single ticket: stale-ticket detection with per-status staleness thresholds, the Waiting-on-Client rot case and its three valid resolutions, duplicate/related-ticket detection signals and safe linking, and technician queue-balance assessment weighted by more than raw ticket count.