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

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/moviepilot-api/SKILL.md

Quality

Content

63%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 well-structured routing and execution guide with concrete calling contracts and strong validation/feedback guidance, weakened by duplicated workflow sections and a progressive-disclosure design whose referenced category files are missing from the bundle.

Suggestions

Ship the 21 referenced api/<category>.md files (or remove the read_skill file-loading step and inline the per-operation contracts) so the progressive-disclosure targets are not dead links.

Merge 'Overall Workflow' and 'Operation Order And Failure Handling' into a single non-redundant checklist to remove the duplicated guidance on operation selection, media_source/media_id preservation, side-effect confirmation, and success=false handling.

Trim the 'API Surface Scope' route-ownership/audit-drift paragraph to the one sentence Claude needs to know (non-listed routes are unavailable), moving the maintenance rationale to the audit doc it already references.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's competence (no basic-concept padding), but 'Overall Workflow' (7 steps) and 'Operation Order And Failure Handling' (5 steps) restate the same guidance, and the 'API Surface Scope' ownership/audit paragraph is maintenance-policy context that could be trimmed.	3 / 5
Actionability	Provides a concrete gateway-call JSON example and a 'Common read and download contracts' table with exact operation_ids and query params, plus explicit path_params/query/body placement rules; minor gaps remain since the per-operation contracts are deferred to category files.	4 / 5
Workflow Clarity	Clear numbered sequence with explicit validation checkpoints (inspect success/execution_outcome/errors; verify writes via read-back) and feedback loops ('never retry an unknown write; verify actual state first'), though it is split across two redundant sections rather than one clean checklist.	4 / 5
Progressive Disclosure	The category index is well-signaled and one-level-deep by design, but all 21 referenced api/<category>.md files are absent from the bundle (no api/, references/, scripts/, or assets/ directories exist), so the disclosure targets are dead links and the detail content is unreachable.	3 / 5
	Total	14 / 20 Passed

Description

78%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, product-specific description that clearly scopes what the skill authorizes and draws explicit boundaries against competing tools. It is comprehensive and distinctive, with only minor room to sharpen trigger phrasing and convert domain categories into more concrete actions.

Dimension	Reasoning	Score
Specificity	Enumerates many concrete capabilities ('media search, torrent search, downloads, subscriptions, library checks, sites, storage, workflows, schedulers, plugins, filter rules, and system settings') but these are domain categories rather than granular verb-actions, leaving minor gaps versus the comprehensive-anchor example.	4 / 5
Completeness	Answers both 'what' (the enumerated MoviePilot operations) and 'when' via the explicit 'Use this skill for MoviePilot product operations such as...' trigger; the 'when' could be more concrete with specific user-trigger phrases rather than a single generic clause.	4 / 5
Trigger Term Quality	Good coverage of MoviePilot's native feature vocabulary ('media search', 'torrent search', 'downloads', 'subscriptions', 'library checks') that a user of the product would naturally say, though a few common phrasings and synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	Clearly niched to MoviePilot with explicit boundary clauses ('authorizes the structured moviepilot_api gateway only; it does not authorize arbitrary HTTP, legacy Agent tools, MCP compatibility commands, authentication headers, or API tokens'), giving minimal conflict risk.	5 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 21 missing	Warning

	Total	14 / 16 Passed

Repository: jxxghp/MoviePilot
Path: skills/moviepilot-api/SKILL.md
Commit: 4f716c4

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.