SKILLEMALL.ai
RU Sign in

BC media-cli-local

Single-file bash CLI for the *arr media stack. Manage Sonarr, Radarr, Prowlarr, qBittorrent, Bazarr, Jellyseerr, and Tdarr from the terminal or via AI agents. Runs on the same machine as your services. No Docker, no Node, no Python packages.

ClawHub Hermes author: Solomon Neas v1.0.0 MIT-0 2 files body ≈ 1 062 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process C 59/100 · Has gaps — weak spots: result and completion, when it triggers, progress reporting

IntegrationDockerInfrastructureAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
66
Run on models
none yet
Process rating
C
59/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 241 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill

Process rating: all ten parameters 59/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 55Failures and branches. 1 branches
  • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 9 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1062 tokens
  • 100Running it twice. No mutating operations

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 241: enough signal without eating the budget
  • +4Structure: 14 headings
  • +3Step-by-step instructions: 9 items
  • +4Has examples (10 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.

External checks

ClawHub: clean
This is a disclosed local media-stack control helper, but agent-run destructive actions should be gated by user confirmation.
LLM: benign (medium) · VirusTotal: · 29 May 2026