Skip to content
Development
Skill

/cluster-operations

Working the clustermgmt namespace through `clustermgmt_execute` — cluster and host inventory, configuration and health state — plus the adjacent read surfaces: `prism_execute` for Prism Central tasks and categories, and `lifecycle_execute` for LCM upgrade inventory and

From plugin
msp-claude-plugins
52200 skills146 agents200 commands4 MCP

Claude Code

$ npx -y skills add wyre-ai/msp-claude-plugins --skill cluster-operations --agent claude-code

SKILL.md

cluster-operations.SKILL.md
name: "Nutanix Cluster Operations"
description: >
  Working the clustermgmt namespace through `clustermgmt_execute` —
  cluster and host inventory, configuration and health state — plus the
  adjacent read surfaces: `prism_execute` for Prism Central tasks and
  categories, and `lifecycle_execute` for LCM upgrade inventory and
  recommendations.
when_to_use: >-
  When inspecting Nutanix clusters, hosts, or Prism Central itself. Use
  when: nutanix cluster, cluster health nutanix, host inventory nutanix,
  clustermgmt, prism central tasks, lcm inventory, nutanix upgrade
  status, or nutanix cluster configuration.

Nutanix Cluster Operations

Overview

Cluster-level work spans three namespaces. `clustermgmt` is the core: clusters, hosts/nodes, cluster profiles, and storage container associations. `prism` covers Prism Central's own surface — tasks, categories, cluster registration state. `lifecycle` exposes LCM (Lifecycle Manager) inventory: what software/firmware versions each cluster runs and what upgrades LCM recommends. Each is reached through its own executor after discovery.

Key Concepts

| Concept | Namespace | Notes | |---------|-----------|-------| | Cluster | `clustermgmt` | Config, health state, nodes, network config; identified by `extId` | | Host / node | `clustermgmt` | Physical servers in a cluster; disk and NIC detail per host | | Task | `prism` | Async operations on PC; status is `QUEUED` / `RUNNING` / `SUCCEEDED` / `FAILED` | | Category | `prism` | key:value tags shared by VMs, hosts, policies | | LCM entity | `lifecycle` | An upgradeable component with current and available versions |

Common Workflows

Cluster health snapshot

1. `listOperations(namespace="clustermgmt", search="clusters")` → list-clusters operation. 2. `clustermgmt_execute` to list clusters; capture name, `extId`, version, node count. 3. For each cluster of interest, get it by `extId` for config and health detail, and list its hosts for per-node state. 4. Fold in open alerts from the `monitoring` namespace (see the monitoring-aiops skill) for a complete health picture.

Recent task audit on Prism Central

1. Discover the list-tasks operation in `prism`. 2. `prism_execute` with an OData filter, e.g. `_filter="status eq 'FAILED'"` plus a time-range predicate, ordered by start time. 3. Report each task's `extId`, operation type, error messages, and timing.

Upgrade posture (read-only)

1. `listOperations(namespace="lifecycle", search="entities")` to find the LCM inventory operation; `lifecycle_execute` to list current component versions per cluster. 2. Discover and read LCM recommendations to see upgrade candidates and blocking pre-check conditions. 3. Stop there: performing upgrades, pre-checks that mutate state, and node imaging are non-GET and blocked by read-only mode. Deliver the findings as an upgrade plan for a human to execute.

Gotchas

  • **The lifecycle namespace is huge (~110 operations).** Always narrow

`listOperations` with a `search` term; paging the whole namespace wastes turns.

  • **Storage containers appear in two namespaces.** `clustermgmt` holds

cluster-side container associations; `storage` is the primary container/volume surface. Prefer `storage` for capacity questions.

  • **Cluster registration is a prism concern.** A cluster missing from

`clustermgmt` lists may simply not be registered with this Prism Central — check registration state via `prism` before declaring it down.

Related Skills

  • [api-patterns](../api-patterns/SKILL.md) — discovery workflow, OData, read-only mode
  • [storage](../storage/SKILL.md) — containers, volume groups, capacity
  • [monitoring-aiops](../monitoring-aiops/SKILL.md) — alerts and capacity forecasting
Read more
@wyre-technology
Ships withmsp-claude-plugins

One command to supercharge Claude Code for MSP workflows. Then restart Claude Code. That's it. Documentation: mcp.wyre.ai

52200 skills146 agents4 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
52
Star history of wyre-technology/msp-claude-plugins on GitHub, a chart by star-history.com

Other skills on msp-claude-plugins.

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills13d309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc2w293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react4d252k
@facebook@facebookInstall Skill

Questions about cluster-operations.

Which coding agents can use cluster-operations?
cluster-operations installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.