librarian-fetch

Submit librarian releases to NZBGet via JSON-RPC after disk-budget validation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MeridianVega/claude-marketplace --skill librarian-fetch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: librarian-fetch
Source: https://github.com/MeridianVega/claude-marketplace/tree/main/plugins/ersatztv-programmer/skills/librarian-fetch
Command: npx skills add https://github.com/MeridianVega/claude-marketplace --skill librarian-fetch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This feature submits releases from the librarian workflow to NZBGet's JSON-RPC append endpoint, while enforcing a disk-budget floor and recording per-run audit logs to keep track of submissions.

Core Features & Use Cases

  • Disk-budget enforcement: validates free space before each append to prevent stalling the transcoding cache.
  • NZBGet JSON-RPC submissions: pushes selected releases to NZBGet as the act half of the librarian's job.
  • Queue-status read-only mode: provides a status snapshot of the active NZBGet queue for monitoring and traceability.
  • Run logging: writes a per-run audit log documenting submissions and outcomes for traceability and debugging.

Quick Start

Submit the current librarian queue to NZBGet while honoring the disk budget and logging the run.

Frequently Asked Questions about librarian-fetch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I submit releases to NZBGet while checking disk space first?

You can submit releases to NZBGet via JSON-RPC after validating available disk space against a budget floor. The submission enforces preflight checks to prevent stalling the transcoding cache before appending the job.

What is disk-budget enforcement for NZBGet queue submissions?

Disk-budget enforcement validates free disk space before each NZBGet append to prevent stalling the transcoding cache. It acts as a preflight check ensuring sufficient storage exists before the queue accepts the job.

Can I monitor the NZBGet queue status without submitting new jobs?

You can retrieve a read-only queue-status snapshot of the active NZBGet queue for monitoring and traceability. This observation mode provides visibility into current jobs without triggering new submissions.

How do I prevent duplicate NZBGet submissions from an automated workflow?

Duplicate prevention is built into the submission logic, checking the queue before appending releases. This ensures the librarian workflow does not submit the same release to NZBGet twice during a run.

Does the NZBGet submission workflow handle logging and safe failure?

The workflow writes a per-run audit log documenting submissions and outcomes for traceability and debugging. Safe failure handling ensures reliable, auditable queue submissions even when errors occur during the process.

What are the limitations of automating NZBGet submissions with disk budgets?

Submissions will fail safely if the disk-budget floor is exceeded or if duplicate releases are detected. The preflight checks prevent appending jobs when storage is insufficient, limiting queue growth to protect the transcoding cache.