recipe-copy-sheet-for-new-month
Duplicate a Google Sheets template tab for a new month of tracking.
70
63%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/recipe-copy-sheet-for-new-month/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 clear, narrow task (duplicating a Google Sheets template tab for monthly tracking), which gives it good distinctiveness. However, it lacks a 'Use when...' clause, limiting Claude's ability to know when to select it, and it could benefit from additional trigger terms and synonyms users might naturally use.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create a new monthly tab, duplicate a template sheet, or set up a new month in Google Sheets.'
Include common keyword variations such as 'spreadsheet', 'copy tab', 'worksheet', 'monthly sheet', or 'new month tab' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names a specific domain (Google Sheets) and a concrete action (duplicate a template tab for a new month), but describes only a single action rather than listing multiple specific capabilities. | 2 / 3 |
Completeness | It answers 'what does this do' but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes natural keywords like 'Google Sheets', 'template tab', 'new month', and 'tracking', but misses common variations users might say such as 'copy tab', 'spreadsheet', 'monthly sheet', or 'duplicate worksheet'. | 2 / 3 |
Distinctiveness Conflict Risk | The description is quite specific to a narrow use case—duplicating a template tab in Google Sheets for monthly tracking—making it 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 concise, actionable skill that provides concrete CLI commands for a straightforward 3-step workflow. Its main weakness is the lack of explicit validation between steps and no mention of how to capture the new sheetId from step 2 for use in step 3, which is a critical data dependency that could cause failures.
Suggestions
Add a note after step 2 explaining that the response contains the new sheetId, which must be used in step 3's payload (replacing the placeholder 123).
Add a brief verification step after step 3, such as re-fetching spreadsheet details to confirm the new tab exists with the correct name.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what Google Sheets is or how APIs work. Every line serves a purpose, and the prerequisite is cleanly stated. | 3 / 3 |
Actionability | Provides fully concrete, copy-paste-ready CLI commands with specific flags, JSON payloads, and parameter structures. Claude can directly execute these commands with minimal adaptation (just replacing IDs). | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (get → copy → rename), but there are no validation checkpoints. Step 2 returns a new sheetId that must be used in step 3, but this dependency is not explicitly called out. There's no error handling or verification that the copy succeeded before renaming. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the structure is appropriate. The prerequisite skill reference is clearly signaled, and the content is well-organized with a clear header and numbered steps. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- googleworkspace/cli
- Commit
a3768d0
- 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.