Receber por email
← Voltar para o catálogo

ImmyBot Endpoint Management

Use this skill when working with ImmyBot computers/endpoints — listing and filtering the managed fleet, searching by name or serial, inspecting installed-software inventory, reviewing which deployments target a device, creating new computer records, and forcing an agent check-in.

31estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: Apache-2.0

Como adicionar

/plugin marketplace add wyre-technology/msp-claude-plugins

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/immybot-endpoint-management/svg)](https://www.skillteca.com.br/skills/immybot-endpoint-management)

Skills relacionadas

Ver todas de DevOps e Infra →

Alerta por categoria

Receba novas skills de DevOps e Infra toda segunda

1 email curto, só com as skills novas de DevOps e Infra. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

ImmyBot Endpoint Management

ImmyBot manages Windows endpoints (computers) grouped under tenants (client organizations). This skill covers querying and onboarding those computers and inspecting their state.

API Tools

| Tool | Purpose | |------|---------| | immybot_computers_list | List computers with tenant/online/OS/status filters | | immybot_computers_get | Full detail for one computer by ID | | immybot_computers_search | Search by name, serial number, etc. | | immybot_computers_inventory | Installed-software / hardware inventory for a computer | | immybot_computers_deployments | Deployments targeting a specific computer | | immybot_computers_create | Create a new computer record | | immybot_computers_trigger_checkin | Force an agent check-in now |

Common Workflows

Survey a tenant's fleet

  1. immybot_tenants_search → resolve the tenant ID.
  2. immybot_computers_list filtered by that tenant ID.
  3. Group results by online status and OS to spot stale or offline

endpoints.

Locate one computer

immybot_computers_search accepts hostname or serial number. Drill in with immybot_computers_get for OS, last-seen, tenant, and agent state.

Inventory audit

  1. immybot_computers_get for the device.
  2. immybot_computers_inventory for what is actually installed.
  3. immybot_computers_deployments for what desired-state expects.
  4. The gap between (2) and (3) is the remediation list — hand it to

the software-deployment workflow.

Onboard a new computer

immybot_computers_create registers a record (name, tenant ID, and optional serial / MAC / location). The ImmyBot agent must still be installed on the endpoint for it to come online.

Force a check-in

immybot_computers_trigger_checkin asks the agent to phone home immediately rather than waiting for its next scheduled interval — useful after staging a deployment when you want fast feedback.

Filtering Notes

  • online status is a point-in-time snapshot; a computer can be

enrolled but offline.

  • Always scope immybot_computers_list by tenant when working a

specific client — the unscoped list spans the whole MSP fleet.

  • Serial number is the most reliable search key when hostnames are

not unique across tenants.

Best Practices

  • Confirm a computer is online before triggering a maintenance

session against it — an offline endpoint just queues work.

  • Use inventory data to validate a deployment actually landed rather

than trusting the deployment's reported status alone.

Related Skills

  • [software-deployment](../software-deployment/SKILL.md) — deploy software to these computers
  • [maintenance-sessions](../maintenance-sessions/SKILL.md) — reconcile desired state
  • [api-patterns](../api-patterns/SKILL.md) — auth and the desired-state model
Compartilhar X LinkedIn