Meridian Vega
Official@meridianvega · United States of America
Offers specialized configuration, validation, and synchronization services for ErsatzTV playout environments and media library management systems.
Agent Skills by Meridian Vega
Showing 9 vetted skills indexed across 1 GitHub repositories.
MeridianVegaersatztv-schedule
Plan, validate, and write ErsatzTV Next playout JSON files.
MeridianVegaroutine
Automate the nightly ErsatzTV Next refresh with M3U/XMLTV generation and Jellyfin updates.
MeridianVegaersatztv-setup
Automate initial ersatztv-programmer plugin setup with Docker and Jellyfin library replication.
MeridianVegalibrarian-search
Rank candidate movies and TV releases using TMDB, Jellyfin, and Prowlarr data.
MeridianVegalibrarian-fetch
Submit librarian releases to NZBGet via JSON-RPC after disk-budget validation.
MeridianVegaersatztv-audit
Audit Legacy ErsatzTV versus Next lineup.json for migration gaps.
MeridianVegaersatztv-knowledge
Explain ErsatzTV architecture and repository layout across Legacy and Next stacks.
MeridianVegalibrarian-taste
Create and update a versioned taste.md profile with append-only feedback.
MeridianVegaersatztv-reference
Pin ErsatzTV Next schemas for playout.json, channel.json, and lineup.json validation.
Frequently Asked Questions About Meridian Vega
FAQPage SchemaWhat specific media management tasks does Meridian Vega enable?▼
Meridian Vega enables precise control over ErsatzTV playout schedules, automated M3U and XMLTV generation, and intelligent media library synchronization. It facilitates ranking candidate releases via TMDB and Prowlarr data, validating disk-budget constraints, and executing remote submissions to NZBGet for media acquisition.
Which technical personas benefit from these media management capabilities?▼
These capabilities are designed for media server administrators and home-lab enthusiasts managing complex ErsatzTV deployments. It specifically targets users requiring rigorous schema validation, automated lineup refreshes, and structured migration paths between legacy and next-generation media playout architectures.
What are the primary dependencies for running these media management routines?▼
Successful operation requires an existing Docker environment hosting Jellyfin, ErsatzTV, and Prowlarr instances. Users must maintain valid TMDB credentials and ensure network accessibility to NZBGet for remote JSON-RPC communication, alongside properly configured local storage for versioned taste profiles and lineup JSON files.