file-management

Organize, back up, compress, split, and merge files/folders using rule-driven plans; use when you need safe previews, conflict handling, and verification before executing file operations.

Quality

67%

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

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Other/file-management/SKILL.md

Quality

Content

60%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 content is well-structured with real bundle references and strong safety/verification guidance, but it is held back by a redundant broken PowerShell snippet and split/merge CLI examples that do not match the actual bundled scripts.

Suggestions

Remove or fix the broken first filter block in Example 1 so only the working "Practical include filter" remains, eliminating the redundant padding.

Correct the split/merge commands to match the actual scripts (e.g., positional input and --part-size-mb 100 for split_file.py; positional directory and --output for merge_parts.py) and drop the "flags may vary" hedge.

Consolidate the scattered preview/verify guidance into one numbered workflow (build manifest → preview/-WhatIf → execute → verify counts/hashes → only then switch copy to move) to tighten workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining basic concepts, but Example 1 inlines a broken filter block ("($Include \| ForEach-Object { $_ }) -contains $_.Extension -eq $false" and the escaped "\$_\" regex) immediately followed by a redo labeled "Practical include filter", which is redundant padding that should be trimmed.	3 / 5
Actionability	PowerShell examples are concrete, but the headline split/merge commands do not match the bundled scripts (documented --input/--part-size 100MB/--input-dir vs. actual positional input, --part-size-mb, --output), and the skill hedges that "CLI flags may vary", so the copy-paste guidance for the bundled scripts is incomplete.	3 / 5
Workflow Clarity	Preview-first execution, -WhatIf dry-run, conflict handling (rename/skip, overwrite only on confirmation), and verification (counts/sizes, SHA256 manifests) provide a clear sequence with most validation checkpoints, though the workflow is spread across separate examples rather than one unified numbered loop.	4 / 5
Progressive Disclosure	Structure is good with clearly signaled one-level-deep references to references/rule-schema.md and scripts/split_file.py, merge_parts.py (all real files), and content is reasonably split; minor gaps remain since large PowerShell blocks are inlined and Implementation Details partially restates the examples.	4 / 5
	Total	14 / 20 Passed

Description

75%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, mostly third-person, and answers both what the skill does and when to use it. It loses points for the second-person "you need" phrasing and a "when" clause framed around features rather than user scenarios.

Suggestions

Rephrase "use when you need" to third person (e.g., "use when the user needs") to avoid the specificity penalty.

Make the trigger clause user-situation oriented (e.g., "use when reorganizing directories, creating repeatable backups, or packaging large files for transfer").

Add a couple of natural synonyms or extensions (e.g., "archive", ".zip") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description lists five concrete actions ("Organize, back up, compress, split, and merge files/folders") plus rule-driven plans, previews, conflict handling, and verification, which is comprehensive; reduced from 5 to 4 because "use when you need" is second person, which the rubric penalizes by one point on specificity.	4 / 5
Completeness	Both "what" (organize/back up/compress/split/merge) and "when" ("use when you need safe previews, conflict handling, and verification") are explicit, but the "when" clause describes feature conditions rather than concrete user situations, so it could be more specific.	4 / 5
Trigger Term Quality	Natural user-facing terms like "organize", "back up", "compress", "split", "merge", and "files/folders" are well covered, but no file extensions or common synonyms are included and "rule-driven plans" leans technical, so a few natural terms are missing.	4 / 5
Distinctiveness Conflict Risk	The combined scope of rule-driven organize/back up/compress/split/merge with safe previews is a fairly distinct niche, though the broad "file management" label carries minor overlap risk with general file-handling skills.	4 / 5
	Total	16 / 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: aipoch/medical-research-skills
Path: scientific-skills/Other/file-management/SKILL.md
Commit: 63c61d3

Reviewed: 6 hours 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.