SKILLEMALL.ai

BD Plex Server

Manage Plex Media Server with optional Nvidia Shield ADB device management.

ClawHub Agent Skills author: Mirko Grewing v1.0.1 MIT-0 5 files body ≈ 766 tokens Open the sourceclawhub.ai analyzed 2 d ago

Manage Plex Media Server with optional Nvidia Shield ADB device management.

As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureInfrastructureSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
99
Quality 40%
67
Run on models
none yet
Process rating
D
46/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
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.
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Exfiltration exfil-secret-in-url scripts/shield-cli.js:103
    Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)
    '-s', `https://plex.tv/api/resources?X-Plex-Token=…
    placeholder

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

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 46/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (Plex Server) differs from the folder (plex-server)
  • 85Steps. 15 steps, 1 vague phrases
  • 100Tools and files. Tools declared in frontmatter
  • 100Execution cost. Instruction body is 766 tokens
  • 100Running it twice. No mutating operations
  • low The response is described with custom markup (5 tags): a typed call is more reliable

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)
  • +3Description length 75: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 15 items
  • +4Has examples (3 code blocks)
  • +3All 1 scripts are documented

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

External checks

ClawHub: clean
This skill does what it claims: it manages a Plex server and optional Nvidia Shield device using disclosed local commands and stored Plex credentials.
LLM: benign (high) · VirusTotal: · 5 Jul 2026