CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moviepilot-api

Use this skill for MoviePilot product operations such as media search, torrent search, downloads, subscriptions, library checks, sites, storage, workflows, schedulers, plugins, filter rules, and system settings. It authorizes the structured moviepilot_api gateway only; it does not authorize arbitrary HTTP, legacy Agent tools, MCP compatibility commands, authentication headers, or API tokens.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

The body is an exceptionally concrete routing and execution guide: executable JSON call shapes, exact field-placement and pagination rules, and a validated multi-step workflow with explicit error-recovery loops. Its weaknesses are length and drift — several sections cover host/WebAgent behavior and product meta-details rather than the API surface — and references to category files that could not be verified in the bundle.

Suggestions

Trim or relocate sections unrelated to the MoviePilot API surface — e.g., the WebAgent choice-callback/snapshot internals in "Agent Task And Conversation State" and the memory/skill tooling guidance in "Reusable learning" — to cut token cost without losing routing value.

Move route-inventory meta-details (widget Bearer semantics, image proxy maxWidth/quality contract, the app/agent/policy/api.py drift test) into the linked docs files and keep only the routing-relevant boundary statements inline.

Standardize reference locations (api/, docs/, root-level code-execution.md, ../../docs/mcp-api.md) under one consistent bundle layout and ship the referenced category files with the skill so every link resolves.

DimensionReasoningScore

Conciseness

The core routing and contract prose is dense with unique operational rules, but sections drift off-skill: "Agent Task And Conversation State" (WebAgent choice callbacks, snapshot replacement, idle workers), "Reusable learning" (memory tool guidance), and meta paragraphs like "The Web image proxy's maxWidth and quality parameters" and "The maintained route-by-route inventory is the fixed registry in app/agent/policy/api.py". That is more than the "minor instances of over-explanation" of the 4 anchor, though the text is never padded, so it stays above 2.

3 / 5

Actionability

Quotes: the executable call shapes {"operation_id":"media.search","path_params":{},"query":{"title":"The Wandering Earth","type":"media"},"body":{}} and {"operation_id":"subscription.execution.list","query":{"limit":10}}, the pagination recipe "send query={"page":1,"count":1} and read collection.total_count", and the verification-contracts table with exact path_params/query fields. Guidance is copy-paste ready and covers the common read/download cases, matching the 5 anchor.

5 / 5

Workflow Clarity

The "Overall Workflow" gives a 7-step sequence with explicit validation checkpoints and feedback loops: "Inspect success, execution_outcome, errors, empty results… before reporting", "An invalid_input response names the failing field… correct that field and all required fields before retrying", and "When a write returns unknown, never retry it; verify the actual state with a supported read operation first". Destructive/batch operations (storage.delete, transfer.history.redo_batch, database.backups.delete) are covered by these checkpoints and read-back verification, so the cap-at-3 rule does not apply.

5 / 5

Progressive Disclosure

Quotes: "Detailed operation contracts live in the linked category files under api/; load only the one category file needed" and the 22-row "API Category Index" table with namespaces and use-for descriptions — a well-signaled, one-level-deep reference design. However, none of the referenced files (api/<category>.md, docs/widgets.md, code-execution.md, ../../docs/mcp-api.md) exist in the reviewed bundle, and reference locations are inconsistent (api/, docs/, skill root, two levels up), which are minor organization gaps versus the fully verified split of the 5 anchor.

4 / 5

Total

17

/

20

Passed

Description

87%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.

A strong description: it names the product niche, lists a dozen concrete operation domains, provides an explicit "Use this skill for…" trigger clause, and delineates authorization boundaries that sharply reduce conflict risk. The main gaps are unmentioned natural trigger terms (music, subtitles, transfers, RSS) relative to the skill's actual API surface.

DimensionReasoningScore

Specificity

Quotes: "media search, torrent search, downloads, subscriptions, library checks, sites, storage, workflows, schedulers, plugins, filter rules, and system settings" plus "It authorizes the structured moviepilot_api gateway only". Twelve concrete operation domains and an explicit authorization boundary exceed the 1-2-action anchor at 3, but the domains are noun phrases rather than verb-led actions and omit parts of the actual surface (transfers, music, subtitles), so comprehensive coverage at 5 is not met.

4 / 5

Completeness

Quotes: "Use this skill for MoviePilot product operations such as media search, torrent search, downloads, subscriptions…" and "It authorizes the structured moviepilot_api gateway only…". The "Use this skill for…" clause explicitly answers when with concrete trigger phrases inline, and the domain list plus gateway boundary clearly answers what; the when is specific, so the 4 anchor ("when could be more explicit or specific") does not fit.

5 / 5

Trigger Term Quality

Quotes: "media search", "torrent search", "downloads", "subscriptions", "plugins", "system settings" — natural phrases users would say. Coverage is good but misses common variations and sibling terms (music, subtitles, transfer/organize, RSS), matching the 4 anchor "good keyword coverage; a few natural terms missing" rather than the synonym/extension completeness of 5.

4 / 5

Distinctiveness Conflict Risk

Quotes: "Use this skill for MoviePilot product operations" and "it does not authorize arbitrary HTTP, legacy Agent tools, MCP compatibility commands, authentication headers, or API tokens". A product-named niche with explicit exclusions of neighboring surfaces gives distinct triggers and minimal conflict risk, exceeding the 4 anchor's "minor overlap risk with closely related skills".

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 23 missing, 1 suspicious

Warning

Total

14

/

16

Passed

Repository

jxxghp/MoviePilot

Path

skills/moviepilot-api/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.