CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mediaserver-operation

Use this skill when the user asks to inspect, diagnose, or directly operate a configured Emby, Jellyfin, Plex, ZSpace, UGREEN, TrimeMedia, or Navidrome server. It discovers provider capabilities on demand and supports libraries, native movie/music search, episode coverage, recent media, resume state, playback sessions, statistics, scans, metadata refreshes, and provider play URLs without adding permanent tools.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured operational skill with strong error-recovery and verification guidance for side-effect operations. Its weaknesses are redundancy (duplicated action table and repeated query-projection boilerplate) and progressive disclosure: the full action contract is inlined rather than split out, and the one reference to deeper documentation is a dangling path.

Suggestions

Drop the action summary table (or reduce it to action names only) since the per-action sections already carry the full contract, and state the `query` projection rules once in the 'Query Content Projection' section instead of repeating them inside every action.

Move the complete action contract into a reference file (e.g. references/actions.md) and keep only the fast-path usage, call shape, and safety rules in SKILL.md, signaling the reference clearly.

Fix or remove the dangling 'See docs/media-server-query.md' reference — the file is absent from the skill bundle, so either bundle it or describe the projection compatibility limits inline.

DimensionReasoningScore

Conciseness

Mostly efficient with no beginner-concept padding, but the action summary table ('| `activity.backdrops` | 读取服务近期媒体的背景图...arguments: `limit`, `remote` |') duplicates the per-action sections that follow, and the `query` projection sentence ('统一内容投影,如 {"fields":["identity","path"]};省略或 fields=null 保留原内容...') is repeated verbatim ~10 times instead of being defined once and referenced.

3 / 5

Actionability

Fully executable guidance throughout: exact bash invocations ('python skills/mediaserver-operation/scripts/mp-mediaserver.py call --server "living-room" --action activity.latest --arguments \'{"limit":20}\''), complete per-action argument types, defaults, required markers (e.g. '`item_id*` (string)'), enums, and a copy-paste-ready external MCP JSON example.

5 / 5

Workflow Clarity

Clear sequenced workflow with explicit validation and feedback loops: the fast path ('If multiple servers remain ambiguous, the failed call lists every valid server name. Reuse that list for the next direct call'), batch error correction ('correct every reported field together instead of retrying one field at a time'), and pre-confirmation plus post-verification for side-effect actions ('Before `library.scan`, confirm the exact server and scan scope', 'After a scan or refresh, verify with `activity.latest`, `items.detail`, or the smallest relevant library query').

5 / 5

Progressive Disclosure

Section headers and the script path reference are well organized, but ~130 lines of the complete action contract ('This is the complete Media Server Operation action contract... a field name ending in `*` is required') are inlined in SKILL.md where a separate reference file would fit better, and the single pointer to deeper detail ('See `docs/media-server-query.md` for the mappings and compatibility limits') targets a file that does not exist in the bundle.

3 / 5

Total

16

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is an exemplary trigger block: third-person, concise, and dense with concrete capabilities and the exact server product names a user would mention. It explicitly answers both what the skill does and when to use it, with no vague or padded language.

DimensionReasoningScore

Specificity

Lists ten concrete capabilities ('libraries, native movie/music search, episode coverage, recent media, resume state, playback sessions, statistics, scans, metadata refreshes, and provider play URLs'), matching the anchor for multiple specific concrete actions with comprehensive coverage; nothing is vague or abstract.

5 / 5

Completeness

Explicitly answers both questions: when ('Use this skill when the user asks to inspect, diagnose, or directly operate a configured... server') and what ('It discovers provider capabilities on demand and supports libraries, native movie/music search...'), with concrete trigger phrases, in third person.

5 / 5

Trigger Term Quality

Covers the natural phrases users would say when needing this skill — the product names users actually mention ('Emby, Jellyfin, Plex, ZSpace, UGREEN, TrimeMedia, or Navidrome server') plus operation terms like 'inspect', 'diagnose', 'search', 'resume state', and 'scans'; no generic filler.

5 / 5

Distinctiveness Conflict Risk

A clear niche — direct operation of seven named media-server products — with triggers tied to those specific products, so overlap with generic library or file skills is minimal; 'without adding permanent tools' further bounds the scope.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

jxxghp/MoviePilot

Path

skills/mediaserver-operation/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.