Source profileQuality 92/100
WYRE-AI/msp-claude-plugins/msp-claude-plugins/immybot/immybot/skills/software-deployment/SKILL.md
ImmyBot Software Deployment
ImmyBot's desired-state software deployment model end-to-end: the software catalog, deployment, maintenance-session and computer tool surfaces; the canonical select → scope → assert → reconcile → verify workflow; and the pinned-vs-latest, conflicting-deployment, and reboot edge cases.
- Source repository stars
- 42
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-08-28
- Source checked
- 2026-08-28
Decision brief
What it does: where it fits
This is ImmyBot's headline capability. The model is desired-state: you assert what should be installed, then a maintenance session brings the endpoint into compliance. This skill walks the canonical deployment workflow end-to-end.
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
Source-detected install commandSource
npx skills add https://github.com/WYRE-AI/msp-claude-plugins --skill "msp-claude-plugins/immybot/immybot/skills/software-deployment"Safe inspection promptEditorial
Inspect the Agent Skill "ImmyBot Software Deployment" from https://github.com/WYRE-AI/msp-claude-plugins/blob/5005f73ba2f52cd299f58aa6bb79f4e70ae87103/msp-claude-plugins/immybot/immybot/skills/software-deployment/SKILL.md at commit 5005f73ba2f52cd299f58aa6bb79f4e70ae87103. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
The Canonical Deployment Workflow
Confirm the software exists in the catalog and what version you intend to deploy.
Confirm the software exists in the catalog and what version you intend to deploy.For tenant-wide rollouts:Call immybotdeploymentscreate with the chosen software, version, and scope. The deployment now exists, but nothing has happened on the endpoint yet. - 02
Anti-triggers
Making the install actually happen — creating a deployment changes
Making the install actually happen — creating a deployment changesOS and security patching — ImmyBot deploys applications, notA one-off command on one machine — use - 03
API Tools
Review the “API Tools” section in the pinned source before continuing.
Review and apply the “API Tools” source section. - 04
Discover the catalog
Review the “Discover the catalog” section in the pinned source before continuing.
Review and apply the “Discover the catalog” source section. - 05
Configure desired state
Review the “Configure desired state” section in the pinned source before continuing.
Review and apply the “Configure desired state” source section.
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
EvidenceSourceComputedTestedEditorial
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 92/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 42 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- WYRE-AI/msp-claude-plugins
- Skill path
- msp-claude-plugins/immybot/immybot/skills/software-deployment/SKILL.md
- Commit
- 5005f73ba2f52cd299f58aa6bb79f4e70ae87103
- License
- Apache-2.0
- Collected
- 2026-08-28
- Default branch
- main
View the original SKILL.md
ImmyBot Software Deployment
This is ImmyBot's headline capability. The model is desired-state: you assert what should be installed, then a maintenance session brings the endpoint into compliance. This skill walks the canonical deployment workflow end-to-end.
Anti-triggers
- Making the install actually happen — creating a deployment changes
nothing on any endpoint; the reconciliation run that acts on it is
immybot-maintenance-sessions. - OS and security patching — ImmyBot deploys applications, not
Windows Update. Patch compliance lives in the RMM:
superops-assets,syncro-assets, orncentral-devices. - A one-off command on one machine — use
immybot-script-execution. - Whether a tenant is compliant overall — rollups and scorecards are
immybot-tenant-compliance.
API Tools
Discover the catalog
| Tool | Purpose |
|---|---|
immybot_software_list | Per-tenant software catalog |
immybot_software_list_global | Global ImmyBot software catalog |
immybot_software_search | Search by name |
immybot_software_get | Full detail for one software |
immybot_software_versions | Available versions for a software |
immybot_software_latest_version | The current "latest" version |
immybot_software_categories | Browse by category |
immybot_software_publishers | Browse by publisher |
immybot_software_stats | Usage stats across the fleet |
Configure desired state
| Tool | Purpose |
|---|---|
immybot_deployments_list | Current deployments |
immybot_deployments_get | Detail for a deployment |
immybot_deployments_create | Assert new desired state |
immybot_deployments_for_computer | Deployments scoped to a computer |
immybot_deployments_for_software | Deployments scoped to a software |
immybot_deployments_compliance | Compliance report for a deployment |
immybot_deployments_trigger | Force immediate reconciliation (destructive) |
immybot_software_install | Install a software via desired state (destructive) |
Reconcile
| Tool | Purpose |
|---|---|
immybot_maintenance_sessions_list | Recent sessions |
immybot_maintenance_sessions_get | One session snapshot |
immybot_maintenance_sessions_start | Start a session (destructive) |
immybot_maintenance_sessions_pause | Pause a running session |
immybot_maintenance_sessions_resume | Resume a paused session |
immybot_maintenance_sessions_cancel | Cancel a session |
immybot_maintenance_sessions_logs | Log stream |
immybot_maintenance_sessions_results | Final outcome |
immybot_maintenance_sessions_active | Currently active sessions |
immybot_maintenance_sessions_summary | Summary metrics |
Computers in scope
| Tool | Purpose |
|---|---|
immybot_computers_list | Enrolled computers |
immybot_computers_get | One computer detail |
immybot_computers_search | Search by name |
immybot_computers_inventory | Installed software on a computer |
immybot_computers_deployments | Deployments hitting a computer |
immybot_computers_trigger_checkin | Force a check-in |
The Canonical Deployment Workflow
1. Identify the software
immybot_software_search → immybot_software_get → immybot_software_latest_version
Confirm the software exists in the catalog and what version you intend to deploy.
2. Identify the scope
For tenant-wide rollouts:
immybot_tenants_get → immybot_tenants_computers
For a single computer:
immybot_computers_search → immybot_computers_get
3. Configure desired state
Call immybot_deployments_create with the chosen software, version,
and scope. The deployment now exists, but nothing has happened on
the endpoint yet.
4. Reconcile
Either wait for the next scheduled maintenance window, or trigger immediately:
immybot_maintenance_sessions_start
This is destructive — get human approval first.
5. Watch the session
Poll immybot_maintenance_sessions_get and tail
immybot_maintenance_sessions_logs. Stop polling once the session is
in a terminal state.
6. Confirm compliance
Call immybot_deployments_compliance to see which computers in
scope reached the desired state and which failed.
Other Common Workflows
Per-computer audit
immybot_computers_getfor the computerimmybot_computers_inventoryfor installed softwareimmybot_computers_deploymentsfor what desired-state expects- Reconcile differences
Per-tenant compliance scorecard
immybot_tenants_getimmybot_tenants_compliancefor the rollup- Drill into failing deployments via
immybot_deployments_compliance
Investigate a failed install
- Identify the maintenance session:
immybot_maintenance_sessions_list immybot_maintenance_sessions_resultsfor outcomeimmybot_maintenance_sessions_logsfor the failing log lines- Cross-reference with
immybot_tasks_logsfor lower-level detail
Edge Cases
- Pinned versions vs latest - A deployment can pin a specific version or track latest. Always confirm which mode you are in before changing the desired version.
- Conflicting deployments - Two deployments hitting the same
software on the same scope can fight. Use
immybot_deployments_for_computerto spot conflicts before adding a new one. - Reboot requirements - Some installs require a reboot. Maintenance sessions handle this, but expect the session to span longer than the install itself.
Best Practices
- Prefer tenant-scoped deployments over per-computer deployments for fleet-wide software; reserve per-computer for exceptions.
- Always run a small pilot (one or two computers) before triggering a fleet-wide maintenance session.
- For destructive operations, log the approver, the scope, and the expected outcome.
Related Skills
- api-patterns - Auth and the desired-state model
Frequently asked questions
What to verify before installation and use
What does the ImmyBot Software Deployment source document cover?
This is ImmyBot's headline capability. The model is desired-state: you assert what should be installed, then a maintenance session brings the endpoint into compliance. This skill walks the canonical deployment workflow end-to-end.
How do I install ImmyBot Software Deployment?
The source record exposes this install command: npx skills add https://github.com/WYRE-AI/msp-claude-plugins --skill "msp-claude-plugins/immybot/immybot/skills/software-deployment". Inspect the command and pinned source before running it.
Alternatives
Compare before choosing
Computed 9982
vasilyu1983/AI-Agents-public
qa-testing-ios
Guides iOS testing with XCTest, XCUITest, Swift Testing, simctl, and xcresult. Use when choosing destinations, controlling flakes, or parsing test artifacts for native apps.
Computed 9829,236
garrytan/gbrain
brain-pdf
Generate a publication-quality PDF from any brain page via the gstack make-pdf binary. Strips YAML frontmatter, sanitizes emoji, applies running headers and page numbers. Brain page is always the source of truth; PDF is a rendering.
Computed 983,123
NVIDIA/skills
rtvi-cv-customize-model
How to swap the DeepStream CV detection model in the VSS Alerts Blueprint verification (2d_cv) mode - covers ONNX export, custom bbox parsers, compose mount gotchas, nvinfer config, runtime TRT engine build, deployment, and a segmentation-capable model addendum handoff.
Computed 9882
vasilyu1983/AI-Agents-public
research-git
Scans public GitHub repos for agent skills, dev practices, and code patterns. Use when enriching skills, setting team policy, or researching a build domain.