transfer-failed-retry

Use this skill for failed MoviePilot video or music transfer history IDs. Inspect the exact records, preserve durable retry evidence, group only records with a trustworthy shared identity, and re-identify/reorganize only legacy records that were actually deleted.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%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 tightly written, fully actionable workflow for a destructive/batch operation, with explicit validation checkpoints and feedback loops at every risky decision point and no padding. It is an exemplar of concise, well-structured instruction-only skill content.

Dimension	Reasoning	Score
Conciseness	The body is lean and padded-free: it assumes Claude's competence, defines no extraneous concepts, and every line is an actionable instruction or constraint that earns its place.	5 / 5
Actionability	Although codeless (appropriate for an API-orchestration skill), it names exact operations and parameters (transfer.history with status=failed, transfer.history.delete, media.recognize with source path, media.search with filename/tag facts, transfer.file with original source/storage/mode) plus concrete branching rules covering missing-source, durable-accepted, durable-rejected, and legacy-deleted cases.	5 / 5
Workflow Clarity	The eight-step flow is clearly sequenced with explicit validation gates and feedback loops (precheck source existence -> stop; delete result -> durable final vs legacy deleted; recognize absent/unreliable -> fall back to search; 'Only when the response confirms ... may you continue'), so the destructive/batch cap does not apply.	5 / 5
Progressive Disclosure	Under 50 lines, single-purpose, with no bundle files and no external references needed; it is well organized into a title, a numbered 'Required Flow' section, and a closing constraints paragraph, meeting the simple-skill exception for a top score.	5 / 5
	Total	20 / 20 Passed

Description

78%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, distinctive, and includes an explicit trigger clause, but its phrasing is more a list of constraints than natural user language, capping trigger-term quality and completeness at 4. It is well above baseline but short of the most user-friendly exemplars.

Suggestions

Reword constraint phrasing into natural trigger phrases a user would say, e.g. 'Retry failed MoviePilot video/music transfers' and 'Re-transfer or re-recognize deleted history records'.

Add one or two common synonyms/extensions (e.g. 'retransfer', 're-recognize media') to broaden natural keyword coverage.

Consider enumerating multiple trigger conditions (e.g. 'Use when the user reports failed transfer history IDs, asks to retry failed MoviePilot transfers, or wants to re-identify deleted records') to reach the explicit-when exemplar.

Dimension	Reasoning	Score
Specificity	Names the MoviePilot transfer-history domain and four concrete actions ('Inspect the exact records', 'preserve durable retry evidence', 'group only records with a trustworthy shared identity', 're-identify/reorganize only legacy records that were actually deleted'), but the framing is constraint-heavy rather than a clean capability list, leaving minor coverage gaps relative to the comprehensive 5-anchor.	4 / 5
Completeness	It has an explicit 'Use this skill for...' trigger clause answering when, plus a concrete action list answering what, but the 'when' gives a single trigger condition rather than the multiple natural variations shown in the 5-anchor, so it sits above 3 but below 5.	4 / 5
Trigger Term Quality	Natural user-facing terms appear ('failed MoviePilot ... transfer history IDs', 'video or music transfer', 'retry'), but the rest leans technical/constraint phrasing ('durable retry evidence', 'trustworthy shared identity') that users would not naturally utter, and common synonyms like 'retransfer' are missing.	4 / 5
Distinctiveness Conflict Risk	A clear, narrow niche (failed MoviePilot transfer-history retry with durable-evidence and grouping constraints) with distinct triggers and minimal overlap risk, matching the 5-anchor better than the broader 4-anchor.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Commit: 4f716c4

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