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 involving Google Sheets template duplication for monthly tracking, which gives it strong distinctiveness. However, it lacks an explicit 'Use when...' clause and covers only a single action, limiting its completeness and specificity. Adding trigger guidance and a few more natural keyword variations would significantly improve skill selection accuracy.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to duplicate, copy, or create a new monthly tab in Google Sheets.'
Include common keyword variations users might say, such as 'copy tab', 'spreadsheet', 'monthly sheet', 'duplicate worksheet', or 'new month tab'.
Expand the capability description slightly to cover related actions, e.g., renaming the new tab with the month name or updating date references.
| 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 describes what the skill does but has no explicit 'Use when...' clause or equivalent trigger guidance, and per the rubric a missing 'Use when' clause caps completeness at 2—but the 'when' is so absent that it falls to 1 since the what is also quite narrow. | 1 / 3 |
Trigger Term Quality | Includes natural terms 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 very specific to a narrow task—duplicating a Google Sheets template tab for monthly tracking—making it highly 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 validation between steps—particularly capturing the new sheetId from step 2's response for use in step 3, and no verification that operations succeeded. Otherwise it's well-structured and token-efficient.
Suggestions
Add a note after step 2 to capture the returned sheetId from the copyTo response, since it's needed in step 3 (the hardcoded '123' is a placeholder that needs replacing).
Add a brief validation step or note after step 3 to verify the rename succeeded, e.g., re-fetching spreadsheet details to confirm the new tab 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 realistic JSON payloads for each step. The commands include specific parameter structures and field names that Claude can directly adapt. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (get → copy → rename), but there are no validation checkpoints. Step 2 produces a new sheetId needed in step 3, but there's no explicit instruction to capture that sheetId from the response. 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
c7c6646
- 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.