moviepilot-api

Use this skill when you need to call MoviePilot REST API endpoints directly with the bundled Python client. Covers MoviePilot HTTP endpoints across media search, downloads, subscriptions, library management, site management, system administration, plugins, workflows, and more. Prefer `moviepilot-cli` for normal local MCP tool workflows; use this skill when the user explicitly asks for HTTP API access, when an endpoint is not exposed as an MCP tool, or when running in an environment where direct REST calls are the appropriate bridge.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

71%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 highly actionable with concrete executable commands and well-sequenced workflows including validation checkpoints. Its main weakness is length: a very large endpoint reference is inlined rather than progressively disclosed into a separate bundled file, hurting both conciseness and progressive-disclosure.

Suggestions

Move the bulk "Complete API Reference" endpoint tables into a bundled reference file (e.g. references/api-reference.md) and keep SKILL.md as an overview with a one-level-deep pointer, improving both conciseness and progressive_disclosure.

Add explicit validation/confirmation checkpoints to destructive and batch workflows (e.g. DELETE download/subscribe, clear transfer history) — a "confirm before deleting" step — to lift workflow_clarity to 5.

Trim or relocate the per-endpoint parameter prose where it duplicates what /api/v1/openapi.json already exposes, keeping only MoviePilot-specific semantics (media_source/media_id contract, 2-suffix token auth, SSE batching) inline.

Dimension	Reasoning	Score
Conciseness	Per-token prose is efficient and assumes Claude's competence (no basic-concept padding), but the ~600-line inline endpoint reference makes the body very long; the reference bulk could be tightened or split out.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands ("python scripts/mp-api.py GET /api/v1/media/search title=... type=...", real JSON bodies, --token-param usage) and five complete worked workflows covering the common cases.	5 / 5
Workflow Clarity	Workflows are numbered and sequenced with validation checkpoints (check-already-subscribed, check-in-library, requires_confirmation) and an HTTP-status error-recovery table, though pure DELETE/clear workflows lack explicit pre-destruction confirmation steps.	4 / 5
Progressive Disclosure	Section structure (## / per-domain ###) is clearly signaled and the sole bundle file scripts/mp-api.py is referenced correctly, but the dominant endpoint reference is inlined monolithically in SKILL.md rather than offloaded to a bundled reference file.	3 / 5
	Total	15 / 20 Passed

Description

92%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, concrete description that states a clear capability, enumerates comprehensive API coverage, and gives explicit "when to use" triggers with active disambiguation from neighboring skills. The only minor gap is a few missing natural phrasings users might say.

Dimension	Reasoning	Score
Specificity	Names the concrete action ("call MoviePilot REST API endpoints directly with the bundled Python client") and enumerates comprehensive coverage domains (media search, downloads, subscriptions, library management, site management, system administration, plugins, workflows) with no notable coverage gap.	5 / 5
Completeness	Explicitly answers both "what" (call REST endpoints directly via the bundled client; covers the listed domains) and "when" ("Use this skill when... explicitly asks for HTTP API access, when an endpoint is not exposed as an MCP tool, or... direct REST calls are the appropriate bridge") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ("HTTP API access", "endpoint is not exposed as an MCP tool", "direct REST calls") with good coverage, but a few common variants (e.g. "hit the API", "API request") are absent.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche (direct HTTP/REST endpoint access) and explicitly disambiguates from sibling skills ("Prefer moviepilot-cli for normal local MCP tool workflows"), minimizing wrong-skill triggers.	5 / 5
	Total	19 / 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
skill_md_line_count	SKILL.md is long (739 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

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

Reviewed: 4 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.