Best for
- Use levelio-cli when an agent or technician needs a portfolio-wide answer about a Level-managed fleet - at-risk endpoints, patch exposure, alert clusters, stale agents, security-score distribution, or custom-field gaps…
Servosity/msp-skills/skills/levelio/SKILL.md
Every Level RMM endpoint, plus a local SQLite fleet store and offline cross-entity rollups no Level tool has: at-risk ranking, patch posture, alert triage, and stale-device detection in one command. Trigger phrases: `check my level fleet`, `what level devices are at risk`, `level patch posture`, `level stale devices`, `level client scorecard`, `triage level alerts`, `use levelio`, `run levelio-cli`.
Decision brief
Every Level RMM endpoint, plus a local SQLite fleet store and offline cross-entity rollups no Level tool has: at-risk ranking, patch posture, alert triage, and stale-device detection in one command. Trigger phrases: `check my level fleet`, `what level devices are at risk`, `level patch posture`, `level stale devices`, `level client scorecard`, `triage level…
Compatibility matrix
| 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
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/Servosity/msp-skills --skill "skills/levelio"Inspect the Agent Skill "levelio" from https://github.com/Servosity/msp-skills/blob/30e109db0872897de0b88adb38d81d4c292da3ae/skills/levelio/SKILL.md at commit 30e109db0872897de0b88adb38d81d4c292da3ae. 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
Authenticate with a Level API key (Settings - API keys; read-only is enough for every list/show/sync/analytics command). Export it as LEVELAPITOKEN; it is sent as 'Authorization: Bearer '.
This skill drives the levelio-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:
Use levelio-cli when an agent or technician needs a portfolio-wide answer about a Level-managed fleet - at-risk endpoints, patch exposure, alert clusters, stale agents, security-score distribution, or custom-field gaps - rather than a single device's detail. It is the right tool…
Do not use this CLI for: - single-device detail lookups (use devices show , not the fleet analytics commands) - real-time monitoring without a prior sync - analytics commands read the local store - authoring automations, scripts, or monitoring policies - the public API only trig…
These capabilities aren't available in any other tool for this API.
Permission review
The documentation asks the agent to run terminal commands or scripts.
npx -y @mvanhorn/printing-press-library install levelio --cli-onlyThe documentation asks the agent to run terminal commands or scripts.
go install github.com/mvanhorn/printing-press-library/library/monitoring/levelio/cmd/levelio-cli@latestThe documentation includes sending, uploading, or posting data to a remote service.
| `webhook:<url>` | POST the output body to the URL (`application/json` or `application/x-ndjson` when `--compact`) |The documentation includes network, browsing, or remote request actions.
| `webhook:<url>` | POST the output body to the URL (`application/json` or `application/x-ndjson` when `--compact`) |Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 83/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 15 | 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
This skill drives the levelio-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:
$HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:
npx -y @mvanhorn/printing-press-library install levelio --cli-only
levelio-cli --version$PATH for the agent/runtime that will invoke this skill.If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.4 or newer). This installs into $GOPATH/bin (default $HOME/go/bin), so add that directory to $PATH instead:
go install github.com/mvanhorn/printing-press-library/library/monitoring/levelio/cmd/levelio-cli@latest
If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.
levelio-cli syncs your entire Level estate - devices, groups, tags, custom fields, alerts, and OS updates - into a local SQLite database, then answers portfolio-wide questions offline that the Level web UI shows one device at a time. Match every API operation with agent-native output (--json/--select/--csv), then transcend with weighted at-risk ranking, fleet-wide patch posture, per-client posture scorecards, group-clustered alert triage, reboot-debt tracking, and custom-field coverage audits.
Use levelio-cli when an agent or technician needs a portfolio-wide answer about a Level-managed fleet - at-risk endpoints, patch exposure, alert clusters, stale agents, security-score distribution, or custom-field gaps - rather than a single device's detail. It is the right tool for cross-entity rollups, anti-joins (what is missing), and scriptable RMM automation, all offline against a synced local store.
Do not use this CLI for:
These capabilities aren't available in any other tool for this API.
at-risk - Rank the worst endpoints across every axis at once - active alerts, pending patches, low security score, and how long they have been dark - as a single weighted risk score.
Reach for this when an agent needs the single prioritized 'fix these first' list across the whole fleet instead of one health axis at a time.
levelio-cli at-risk --top 20 --agent
patch-posture - Aggregate OS updates across the fleet - available vs installed, by category and device, including patches that errored - so you can see exposure at a glance.
Use when an agent must report fleet-wide patch exposure or pick which category of updates to push next.
levelio-cli patch-posture --category security --agent
fleet - One-screen inventory rollup, cross-tabbed any way you slice it - by OS, platform, group, or tag - with online and maintenance counts.
Reach for this for a portfolio-wide inventory answer instead of paging through device lists.
levelio-cli fleet --by os --online --agent
alert-triage - Cluster unresolved alerts by group and severity with device context, so systemic fires surface above one-off noise.
Reach for this to answer 'where are my fires and which are systemic' in one call.
levelio-cli alert-triage --severity critical --group-by group --agent
client-scorecard - One row per top-level group (client) with device count, online %, open critical alerts, average security score, stale count, and patch exposure - the QBR-ready per-client rollup.
Reach for this when an agent needs per-client fleet posture in one table - which client is worst, where to focus - instead of walking groups and devices one call at a time.
levelio-cli client-scorecard --agent
stale - List devices that have gone dark - not seen in N days - with an option to exclude machines intentionally in maintenance mode.
Use to find agents that silently stopped checking in without chasing each device in the UI.
levelio-cli stale --days 14 --exclude-maintenance --agent
group-tree - Render the Level group hierarchy with each node showing its real rolled-up health - descendant device, alert, stale, and score counts.
Use to see the org structure annotated with where the problems actually concentrate.
levelio-cli group-tree --with alerts,stale,score --agent
since - Show what changed in a recent time window - new alerts, newly published updates, and devices last seen - so you can answer 'what happened since I last looked'.
Reach for this at the start of a shift to catch up on everything that moved overnight.
levelio-cli since --hours 24 --agent
alert-recurrence - Rank which alert names fire most often across the fleet and on how many distinct devices, so chronically noisy monitors surface above one-off fires.
Reach for this when the question is which monitors are chronically noisy and worth tuning, not which fires are burning right now (use alert-triage for that).
levelio-cli alert-recurrence --top 15 --agent
reboot-due - List devices waiting on a reboot to finalize installed patches - and how long they have been waiting - joined with online and maintenance state.
Reach for this when patches are installed but not yet effective - the reboot backlog is the gap between patch posture on paper and in reality.
levelio-cli reboot-due --days 3 --agent
cf-coverage - Audit which devices, groups, or the org are missing a custom-field value - the absence the UI can't show - via an anti-join.
Reach for this when an agent must enforce data hygiene - e.g. every device must carry an asset-tag or warranty field.
levelio-cli cf-coverage --missing --agent
security-posture - Show the fleet security-score distribution and everyone under a threshold, optionally rolled up by group.
Use to report fleet security posture or target the weakest endpoints for remediation.
levelio-cli security-posture --below 70 --by-group --agent
tag-audit - Surface tag-data drift: devices with zero tags, orphan tags applied to nothing, and duplicate tag names that fragment the fleet.
Reach for this when fleet filters and automations misbehave because tag data drifted - untagged devices and orphan tags are invisible until audited.
levelio-cli tag-audit --agent
alerts - Alerts generated by monitoring devices.
levelio-cli alerts list - Returns a list of your alerts.levelio-cli alerts show - Retrieves the details of an existing alert.automations - Operations on automations.
levelio-cli automations <token> - Triggers an automation via a webhook.custom-field-values - Values assigned to custom fields for the organization, groups, and devices.
levelio-cli custom-field-values delete - Deletes a custom field value for the organization, group, or device.levelio-cli custom-field-values list - Returns a list of custom field values for the organization, groups, or devices.levelio-cli custom-field-values update - Set a custom field value for the organization, group, or device.custom-fields - Custom fields that can have values assigned to them.
levelio-cli custom-fields create - Creates a custom field.levelio-cli custom-fields delete - Deletes a custom field.levelio-cli custom-fields list - Returns a list of custom fields.levelio-cli custom-fields show - Retrieves the details of an existing custom field.levelio-cli custom-fields update - Updates a custom field.devices - Devices with the Level agent installed.
levelio-cli devices delete - Deletes the specified device.levelio-cli devices list - Returns a list of your devices.levelio-cli devices show - Retrieves the details of an existing device.levelio-cli devices update - Updates the specified device.groups - The group hierachy that contains devices.
levelio-cli groups create - Creates a new group.levelio-cli groups delete - Deletes an existing group.levelio-cli groups list - Returns a list of your groups.levelio-cli groups show - Retrieves the details of an existing group.levelio-cli groups update - Updates an existing group.tags - Tags that can be applied to devices.
levelio-cli tags create - Creates a new tag.levelio-cli tags delete - Deletes a tag.levelio-cli tags list - Returns a list of tags.levelio-cli tags show - Retrieves a tag.levelio-cli tags update - Updates an existing tag.updates - Update operations and status for devices.
levelio-cli updates list - Returns a list of your updates.levelio-cli updates show - Retrieves the details of an existing update.When you know what you want to do but not which command does it, ask the CLI directly:
levelio-cli which "<capability in your own words>"
which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match - fall back to --help or use a narrower query.
levelio-cli since --hours 12 --agent
Everything that changed overnight - new alerts, new updates, devices that checked in - in one structured payload.
levelio-cli patch-posture --category security --agent --select summary,by_category
Fleet-wide pending vs installed security updates, narrowed to just the rollup fields an agent needs.
levelio-cli at-risk --top 10 --agent --select rank,hostname,risk_score,reasons
Top-10 risk ranking with only the decision fields, ready to pipe into a ticket.
levelio-cli stale --days 7 --exclude-maintenance
Devices that have not checked in for a week and are not in maintenance - the silent-failure list.
levelio-cli cf-coverage --missing --agent
Every assignee missing a custom-field value, so required asset/warranty data can be backfilled.
levelio-cli client-scorecard --agent
One row per client group - devices, online %, open criticals, average security score, stale count, and patch exposure - ready for a QBR slide.
Authenticate with a Level API key (Settings -> API keys; read-only is enough for every list/show/sync/analytics command). Export it as LEVEL_API_TOKEN; it is sent as 'Authorization: Bearer '.
Run levelio-cli doctor to verify setup.
Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.
Pipeable - JSON on stdout, errors on stderr
Filterable - --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:
levelio-cli alerts list --agent --select id,name,status
Previewable - --dry-run shows the request without sending
Offline-friendly - sync/search commands can use the local SQLite store when available
Non-interactive - never prompts, every input is a flag
Explicit retries - use --idempotent only when an already-existing create should count as success, and --ignore-missing only when a missing delete target should count as success
Commands that read from the local store or the API wrap output in a provenance envelope:
{
"meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
"results": <data>
}
Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal AND no machine-format flag (--json, --csv, --compact, --quiet, --plain, --select) is set - piped/agent consumers and explicit-format runs get pure JSON on stdout.
When you (or the agent) notice something off about this CLI, record it:
levelio-cli feedback "the --since flag is inclusive but docs say exclusive"
levelio-cli feedback --stdin < notes.txt
levelio-cli feedback list --json --limit 10
Entries are stored locally at ~/.local/share/levelio-cli/feedback.jsonl. They are never POSTed unless LEVELIO_FEEDBACK_ENDPOINT is set AND either --send is passed or LEVELIO_FEEDBACK_AUTO_SEND=true. Default behavior is local-only.
Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.
Every command accepts --deliver <sink>. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:
| Sink | Effect |
|---|---|
stdout | Default; write to stdout only |
file:<path> | Atomically write output to <path> (tmp + rename) |
webhook:<url> | POST the output body to the URL (application/json or application/x-ndjson when --compact) |
Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.
A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.
levelio-cli profile save briefing --json
levelio-cli --profile briefing alerts list
levelio-cli profile list --json
levelio-cli profile show briefing
levelio-cli profile delete briefing --yes
Explicit flags always win over profile values; profile values win over defaults. agent-context lists all available profiles under available_profiles so introspecting agents discover them at runtime.
| Code | Meaning |
|---|---|
| 0 | Success |
| 2 | Usage error (wrong arguments) |
| 3 | Resource not found |
| 4 | Authentication required |
| 5 | API error (upstream issue) |
| 7 | Rate limited (wait and retry) |
| 10 | Config error |
Parse $ARGUMENTS:
help, or --help → show levelio-cli --help outputinstall → ends with mcp → MCP installation; otherwise → see Prerequisites above--agent)go install github.com/mvanhorn/printing-press-library/library/monitoring/levelio/cmd/levelio-mcp@latest
claude mcp add levelio-mcp -- levelio-mcp
claude mcp listwhich levelio-cli
If not found, offer to install (see Prerequisites at the top of this skill).--agent flag:
levelio-cli <command> [subcommand] [args] --agent
levelio-cli <command> --help.Alternatives
coreyhaines31/marketingskills
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
coreyhaines31/marketingskills
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o
event4u-app/agent-config
Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.
K-Dense-AI/scientific-agent-skills
Distributed computing for larger-than-RAM pandas/NumPy workflows. Use when you need to scale existing pandas/NumPy code beyond memory or across clusters. Best for parallel file processing, distributed ML, integration with existing pandas code. For out-of-core analytics on single machine use vaex; for in-memory speed use polars.