media-path-validator
Skill1 starsChanged 4 months agoMITView on GitHub
Validate that media library and download paths are correctly mounted, writable, and on the same filesystem for hardlinks (not copies) between the Arr apps' download and library folders. Use when the user reports an Arr app "importing" via slow copy instead of instant hardlink/move, sees permission errors on import, sets up a new root folder or download client path, or after any docker-compose volume/mount change. Trigger phrases: "radarr is copying instead of hardlinking", "check the media paths", "permission denied importing", "validate mount points", "did I break the paths".
In this repository7 other files it gives its agents.
- arr-config-syncSkill
- docker-compose-managerSkill
- download-client-orchestratorSkill
- health-monitorSkill
- request-manager-integratorSkill
- secret-injectorSkill
- trash-guides-applierSkill
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 56
Read-only tool: it never creates, deletes, or moves files — only os.stat/os.access checks and a non-persisted os.link() dry-probe (creates …
≈ “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
Media Path Validator
Cross-Arr-app hardlinking (instant "import" instead of a slow copy across filesystems) requires the download client's completed-download folder and the library's root folder to be on the same filesystem inside the container — not just both "mounted", but sharing the same device ID. This is the single most common Arr-stack misconfiguration, and it's invisible until an import happens (Radarr/Sonarr silently fall back to copy+delete, which works but is slow and doubles disk I/O during import).
What it checks
- Existence — does the path exist inside the container/host as configured?
- Writability — can the runtime user actually write there?
- Same-filesystem — do a download path and a library path share
st_dev(i.e. wouldos.link()succeed), using Python'sos.stat(). - Case/trailing-slash consistency — catches the classic
/media/moviesvs/media/movies/root-folder mismatch that makes Radarr treat an existing folder as new.
Usage
python3 validator.py check /downloads/complete /media/movies # pairwise hardlink check
python3 validator.py check-all --config paths.json # check every pair from a config file
python3 validator.py writable /media/tv
python3 validator.py exists /downloads/complete /media/movies /media/showspaths.json format:
{
"pairs": [
{"download": "/downloads/complete", "library": "/media/movies", "label": "radarr"},
{"download": "/downloads/complete", "library": "/media/tv", "label": "sonarr"}
]
}Interpreting results
same_filesystem: falsebetween a download path and its matching library path is the root cause of "importing" behaving like a slow copy — fix by ensuring both paths are bind-mounted from the same host volume/root inside the container (this is adocker-compose.ymlvolume mapping issue, not something this skill can fix — it only diagnoses it).- Report findings plainly; do not attempt to edit
docker-compose.ymlvolume mappings automatically — that's a structural change the user should review, since it affects every container sharing the volume.
Safety rules
- Read-only tool: it never creates, deletes, or moves files — only
os.stat/os.accesschecks and a non-persistedos.link()dry-probe (creates a temp hardlink then removes it immediately, only when both paths already passed the existence/writability checks).
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.

