/deploy-software
Stage and reconcile an ImmyBot desired-state software deployment to a tenant or computer
$ npx -y skills add wyre-technology/msp-claude-plugins --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/deploy-software
Context preview
What this command does when you run it.
Stage and reconcile an ImmyBot desired-state software deployment to a tenant or computer
Command definition
deploy-software.mddescription: Stage and reconcile an ImmyBot desired-state software deployment to a tenant or computer
argument-hint: "<software> <scope>"
arguments: [software, scope]
ImmyBot Deploy Software
Stage a desired-state deployment of "$ARGUMENTS.software" to "$ARGUMENTS.scope" and reconcile it through a maintenance session.
Arguments
- `software` (required) — Software name or keyword to deploy
- `scope` (required) — Target tenant name or computer name/hostname
Prerequisites
- ImmyBot MCP server connected with valid `IMMYBOT_INSTANCE_SUBDOMAIN`,
`IMMYBOT_TENANT_ID`, `IMMYBOT_CLIENT_ID`, `IMMYBOT_CLIENT_SECRET`
- Maintenance sessions are destructive — this command requires
explicit human approval before reconciling
Instructions
1. **Resolve the software** — `immybot_software_search` for the keyword, `immybot_software_get` for detail, and `immybot_software_latest_version` for the version. Confirm the canonical package. 2. **Resolve the scope** — If the scope looks like a tenant, use `immybot_tenants_search` then `immybot_tenants_computers` and report the computer count. If it looks like a computer, use `immybot_computers_search`. 3. **Check for conflicts** — `immybot_deployments_for_software` to spot existing deployments that could fight the new one. 4. **Stage desired state** — `immybot_deployments_create` with the software, version, and scope. Confirm nothing has executed yet. 5. **Reconcile (destructive)** — Present the software, version, and blast radius, and obtain approval. With approval, call `immybot_maintenance_sessions_start`. 6. **Monitor** — Poll `immybot_maintenance_sessions_get` and tail `immybot_maintenance_sessions_logs` until terminal. 7. **Confirm** — `immybot_deployments_compliance` for the result.
Example
/deploy-software "7-Zip" "Acme Corp"
Related Commands
- `/search-software` — confirm the package before deploying
- `/maintenance-status` — monitor the reconciling session
Read more
description: Stage and reconcile an ImmyBot desired-state software deployment to a tenant or computer argument-hint: "<software> <scope>" arguments: [software, scope]
ImmyBot Deploy Software
Stage a desired-state deployment of "$ARGUMENTS.software" to "$ARGUMENTS.scope" and reconcile it through a maintenance session.
Arguments
- `software` (required) — Software name or keyword to deploy
- `scope` (required) — Target tenant name or computer name/hostname
Prerequisites
- ImmyBot MCP server connected with valid `IMMYBOT_INSTANCE_SUBDOMAIN`,
`IMMYBOT_TENANT_ID`, `IMMYBOT_CLIENT_ID`, `IMMYBOT_CLIENT_SECRET`
- Maintenance sessions are destructive — this command requires
explicit human approval before reconciling
Instructions
1. **Resolve the software** — `immybot_software_search` for the keyword, `immybot_software_get` for detail, and `immybot_software_latest_version` for the version. Confirm the canonical package. 2. **Resolve the scope** — If the scope looks like a tenant, use `immybot_tenants_search` then `immybot_tenants_computers` and report the computer count. If it looks like a computer, use `immybot_computers_search`. 3. **Check for conflicts** — `immybot_deployments_for_software` to spot existing deployments that could fight the new one. 4. **Stage desired state** — `immybot_deployments_create` with the software, version, and scope. Confirm nothing has executed yet. 5. **Reconcile (destructive)** — Present the software, version, and blast radius, and obtain approval. With approval, call `immybot_maintenance_sessions_start`. 6. **Monitor** — Poll `immybot_maintenance_sessions_get` and tail `immybot_maintenance_sessions_logs` until terminal. 7. **Confirm** — `immybot_deployments_compliance` for the result.
Example
/deploy-software "7-Zip" "Acme Corp"
Related Commands
- `/search-software` — confirm the package before deploying
- `/maintenance-status` — monitor the reconciling session
One command to supercharge Claude Code for MSP workflows. Then restart Claude Code. That's it. Documentation: mcp.wyre.ai
Repo: wyre-technology/msp-claude-plugins
Other commands on msp-claude-plugins.
- /case-review
Review and triage abuse mailbox cases in Abnormal Security
Open command - /search-threats
Search for specific threat patterns in Abnormal Security by sender, recipient, attack type, or keywords
Open command - /threat-triage
Triage recent email threats detected by Abnormal Security by severity and attack type
Open command - /list-overdue-invoices
List open and overdue Alternative Payments invoices and optionally generate hosted payment links for them
Open command - /reconcile-payout
Reconcile an Alternative Payments payout by listing its transactions and matching them against invoices and customers
Open command - /eol-report
EOL/EOS risk report — devices, OS versions, and firmware approaching or past end-of-life/end-of-support, prioritized by criticality
Open command

