BC emby
Emby Server API integration for managing media libraries, users, devices, live TV, and encoding settings. Use when interacting with Emby media server including: (1) Querying movies, shows, artists, albums, genres, (2) Managing users and authentication, (3) Controlling playback sessions, (4) Live TV and recording management, (5) Library and folder operations, (6) Device management, (7) System configuration and encoding options.
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.
The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.
How to improve
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
medium Secrets in code
secret-labelled-tokenemby.py:6Labelled token / key literal (vendor format unknown — verify it is not a live credential)API_KEY = "6524…7aa"
-
medium Secrets in code
secret-labelled-tokenSKILL.md:14Labelled token / key literal (vendor format unknown — verify it is not a live credential)API_KEY = "6524…7aa" # 修改为你的API Key
-
low Secrets in code
secret-password-literalemby.py:6Hard-coded password / key literal (may be an example)API_KEY = "6524…7aa"
-
low Secrets in code
secret-password-literalSKILL.md:14Hard-coded password / key literal (may be an example)API_KEY = "6524…7aa" # 修改为你的API Key
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Emby Server API integration for managing media libraries, users, d… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 43 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 653 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 430: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 43 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.