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

Transfer Failed Retry

Use structured moviepilot_api operations only; discover their current schemas.

Required Flow

  1. Inspect every exact requested history ID. Record source/storage, destination, mode, identity, season/episode, status, error, and durable task context. Treat unknown task ownership as durable, and never act on another record.
  2. Verify source availability with storage.list. Stop for missing files, storage/permission/configuration faults, manual review, uncertain effects, or exhausted retry budgets. Do not delete targets or change global rules.
  3. Analyze the filename and error. Verify identity with media.recognize or media.search, and check TV season/episode with media.detail or media.seasons. Do not reuse a wrong failed identification unchanged. Season 2 - 03 requires verifying S02E03 rather than assuming S01. Group only proven shared identities; verify each file's season/episode.
  4. Preview with transfer.file and preview=true using the original source, destination, mode, and verified identity and season/episode. Inspect the preview before submitting any correction.
  5. For durable records, use transfer.history.replan with the exact history ID, original task_id and settlement_revision from the supplied context, verified media_source, media_id, media_type (movie/tv), and optional season/episode. It accepts only failed planning rejections with no file effects. It preserves the task, original plan/step evidence, settlement receipts, source deduplication, and consumed retry budget.
  6. Stop on a replan rejection and report the blocker. Never use transfer.history.delete, ordinary redo, a new non-preview transfer.file, target cleanup, or evidence deletion to bypass a durable task's checks. Music and tasks with file-operation evidence require manual recovery.
  7. Only records explicitly marked legacy may call transfer.history.delete without deleting source/target files, then continue with transfer.file after the response confirms history deletion. Preserve verified identity, original storage/mode/destination, season/episode, and music entity fields. A verified complete album sharing one directory may be retried once as an album; an artist is never a transfer target.
  8. Report verified corrections, accepted/queued replans, confirmed transfer successes, and remaining blockers accurately. A queued replan is not a completed transfer. Never reset or remove failure/retry evidence.

重新规划输入

将失败历史 ID 放在 path_params.history_id,将原任务与结算版本放在 body。 media_source、media_id 和 media_type 必须使用同一次媒体查询核实的值, 预览与重新规划保留相同的身份及季集。media_type 使用 movie 或 tv。 重新规划会清空旧识别结果并按提交的来源原生标识直接查询。 收到受理结果后,用 transfer.history 核实该条历史的最终状态。

以下示例的历史 ID、任务标识、结算版本和媒体身份均须替换为本次查询的实际值。

{
  "operation_id": "transfer.history.replan",
  "path_params": {"history_id": 123},
  "body": {
    "task_id": "task-from-analysis-context",
    "settlement_revision": 1,
    "media_source": "themoviedb",
    "media_id": "117061",
    "media_type": "tv",
    "season": 2,
    "episode": 3
  }
}
Repository

jxxghp/MoviePilot

Path

skills/transfer-failed-retry/SKILL.md

Last updated
First committed

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.