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.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/transfer-failed-retry/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

A tight, highly operational skill body: an 8-step flow with explicit stop conditions, preview validation, rejection handling, and post-replan verification, plus a complete JSON payload example for the key operation. Its only weaknesses are mild constraint repetition and request shapes being shown for just the replan operation.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive with no explanations of concepts Claude already knows; the only trim opportunity is the repeated preservation constraints ("verified identity, original storage/mode/destination, season/episode" recurs in steps 4, 5, 7, and again in the replan-input section). Matches anchor 4 (efficient with minor instances that could be trimmed); not 5 because that repetition is a real, if small, redundancy.

4 / 5

Actionability

Gives concrete, executable guidance: "Preview with `transfer.file` and `preview=true`", replan with "the exact history ID, original `task_id` and `settlement_revision`", explicit payload placement ("将失败历史 ID 放在 `path_params.history_id`"), and a complete JSON example whose placeholder values are explicitly flagged as needing replacement. Matches anchor 4 — the replan call is copy-paste ready, but only that one operation gets a request shape while the rest are named only ("discover their current schemas").

4 / 5

Workflow Clarity

The 8-step Required Flow is explicitly sequenced with validation checkpoints at every risky point: stop conditions ("Stop for missing files, storage/permission/configuration faults, manual review, uncertain effects, or exhausted retry budgets"), pre-submit validation ("Inspect the preview before submitting any correction"), error recovery ("Stop on a replan rejection and report the blocker"), and post-action verification ("收到受理结果后,用 `transfer.history` 核实该条历史的最终状态"). The destructive-operation cap does not apply since validation is present; matches anchor 5.

5 / 5

Progressive Disclosure

No bundle files exist and none are needed: the ~64-line body is self-contained, organized into a clear Required Flow and a focused replan-input section with one small inline JSON example that does not warrant extraction. Matches the small-skill allowance — well-organized sections, no buried references, nothing that belongs in a separate file.

5 / 5

Total

18

/

20

Passed

Description

62%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.

A specific, distinctive, third-person description that clearly states what the skill does, but it completely lacks an explicit "Use when..." trigger clause and leans on internal jargon ("durable recognition rejections", "retry budgets") over natural user phrasings. The missing when-clause caps completeness and weakens trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when a MoviePilot transfer or recognition fails and the user asks to retry, retransfer, or fix the failed record."

Include natural user phrasings and synonyms — "failed transfer", "retry", "retransfer", "wrong episode/identification" — instead of only internal terms like "durable recognition rejections" and "retry budgets".

Briefly extend the action list to cover the secondary paths the skill handles (legacy history deletion and album retry) so specificity reaches comprehensive coverage.

DimensionReasoningScore

Specificity

Lists three concrete, domain-specific actions — "Analyze failed MoviePilot transfers", "verify media identity and season/episode", "safely replan durable recognition rejections" — plus preservation constraints. Closest to anchor 4: several specific actions with minor gaps (the legacy-deletion and album-retry paths are not covered), below anchor 5's comprehensive coverage but well above the 1-2 actions of anchor 3.

4 / 5

Completeness

The "what" is explicit and concrete, but there is no "Use when..." clause or equivalent trigger guidance — "when" is only weakly implied by "failed ... transfers", which per the judging guidelines caps completeness at 3. Not 4 because the when-clause is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

"failed MoviePilot transfers" and "season/episode" are relevant keywords, but common natural phrasings users would say ("retry", "retransfer", "redownload", "wrong episode") are missing, and terms like "durable recognition rejections" and "retry budgets" are internal jargon. Matches anchor 3 (some relevant keywords, missing variations); not 4 because several natural terms users actually say are absent.

3 / 5

Distinctiveness Conflict Risk

"failed MoviePilot transfers" pins a clear niche (MoviePilot transfer-failure recovery) with distinct triggers, and "durable recognition rejections" further narrows it — minimal overlap risk with any other skill. Matches anchor 5; anchor 4's "minor overlap risk" understates how specific this niche is.

5 / 5

Total

15

/

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.