Naming convention

Script Naming Guide

Nerdy-RMMScripts uses a predictable filename format so scripts are easy to scan, search, import, and maintain across RMM platforms.

Getting startedView repository

Filename Format

<Category> - <Descriptive Title>.<ext>

Monitor - CPU Usage.shSecurity - Firewall Status.shAgent - Wazuh Update.ps1Maintain - Disk Clean.bat

Rules

Keep the original file extensionUse spaces for readable titlesUse one clear category prefixSeparate category and title with -

Category Reference

CheckOne-off status and health verification tests.

MonitorOngoing resource, uptime, trend, or metric checks.

AuditSecurity, configuration, and compliance enumeration.

CollectInventory and general data gathering.

Software ManagementPackage install, update, repo, and software state tasks.

SecurityHardening, firewall, access control, and enforcement workflows.

NetworkRoutes, DNS, interfaces, connectivity, and diagnostics.

AgentManagement and monitoring agent status or maintenance.

MaintainCleanup, repair, pruning, and routine maintenance.

CustomizeEnvironment, profile, shell, or personalization changes.

CronCrontab, scheduled task, and automation schedule checks.

ImageContainer image hygiene and cleanup.

OSOperating system settings and platform configuration.

Exit Codes

0OK or successful completion.

1Alert, error, or failed check.

2Secondary state, such as auto-recovered or warning.

Best Practices

Be specific

Choose the most accurate category and keep the title short enough to scan quickly.

Use title case

Prefer names like Monitor - CPU Usage.sh over vague names like script.sh.

Test exit codes

Make sure your RMM receives clear success, alert, and warning states.

Choosing Between Similar Categories

Use Collect - for pure inventory and data gathering. Use Audit - when the script is security-relevant, checks configuration drift, or produces reviewable compliance information.