CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

organize-files

Use this skill when the user asks MoviePilot to identify and organize a local or downloaded video/music file, season folder, recording, album directory, or mixed folder that automatic transfer did not handle. If failed transfer history IDs are supplied, use transfer-failed-retry instead.

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 dense, token-efficient orchestration guide with concrete operation names, parameter placement, and response-state semantics, and the 8-step workflow has thorough validation gates appropriate for batch file transfers. Minor gaps: the manual-transfer request body shape is never exemplified, and the Chinese-only final section header slightly weakens scanability. No bundle files exist and none are needed at this size.

DimensionReasoningScore

Conciseness

Every sentence carries MoviePilot-specific operational content ('Retired file, recognition, transfer, and history tools are not available', per-operation parameter placement, per-item response-state semantics) with no explanation of concepts Claude already knows and no padding, matching 'every token earns its place'. Re-reading anchor 4, there are no trimmable over-explanations to demote it.

5 / 5

Actionability

Guidance names exact operations ('storage.list', 'media.recognize', 'transfer.file') with parameter locations ('with title/path in query', 'with path_params.media_id', 'the manual-transfer request in body') and concrete response fields, so it is mostly executable. It is not 5 because the manual-transfer request body and several payload shapes are never exemplified, and not 3 because every step specifies a concrete call and its arguments.

4 / 5

Workflow Clarity

The 8-step sequence has explicit validation checkpoints (duplicate check via 'library.exists', a confirmation gate before 'a state-changing transfer', album track-count consistency, per-item state inspection where 'only completed confirms execution and settlement') plus feedback loops and enumerated stop-and-report conditions, satisfying the batch/destructive validation requirement that matches the anchor-5 example.

5 / 5

Progressive Disclosure

Sections (Workflow, Structured Calls, stop conditions, recovery/history) are well organized and no external files are needed at ~60 lines, but the final section's header is Chinese-only ('整理恢复与历史上下文') which slightly weakens header-based navigation, and the body is just over the under-50-line threshold where organized sections alone would warrant a 5.

4 / 5

Total

18

/

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 explicitly states both what the skill does and when to use it, with six concrete input types, an automatic-transfer-missed condition, and an explicit routing rule that disambiguates the sibling transfer-failed-retry skill. Trigger terms are natural and domain-anchored, though a few common synonyms and file extensions are missing. A strong, well-scoped description overall.

DimensionReasoningScore

Specificity

'identify and organize a local or downloaded video/music file, season folder, recording, album directory, or mixed folder' names the domain with two concrete actions and a thorough enumeration of six input types plus the 'automatic transfer did not handle' boundary. It sits above anchor 3 (1-2 actions, not comprehensive) due to the enumeration, but below anchor 5 since only two action verbs are given.

4 / 5

Completeness

It explicitly answers both questions: the what ('identify and organize... video/music file, season folder, recording, album directory, or mixed folder') and the when ('Use this skill when the user asks MoviePilot to...'), with concrete trigger phrases and an explicit condition ('that automatic transfer did not handle'), matching the anchor-5 example structure. Anchor 4's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ('identify and organize', 'video/music file', 'season folder', 'recording', 'album directory', 'mixed folder'), giving good keyword coverage. It falls short of anchor 5's comprehensive synonym/extension coverage because common variations like 'sort', 'rename', 'transfer', or extensions (.mkv, .mp3) are missing.

4 / 5

Distinctiveness Conflict Risk

The description is anchored to a specific application (MoviePilot), a distinct niche (files automatic transfer did not handle), and explicitly disambiguates the closest sibling skill ('If failed transfer history IDs are supplied, use transfer-failed-retry instead'), giving a clear niche with minimal conflict risk per anchor 5.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

jxxghp/MoviePilot

Path

skills/organize-files/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.