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.
95
95%
Does it follow best practices?
Impact
91%
1.75xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
89%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 skill description that clearly communicates its purpose and provides explicit trigger terms. Its main weakness is that the capability description could be more specific about what concrete actions it supports (e.g., regex-based replacement, in-place file editing, recursive directory replacement). The trigger terms are well-chosen and cover natural user language variations.
Suggestions
Expand the capability description with more specific actions, e.g., 'Performs regex-based find-and-replace across files, batch string substitution, and in-place file editing using sd.'
| 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'. The parenthetical 'simpler than sed' is comparative context rather than a concrete capability. | 2 / 3 |
Completeness | Clearly answers 'what' (modern find-and-replace using sd and batch replacement patterns) and 'when' (explicit 'Triggers on:' clause listing 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 functionality. | 3 / 3 |
Distinctiveness Conflict Risk | The focus on the specific tool 'sd', find-and-replace operations, and string replacement creates a clear niche. The mention of sd vs sed helps distinguish it from general text processing or editing skills. | 3 / 3 |
Total | 11 / 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 commands 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 is particularly efficient at conveying key differences.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It jumps straight into executable commands, uses tables for comparisons instead of prose, and doesn't explain concepts Claude already knows (like what regex is or what find-and-replace means). | 3 / 3 |
Actionability | All examples are concrete, copy-paste ready bash commands. The sd vs sed comparison table, common patterns, and batch workflow all provide fully executable commands with realistic use cases. | 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 reference to an advanced patterns file for deeper content. The skill itself stays concise while pointing to additional resources. | 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.
e437c3c
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.