Modern find-and-replace using sd (simpler than sed) and batch replacement patterns. Triggers on: sd, find replace, batch replace, sed replacement, string replacement, rename.
92
91%
Does it follow best practices?
Impact
91%
1.75xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
82%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 solid description that clearly communicates the tool and its purpose, with explicit trigger terms. Its main weaknesses are moderate specificity (could list more concrete actions like regex replacement, in-place file editing, piped input) and some overlap risk with the broad trigger term 'rename' which could conflict with file renaming skills.
Suggestions
Add more specific concrete actions like 'replace strings in files, perform regex substitutions, pipe-based text transformation' to improve specificity.
Consider removing or qualifying the 'rename' trigger term, as it could conflict with file-renaming skills — or clarify it as 'string rename in files'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (find-and-replace) and the tool (sd), and mentions batch replacement patterns, but doesn't list multiple concrete actions beyond 'find-and-replace' and 'batch replacement'. It could specify more actions like replacing in files, regex support, piped input, etc. | 2 / 3 |
Completeness | Clearly answers 'what' (modern find-and-replace using sd, batch replacement patterns) and 'when' (explicit 'Triggers on:' clause with specific trigger terms). The trigger guidance is explicit and actionable. | 3 / 3 |
Trigger Term Quality | Includes a good set of natural trigger terms: 'sd', 'find replace', 'batch replace', 'sed replacement', 'string replacement', 'rename'. These cover common variations a user would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Fairly distinct due to the specific tool name 'sd' and the sed comparison, but terms like 'find replace', 'string replacement', and 'rename' could overlap with text editor skills, refactoring skills, or file renaming skills. The 'rename' trigger in particular seems potentially conflicting. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that is concise, highly actionable, and well-structured. It provides executable examples throughout, includes a safe batch workflow with explicit validation steps, and appropriately defers advanced content to a reference file. The sd vs sed comparison table adds genuine value for tool selection.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and code blocks to convey information densely. No unnecessary explanations of concepts Claude already knows — it jumps straight to syntax and patterns. | 3 / 3 |
Actionability | All examples are concrete, executable bash commands that are copy-paste ready. The sd vs sed comparison table, common patterns, and batch workflow all provide specific, immediately usable commands. | 3 / 3 |
Workflow Clarity | The 'Safe Batch Workflow' section provides a clearly numbered 4-step sequence with explicit validation: listing affected files first, previewing replacements, applying, then verifying with both rg and git diff. This includes proper feedback loops for a destructive batch operation. | 3 / 3 |
Progressive Disclosure | Content is well-organized into logical sections (basics, comparison, patterns, workflow, special chars, tips) with a clear one-level-deep reference to `./references/advanced-patterns.md` for more detail. Appropriate for the skill's scope. | 3 / 3 |
Total | 12 / 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.
f772de4
Table of Contents
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.