CtrlK
BlogDocsLog inGet started
Tessl Logo

transfer-failed-retry

Use this skill when you need to retry failed video or music transfers/organizations. Given failed transfer history IDs, query the exact records, group by trustworthy movie/series/recording/album identity, delete only the old records being retried, then re-identify and re-organize through MoviePilot. This skill is automatically triggered when transfer failures occur and AI retry is enabled.

69

Quality

85%

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

82%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, actionable retry workflow with concrete tool calls, a failure-cause table, and both single-file and batch examples. It would improve by tightening the redundant Important Notes section and adding an explicit validation feedback loop for the destructive delete→re-transfer sequence.

Suggestions

Trim the "Important Notes" section to only items not already stated in the Workflow steps to remove redundancy and improve conciseness.

Add an explicit validation checkpoint after re-transfer (e.g. re-query the history to confirm the record is no longer 'failed') before declaring success, strengthening the feedback loop for this destructive/batch skill.

Consider splitting the two long worked-example blocks into a short reference file referenced one level deep, which would let the main workflow read more concisely.

DimensionReasoningScore

Conciseness

The body is largely efficient with concrete tool calls and assumes Claude's competence, but the "Important Notes" section restates rules already embedded in the workflow (delete old record first, skip if source gone, recognize before search), fitting anchor-4 rather than the fully lean anchor-5.

4 / 5

Actionability

Fully executable tool calls with parameters (e.g. transfer_file(file_path=..., media_source=..., media_id=..., media_type=...)) plus two complete worked examples (single-file and 4-episode batch) cover the common cases, matching the anchor-5 example.

5 / 5

Workflow Clarity

A clear 5-step sequence exists with checkpoints (the failure-analysis table that tells the agent to skip unfixable records, the batch stop-early rule, and Step 5's result verification), but there is no explicit validate→fix→retry feedback loop for the transfer itself, so it sits at anchor-4 rather than 5.

4 / 5

Progressive Disclosure

Content is a single self-contained SKILL.md with no bundle files, well-organized into clearly signaled sections and no nested references; it is well-placed but slightly longer than the under-50-line simple-skill exception, fitting anchor-4.

4 / 5

Total

17

/

20

Passed

Description

87%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 strong: it states concrete capabilities, an explicit trigger clause, and an auto-trigger condition, carving out a distinct niche. The main weakness is the second-person voice, which costs it a specificity point.

DimensionReasoningScore

Specificity

Names multiple concrete actions ("query the exact records", "group by trustworthy...identity", "delete only the old records being retried", "re-identify and re-organize through MoviePilot"), matching the anchor-5 example, but the second-person opening ("Use this skill when you need to…") triggers the voice penalty, reducing it by one to 4.

4 / 5

Completeness

Explicitly answers both what (query, group, delete, re-identify, re-organize) and when ("Use this skill when you need to retry…" and "automatically triggered when transfer failures occur and AI retry is enabled"), matching the anchor-5 example.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("retry failed video or music transfers", "transfer failures", "re-organize") but missing common synonyms and file-type markers a user might say, fitting the anchor-4 example better than the comprehensive anchor-5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (MoviePilot failed-transfer retry for video/music) with distinct triggers and minimal overlap with other skills, matching the anchor-5 example.

5 / 5

Total

18

/

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.

Validation15 / 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
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.