/task-status

Drill into an N-central scheduled task's outcome - aggregate status down to per-device results and output

wyre-technology@wyre-technology

GitHub

From plugin

msp-claude-plugins

39200 skills141 agents200 commands

Install

$ npx -y skills add wyre-technology/msp-claude-plugins --agent claude-code

How 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/task-status

Context preview

What this command does when you run it.

Drill into an N-central scheduled task's outcome - aggregate status down to per-device results and output

Command definition

task-status.md

description: Drill into an N-central scheduled task's outcome - aggregate status down to per-device results and output
argument-hint: "[task_id] [device_id]"
arguments: [task_id, device_id]

N-central Task Status

Answer "did that task actually work?" - from aggregate outcome down to per-device results and captured output. This is the follow-up workflow after any scheduled task or direct support task run.

Prerequisites

N-central connected in Conduit (Connections → N-able N-central) with a valid Server URL and User-API Token
Tools: `ncentral_list_device_tasks`, `ncentral_get_task`, `ncentral_get_task_status`, `ncentral_get_task_status_details`

Steps

1. **Resolve the task**

If `task_id` was provided, go straight to step 2. If only `device_id` was provided, call `ncentral_list_device_tasks` for that device and let the user pick. If neither was provided, ask for one - do not guess.

2. **Get the definition and aggregate status**

Call `ncentral_get_task` for what the task is (script, parameters, targets), then `ncentral_get_task_status` for the aggregate outcome - completed / failed / in-progress counts across targets.

3. **Drill into failures only**

If the aggregate shows failures (or the user asked for output), call `ncentral_get_task_status_details` for per-device status, return codes, and captured output. Skip this on wide all-green tasks - the details payload is large.

4. **Produce the output**

Task header (name, what it runs, target count), aggregate outcome table, then per-failed-device detail: device name/ID, status, return code, and the relevant slice of output. If the task is still running, say so explicitly and suggest re-checking rather than polling in a tight loop.

Parameters

| Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| | task_id | string | No | prompt | Task to inspect | | device_id | string | No | none | Device to list tasks for when task_id is unknown |