What problem does it solve?
This Skill helps you troubleshoot and optimize a self-hosted media-consumer stack by answering questions about Jellyfin video playback, transcoding behavior (including NVENC constraints), Jellyseerr request routing into the arr ecosystem, and Navidrome music scrobbling/integration setup.
Core Features & Use Cases
- Service topology + ports awareness: Quickly map which service is responsible for what (Jellyfin/Jellyseerr/Navidrome), including internal IPs, external domains, and network separation between
servarr and media.
- Transcoding and NVENC “GPU mutex” guidance: Diagnose performance issues and scheduling conflicts caused by the single Pascal NVENC chip shared across Jellyfin, Tdarr, and Bazarr/Whisper workloads.
- Cross-stack integration debugging: Identify why Jellyseerr-to-arr requests fail by directing investigation to Sonarr/Radarr internals, API key sources, and the correct internal URLs to avoid WAF/TLS hop issues.
- Playback/library metadata troubleshooting: Explain Jellyfin library scan behavior, mount layouts, and heavy scanning I/O implications under shfs.
Quick Start
Ask it: “Help me debug why a client playback triggers heavy transcoding and where I should check logs/settings for Jellyfin, considering NVENC contention and Jellyseerr/arr routing.”