Rename multiple Google Drive files matching a pattern to follow a consistent naming convention.
74
63%
Does it follow best practices?
Impact
98%
2.13xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/recipe-batch-rename-files/SKILL.mdQuality
Discovery
40%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 identifies a specific, narrow capability (batch renaming Google Drive files) which makes it distinctive, but it lacks completeness by omitting explicit trigger guidance. The single action described and missing 'Use when...' clause significantly limit Claude's ability to confidently select this skill from a large pool.
Suggestions
Add a 'Use when...' clause with trigger terms like 'rename Drive files', 'batch rename', 'fix file names', 'standardize naming'
Expand the capability description to include related actions if applicable, such as 'preview changes before applying' or 'rename based on date, type, or custom patterns'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Drive) and a specific action (rename files matching a pattern), but only describes one action rather than multiple concrete capabilities. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Google Drive', 'rename', 'files', 'naming convention' which are relevant, but misses common variations like 'batch rename', 'bulk rename', 'file names', or 'Drive files'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Google Drive' + 'rename' + 'pattern' + 'naming convention' creates a clear, specific niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
87%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-crafted, concise skill that provides actionable commands for batch renaming files. The main weakness is that despite being titled 'Batch Rename,' it only shows how to rename a single file without addressing iteration over multiple files or error handling for batch operations.
Suggestions
Add guidance on iterating through multiple files from the list results (e.g., a loop pattern or note about processing each FILE_ID)
Include a validation/retry pattern for handling failures when renaming multiple files in sequence
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient - no unnecessary explanations, assumes Claude knows what Google Drive is and how CLI tools work. Every line serves a purpose. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready commands with concrete examples including query syntax, parameter formats, and JSON payloads. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (find → rename → verify), but for a batch operation there's no feedback loop for handling multiple files or error recovery if a rename fails mid-batch. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is appropriately structured with a clear prerequisite callout and well-organized steps. No need for external references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
6ed836c
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.