repomix-unmixer
Extracts files from repomix-packed repositories, restoring original directory structures from XML/Markdown/JSON formats. Activates when users need to unmix repomix files, extract packed repositories, restore file structures from repomix output, or reverse the repomix packing process.
82
75%
Does it follow best practices?
Impact
93%
1.43xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./repomix-unmixer/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines a specific niche (repomix file extraction), lists concrete capabilities including supported formats, and provides explicit activation triggers with multiple natural phrasings. It follows the third-person voice convention and is concise without unnecessary padding.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Extracts files from repomix-packed repositories', 'restoring original directory structures', and specifies the formats handled (XML/Markdown/JSON). These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (extracts files from repomix-packed repos, restoring directory structures from XML/Markdown/JSON) and 'when' (explicit 'Activates when...' clause with multiple trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'repomix', 'unmix', 'packed repositories', 'extract', 'restore file structures', 'repomix output', 'reverse the repomix packing process'. These cover multiple natural phrasings a user might use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — 'repomix' is a very specific tool/format, making this unlikely to conflict with general file extraction or repository management skills. The niche is clearly defined. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is highly actionable with clear, executable commands, but is severely over-padded for what amounts to a single-command operation. The content repeats the same basic command pattern across multiple sections (use cases, examples, best practices) and explains concepts Claude already understands (file permissions, encoding, directory creation). The skill would benefit greatly from aggressive trimming to ~40-50 lines with format details and troubleshooting moved to reference files.
Suggestions
Reduce the skill to its core: the command syntax, supported formats (brief list), the validation workflow, and the 'extract to temp first' principle — move troubleshooting and detailed format specs to reference files.
Remove the 'When to Use This Skill' section entirely (duplicates frontmatter description), the 'What the Script Does' section (obvious from context), and the 'Resources' section (which just re-describes referenced files).
Collapse the three nearly identical use cases into a single example with a note that the same command works for any repomix file.
Add explicit validation checkpoints to the core workflow — e.g., check exit code, verify file count matches expected, diff a sample file — rather than listing vague validation steps in a separate section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose for what is essentially a single-command skill. The 'What the Script Does' section explains obvious behavior, 'When to Use This Skill' restates the description, use cases are near-identical repetitions of the same command, and the troubleshooting section covers things Claude already knows (permissions, encoding, mkdir). The entire skill could be reduced to ~30 lines. | 1 / 3 |
Actionability | Provides fully executable bash commands with concrete paths and parameters. The primary command is copy-paste ready, examples are specific, and troubleshooting includes actionable solutions with real commands. | 3 / 3 |
Workflow Clarity | The validation workflow section lists steps but they are vague ('spot check content', 'run validation') without explicit validation commands or success/failure criteria. The 'Verify Before Overwriting' section is good practice but the core workflow lacks a feedback loop — there's no step to check extraction success before proceeding, and destructive operations (overwriting) don't have explicit checkpoints. | 2 / 3 |
Progressive Disclosure | References to external files (references/repomix-format.md, references/validation-workflow.md, scripts/unmix_repomix.py) are well-signaled and one level deep, which is good. However, no bundle files were provided to verify these exist, and the SKILL.md itself contains far too much inline content (troubleshooting, format details, use cases) that could be in reference files, making the main file bloated. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- daymade/claude-code-skills
- Commit
bbf87f3
- 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.