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

88%

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

77%Weight 40%Scale 1-3

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 executable commands and well-sequenced workflows that include validation checkpoints and error-recovery guidance. Its main weakness is token efficiency: the full endpoint catalog and some inferable prose are inlined in SKILL.md rather than split into a one-level reference file.

Suggestions

Move the Complete API Reference catalog into a references/ file (e.g. references/endpoints.md) and keep SKILL.md as an overview with a one-level pointer, recovering context budget while preserving discoverability.

Trim inferable prose such as the AniList proxy/fallback paragraph and the Radarr/Sonarr integration note to just the behavior a caller needs (proxy preference and auth caveats).

Consider adding a one-line validation note to destructive/batch workflow steps (e.g. confirm subscription absence before DELETE) to make existing checkpoints explicit for every destructive endpoint.

Dimension	Reasoning	Score
Conciseness	Mostly efficient factual reference, but the ~450-line endpoint catalog is inlined in SKILL.md rather than offloaded to a reference file, with occasional prose restating behavior Claude could infer (e.g. the AniList proxy paragraph, the Radarr/Sonarr integration note).	2 / 3
Actionability	Provides a concrete general syntax, copy-paste-ready executable examples, full per-endpoint param tables, and complete numbered workflow scripts that are directly runnable.	3 / 3
Workflow Clarity	Multi-step workflows are clearly numbered and include explicit validation checkpoints (e.g. "Check if already subscribed" and "Check if already in library" before "Add subscription"), with an error-handling table mapping HTTP codes to corrective actions.	3 / 3
Progressive Disclosure	The single bundle file (scripts/mp-api.py) is correctly referenced and sections are well organized, but the large endpoint catalog that should live in a separate reference file is inlined in SKILL.md, matching the anchor of inlined reference content.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 precise, third-person, and explicitly covers both what the skill does and when to use it, while clearly distinguishing it from the sibling `moviepilot-cli` skill. It avoids vague fluff and names concrete capability areas plus natural trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capability areas ("media search, downloads, subscriptions, library management, site management, system administration, plugins, workflows") grounded in a specific action ("call MoviePilot REST API endpoints directly with the bundled Python client").	3 / 3
Completeness	Explicitly answers both what (call REST API endpoints via bundled Python client) and when ("Use this skill when you need to call...", "use this skill when the user explicitly asks for HTTP API access"), with explicit trigger guidance.	3 / 3
Trigger Term Quality	Natural user-facing triggers are well covered ("REST API endpoints", "HTTP API access", "the user explicitly asks for HTTP API access", "an endpoint is not exposed as an MCP tool"); the soft "and more" is minor.	3 / 3
Distinctiveness Conflict Risk	Carves a clear niche (direct REST endpoints not exposed as MCP tools) and explicitly steers away from `moviepilot-cli`, stating when not to use it, so conflict risk is low.	3 / 3
	Total	12 / 12 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 (632 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: 1b065cc

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