How do I install the N Central Admin skill?

Run npx skillmds@latest add dvcrn/n-central-admin in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is N Central Admin safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with N Central Admin?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is N Central Admin free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published N Central Admin?

dvcrn (@dvcrn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

N Central Admin by dvcrn — Agent Skill

Name: N Central Admin
Rating: 4.2 (5 reviews)
Author: dvcrn

N Central Admin

Operate N-able N-central safely and efficiently through its web UI. Use when handling device administration, filters, rules, scheduled tasks, automation policies, monitoring associations, remote tools, and tenant/customer/site scoped changes in N-central.

dvcrn Updated Sep 8, 2026 32 repo stars

File contents

N-central Admin

Use this skill to run reliable browser-driven N-central operations.

Operating model

Follow this sequence for almost every change:

Confirm scope (SO / Customer / Site).
Confirm targeting (filter preview or explicit devices).
Apply change (rule/task/template/action).
Validate on a small sample of devices.
Expand scope only after validation.

Read references only as needed

Read references/ui-navigation-and-operating-model.md for hierarchy, module navigation, and change-control flow.
Read references/filters-and-rules.md for filter expression logic, rule behavior, trigger events, and troubleshooting.
Read references/automation-policies-and-tasks.md for Automation Manager behavior, scheduled task execution, and offline/timing caveats.
Read references/device-details-tabs-and-tools.md for per-device tabs, quick actions, and tool availability expectations.
Read references/browser-operator-playbooks.md for browser execution playbooks and stability patterns.

Guardrails

Prefer the narrowest scope that solves the task.
Clone and specialize shared objects instead of risky in-place edits.
Name filters/rules/tasks with explicit scope and intent.
Confirm target count before save and after save.
Use pilot-first rollout for broad-impact changes.
Verify outcome using Monitoring, Associations, and Audit Trail.

Quick dispatch

If you need left-nav click paths, use references/ui-navigation-and-operating-model.md#left-navigation-path-map-common-admin-tasks.
If rule behavior is wrong, use references/filters-and-rules.md#rule-not-firing-checklist.
If scheduled execution behavior is wrong, use references/automation-policies-and-tasks.md#offline-and-timing-behavior.
If target selector arrows are confusing, use references/automation-policies-and-tasks.md#dual-list-selector-buttons-targeting-and-similar-fields.
If an expected tool is missing on a device, use references/device-details-tabs-and-tools.md#why-actions-may-be-unavailable.
If browser automation gets flaky, use references/browser-operator-playbooks.md#ui-stability-patterns.

---name: n-central-admindescription: Operate N-able N-central safely and efficiently through its web UI. Use when handling device administration, filters, rules, scheduled tasks, automation policies, monitoring associations, remote tools, and tenant/customer/site scoped changes in N-central.---# N-central AdminUse this skill to run reliable browser-driven N-central operations.## Operating modelFollow this sequence for almost every change:1. Confirm scope (SO / Customer / Site).2. Confirm targeting (filter preview or explicit devices).3. Apply change (rule/task/template/action).4. Validate on a small sample of devices.5. Expand scope only after validation.## Read references only as needed- Read `references/ui-navigation-and-operating-model.md` for hierarchy, module navigation, and change-control flow.- Read `references/filters-and-rules.md` for filter expression logic, rule behavior, trigger events, and troubleshooting.- Read `references/automation-policies-and-tasks.md` for Automation Manager behavior, scheduled task execution, and offline/timing caveats.- Read `references/device-details-tabs-and-tools.md` for per-device tabs, quick actions, and tool availability expectations.- Read `references/browser-operator-playbooks.md` for browser execution playbooks and stability patterns.## Guardrails- Prefer the narrowest scope that solves the task.- Clone and specialize shared objects instead of risky in-place edits.- Name filters/rules/tasks with explicit scope and intent.- Confirm target count before save and after save.- Use pilot-first rollout for broad-impact changes.- Verify outcome using Monitoring, Associations, and Audit Trail.## Quick dispatch- If you need left-nav click paths, use `references/ui-navigation-and-operating-model.md#left-navigation-path-map-common-admin-tasks`.- If rule behavior is wrong, use `references/filters-and-rules.md#rule-not-firing-checklist`.- If scheduled execution behavior is wrong, use `references/automation-policies-and-tasks.md#offline-and-timing-behavior`.- If target selector arrows are confusing, use `references/automation-policies-and-tasks.md#dual-list-selector-buttons-targeting-and-similar-fields`.- If an expected tool is missing on a device, use `references/device-details-tabs-and-tools.md#why-actions-may-be-unavailable`.- If browser automation gets flaky, use `references/browser-operator-playbooks.md#ui-stability-patterns`.

Frequently asked questions