request-manager-integrator
Skill1 starsChanged 4 months agoMITView on GitHub
Configure and verify a request manager (Jellyseerr/Overseerr-family) integration with Radarr and Sonarr — connect it to the right instance, root folder, and quality profile, and confirm the connection is actually live. Use when the user asks to hook up Jellyseerr/Overseerr to radarr/sonarr, add a second quality-profile-specific connection, or troubleshoot "requests aren't showing up in radarr/sonarr". Trigger phrases: "connect jellyseerr to radarr", "set up request manager", "requests aren't being sent to sonarr", "add a second radarr connection to overseerr".
- Reads credentials
In this repository7 other files it gives its agents.
- arr-config-syncSkill
- docker-compose-managerSkill
- download-client-orchestratorSkill
- health-monitorSkill
- media-path-validatorSkill
- 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 51
If requests silently vanish (accepted in the request manager, never appear in Radarr/Sonarr's queue), check the connection's configured …
≈ “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
Request Manager Integrator
Configures a Jellyseerr/Overseerr-family request manager's Radarr/Sonarr "server" connections via its REST API, and verifies end-to-end reachability (request manager -> Arr app) rather than just writing config and assuming it works.
Auth / config
SEERR_URL / SEERR_API_KEY (defaults to http://localhost:5055)
RADARR_URL / RADARR_API_KEY (same vars as arr-config-sync / trash-guides-applier)
SONARR_URL / SONARR_API_KEYSEERR_* works for either Jellyseerr or Overseerr — they share the same request-manager
settings API shape.
The Arr URL the request manager needs to store is whatever hostname it can actually reach
from where it runs — the docker-internal service name (e.g. http://radarr:7878) if
both run in the same compose network, not localhost (which resolves to the request
manager's own container, not Radarr/Sonarr). Never hardcode a LAN IP; always resolve via
env var or docker service name.
Usage
python3 integrator.py list-connections # what's currently configured
python3 integrator.py connect radarr --root /media/movies --profile "HD Bluray + WEB"
python3 integrator.py connect sonarr --root /media/tv --profile "WEB-1080p"
python3 integrator.py verify # test every configured connection actually reaches its Arr appconnect looks up the target root folder and quality profile by name against the live
Arr instance (via the same API pattern as arr-config-sync) and fails loudly if either
doesn't exist yet, rather than writing a broken connection. It uses the Arr app's own
compose service name as the connection hostname by default — pass --name to label the
connection differently, but the hostname itself always comes from the app name, since
that's what the request manager's own container can actually resolve.
Interpreting results
verifyfailing for a connection thatlist-connectionsshows as configured usually means the Arr app's API key was rotated without updating the request manager, or the container-internal hostname changed — confirm the Arr container itself is reachable before assuming the request manager's config is wrong.- If requests silently vanish (accepted in the request manager, never appear in
Radarr/Sonarr's queue), check the connection's configured root folder against what
arr-config-sync list-apps/add-root-foldershows as actually present in the Arr app.
Safety rules
connectnever deletes or replaces an existing connection with the same name unless--forceis passed — multiple connections per app (e.g. different quality-profile routing) are a normal, intentional pattern, not something to silently collapse.
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.

