arr-config-sync
Skill1 starsChanged 4 months agoMITView on GitHub
Backup, restore, and diff configuration (root folders, quality profiles, indexers, download-client settings, notification connections) across Arr-stack apps — Radarr, Sonarr, Lidarr, Readarr, Prowlarr — via their REST APIs. Use when the user asks to back up an Arr app's config before a change, restore it after something breaks, compare config against an older backup, or replicate a setting (e.g. a root folder or download client) across all Arr apps at once. Trigger phrases: "back up radarr config", "sync indexers to all arr apps", "what changed in sonarr's config", "restore radarr settings", "add this root folder to every arr app".
- Reads credentials
In this repository7 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 63
Never delete existing entries on restore/sync — only add or update by matching id/name.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Arr Config Sync
Talks to the Radarr/Sonarr/Lidarr/Readarr/Prowlarr REST APIs (all share the same
Servarr API shape — /api/v3 for Radarr/Sonarr, /api/v1 for Lidarr/Readarr/Prowlarr)
to export, diff, and replicate configuration as JSON. Covers root folders, download
clients, indexers, notification connections, and full-app backup/restore snapshots —
for quality-profile/custom-format work specifically, see the trash-guides-applier
skill in this same toolkit.
Auth
Each app needs its API key, read from environment variables (never hardcode a key in a command or file):
RADARR_URL / RADARR_API_KEY
SONARR_URL / SONARR_API_KEY
LIDARR_URL / LIDARR_API_KEY
READARR_URL / READARR_API_KEY
PROWLARR_URL / PROWLARR_API_KEY*_URL defaults to http://localhost:<default-port> if unset (7878/8989/8686/8787/9696
respectively) — override to the docker-internal hostname (e.g. http://radarr:7878) when
running inside a compose network, or the LAN-facing URL when running from the host. Never
hardcode a real LAN IP as the default — that must come from the environment.
Usage
# Snapshot one app's config to a timestamped JSON file
python3 sync.py backup radarr --out ./backups/
# Restore a specific section from a backup file (dry-run by default)
python3 sync.py restore radarr ./backups/radarr-2026-07-13T12:00:00.json --section rootfolder --apply
# Diff the same app's live config against an older backup (diffing two different
# apps isn't meaningful — different schemas)
python3 sync.py diff radarr ./backups/radarr-2026-01-01T00:00:00.json
# Replicate a root folder across an Arr app
python3 sync.py add-root-folder --path /media/movies --apps radarr
python3 sync.py add-root-folder --path /media/tv --apps sonarr
# List what apps are reachable/configured right now
python3 sync.py list-appsSections covered
rootfolder, downloadclient, indexer, notification, qualityprofile (read-only
export — use trash-guides-applier to write quality profiles/custom formats).
Safety rules
restoreis dry-run unless--applyis passed: it prints a diff of what would change before touching anything.- Never delete existing entries on restore/sync — only add or update by matching
id/name. Removing a root folder or indexer a user is actively relying on is a destructive action outside this skill's scope; flag it instead of doing it silently. - Back up before restoring:
restorerefuses to run if no backup file is given.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

