CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

publish-moviepilot-plugin

Use this skill when the user asks to publish, upload, sync, pull, push, diff, or maintain a MoviePilot local plugin in a GitHub repository. Covers using the configured MoviePilot GitHub token, PLUGIN_LOCAL_REPO_PATHS local plugin repositories, package.json/package.v2.json/package.v3.json metadata, plugins/plugins.v2/plugins.v3 layouts, safe file exclusion, diff preview before publishing, incremental GitHub Contents API updates, and syncing local plugin changes back from GitHub. Includes asking whether to use an existing repository or create a new public repository when no target repository is available. Also use for Chinese requests mentioning 插件发布, 插件维护, 推送插件到 GitHub, 从 GitHub 拉取插件, 同步本地插件仓库, 增量发布插件, 插件仓库维护.

Quality

96%

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

92%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 a strong operational manual: executable commands, explicit safety validation with feedback loops, and appropriate delegation of mechanics to the bundled script. Its only real weakness is redundancy — the repo-creation and public-visibility guidance recurs across four-plus sections and could be consolidated into one authoritative statement.

DimensionReasoningScore

Conciseness

The body is dense and free of explanations of known concepts, but the repository-creation/public-default rule is repeated in Scope, Pre-Flight step 2, Safety Rules, the create-repo option, and Examples, and pull-conflict handling appears in both Safety Rules and Examples. This matches 'efficient; minor instances of over-explanation that could be trimmed' rather than the lean every-token-earns-its-place anchor.

4 / 5

Actionability

The Script section provides copy-paste-ready publish_plugin.py invocations for preview, push, pull, create-repo, and the v3 layout, followed by a complete flag list and explicit exclusion globs (.env, *.pem, node_modules/, etc.), plus named settings (GITHUB_TOKEN, REPO_GITHUB_TOKEN, PLUGIN_LOCAL_REPO_PATHS). This matches the fully-executable anchor with common cases covered.

5 / 5

Workflow Clarity

Pre-Flight gives a numbered decision sequence with explicit fallbacks, Safety Rules mandate 'Always run preview before push', non-fast-forward conflicts trigger a stop-and-re-preview feedback loop, invalid local package JSON halts pull before any write, and a Final Checklist closes the process. Despite destructive/batch operations, explicit validation and recovery loops match the top anchor.

5 / 5

Progressive Disclosure

Procedural rules stay inline while implementation detail is delegated one level deep to scripts/publish_plugin.py (verified present in the bundle, invoked via full command lines), and the Ground Truth section signals authoritative sources (app/adapters/external/market.py, app/runtime/config.py). Sections are clearly headed and easy to navigate, matching the well-signaled one-level-deep structure anchor.

5 / 5

Total

19

/

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 exemplary: it states explicit trigger guidance in both English and Chinese, enumerates concrete capabilities rather than abstractions, and carves out an unmistakable niche. Only a minor stylistic nit exists — 'incremental GitHub Contents API updates' slightly conflicts with the body's Git Data API push mechanism — but this does not weaken the trigger or coverage quality.

DimensionReasoningScore

Specificity

Quotes 'publish, upload, sync, pull, push, diff, or maintain a MoviePilot local plugin in a GitHub repository' plus 'safe file exclusion, diff preview before publishing, incremental GitHub Contents API updates' — multiple concrete actions covering the full publish/pull/maintain lifecycle, matching the comprehensive anchor. It is not 4 because no meaningful capability is left uncovered.

5 / 5

Completeness

Both 'what' ('Covers using the configured MoviePilot GitHub token… incremental GitHub Contents API updates') and 'when' ('Use this skill when the user asks to…' and 'Also use for Chinese requests mentioning…') are explicitly and concretely stated with trigger phrases, matching the top anchor; it is not 4 because the when-clause is fully explicit, not merely present.

5 / 5

Trigger Term Quality

Natural user verbs ('publish, upload, sync, pull, push, diff, maintain') are supplemented with synonyms and file names (package.json/package.v2.json/package.v3.json) and a full set of Chinese trigger phrases (插件发布, 推送插件到 GitHub, 从 GitHub 拉取插件, 同步本地插件仓库), matching the comprehensive synonym coverage anchor rather than the 'a few natural terms missing' anchor.

5 / 5

Distinctiveness Conflict Risk

The niche is sharply defined — publishing MoviePilot local plugins to GitHub with named settings like PLUGIN_LOCAL_REPO_PATHS and package.v3.json layouts — giving it distinct triggers and minimal overlap with adjacent skills (e.g., plugin creation), which matches the clear-niche anchor.

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/publish-moviepilot-plugin/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.