repomix-safe-mixer
Safely package codebases with repomix by automatically detecting and removing hardcoded credentials before packing. Use when packaging code for distribution, creating reference packages, or when the user mentions security concerns about sharing code with repomix.
Install with Tessl CLI
npx tessl i github:daymade/claude-code-skills --skill repomix-safe-mixerOverall
score
87%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
85%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 a well-structured description that clearly communicates both the capability and usage triggers. The explicit 'Use when...' clause with multiple scenarios is a strength. The main weakness is limited trigger term coverage for security-related vocabulary that users commonly use.
Suggestions
Expand trigger terms to include common security vocabulary like 'secrets', 'API keys', 'tokens', 'sensitive data', or 'environment variables'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'package codebases with repomix', 'automatically detecting and removing hardcoded credentials', and 'packing'. Uses third person voice correctly. | 3 / 3 |
Completeness | Clearly answers both what ('Safely package codebases with repomix by automatically detecting and removing hardcoded credentials') and when ('Use when packaging code for distribution, creating reference packages, or when the user mentions security concerns about sharing code with repomix'). | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'repomix', 'packaging code', 'credentials', 'security concerns', but misses common variations users might say like 'secrets', 'API keys', 'tokens', 'sensitive data', or 'code sharing'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining repomix tool with credential detection/removal. The combination of 'repomix' and 'credentials/security' creates a distinct trigger profile unlikely to conflict with general code packaging or security scanning skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with clear workflows and good progressive disclosure. The main weakness is some verbosity - sections explaining post-exposure actions and false positives could be trimmed since Claude understands these concepts. The executable examples and validation-enforced workflow are particular strengths.
Suggestions
Trim the 'Post-Exposure Actions' section to a brief checklist - Claude knows incident response basics
Condense the 'Common False Positives' section since the tool handles these automatically; just mention --exclude for custom patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy - the overview repeats the description, and some sections like 'Common False Positives' and 'Post-Exposure Actions' explain concepts Claude likely knows. The examples are good but could be tighter. | 2 / 3 |
Actionability | Excellent actionability with fully executable bash commands, concrete code examples for replacing secrets, and copy-paste ready workflows. Every instruction has specific commands with real output examples. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows with explicit validation checkpoints. The 'Clean and Package' workflow shows scan → fix → verify → pack sequence. The tool itself enforces validation by blocking packaging when secrets are found. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from quick start to advanced options. References to external files (common_secrets.md, scripts) are one level deep and clearly signaled. Content is appropriately split between overview and detailed references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
88%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
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
- 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.