CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

transfer-failed-retry

Analyze failed MoviePilot transfers, verify media identity and season/episode, and safely replan durable recognition rejections while preserving task identity, execution evidence, and retry budgets.

68

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

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 an exemplary lean, safety-first procedural skill: a tightly numbered flow with explicit stop conditions, preview validation, and evidence-preservation rules, all within ~40 lines and no unnecessary explanation. The only minor gap is the absence of a concrete example request payload, which keeps actionability just below fully copy-paste-ready.

DimensionReasoningScore

Conciseness

The body is ~38 lines of purely operational instruction ("Inspect every exact requested history ID", "Stop for missing files... or exhausted retry budgets") with zero concept explanations or padding; every token earns its place, matching the lean anchor rather than the "minor over-explanation" of level 4.

5 / 5

Actionability

Guidance names exact operations and payload fields ("`transfer.history.replan` with the exact history ID, original `task_id` and `settlement_revision`... verified `media_source`, `media_id`, `media_type`") plus a concrete worked case ("`Season 2 - 03` requires verifying S02E03"), but exact request syntax is deferred to runtime schema discovery and no example request/response is shown — a minor gap keeping it below fully copy-paste-ready level 5.

4 / 5

Workflow Clarity

An explicitly numbered 8-step sequence embeds validation checkpoints and feedback loops for destructive operations: verify source with `storage.list`, "Inspect the preview before submitting any correction", and "Stop on a replan rejection and report the blocker" — meeting the top anchor's validation and error-recovery bar; this also satisfies the destructive-operation validation requirement, so no cap applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external reference files (none exist in the bundle), and is cleanly organized into a title, a one-line tooling note, and a single "Required Flow" section; per the guidelines a short skill with well-organized sections and no need for references scores 5.

5 / 5

Total

19

/

20

Passed

Description

75%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 specific, dense with concrete actions, and occupies a distinct niche, but it omits any explicit "Use when..." trigger guidance, which caps its completeness and limits natural trigger-term coverage. Adding a trigger clause with user-facing synonyms (e.g., re-identify, retry failed transfer) would raise it substantially.

Suggestions

Add an explicit trigger clause such as "Use when a MoviePilot transfer fails, media is misrecognized, or a recognition rejection needs a safe retry."

Include natural user-facing synonyms like "re-identify", "wrongly recognized media", or "retry failed transfers" to broaden trigger-term coverage.

Optionally mention the preview-before-submit safety check in the description so the safety-preserving nature of replanning is fully conveyed.

DimensionReasoningScore

Specificity

Quotes like "Analyze failed MoviePilot transfers", "verify media identity and season/episode", and "safely replan durable recognition rejections" list multiple concrete actions with comprehensive coverage of the skill's purpose, matching the top anchor; it is not the level below because no action is generic or minimal.

5 / 5

Completeness

The "what" is clearly and concretely answered (analyze, verify, replan, preserve evidence), but there is no "Use when..." clause or equivalent explicit trigger guidance; per the judging guidelines a missing trigger clause caps completeness at 3, and it is not a 2 because the "what" is specific rather than vague.

3 / 5

Trigger Term Quality

Terms such as "failed MoviePilot transfers", "media identity", "season/episode", and "retry budgets" give good natural keyword coverage, but common user variations like "re-identify", "wrongly recognized", or "retry failed transfer" are missing — above anchor 3 (which would require only some relevant keywords) but not fully comprehensive like anchor 5.

4 / 5

Distinctiveness Conflict Risk

"failed MoviePilot transfers" and "durable recognition rejections" define a clear niche with distinct triggers and minimal conflict risk with any other skill; nothing about it is broad or overlapping.

5 / 5

Total

17

/

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/transfer-failed-retry/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.