recipe-backup-sheet-as-csv
Export a Google Sheets spreadsheet as a CSV file for local backup or processing.
77
72%
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-backup-sheet-as-csv/SKILL.mdQuality
Discovery
57%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 is concise and clearly scoped to a specific task (exporting Google Sheets as CSV), which gives it good distinctiveness. However, it lacks an explicit 'Use when...' clause and only describes a single action, limiting its completeness and specificity scores. Adding trigger guidance and a few more natural user terms would strengthen it significantly.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to download, export, or convert a Google Sheets spreadsheet to CSV format.'
Include additional natural trigger terms users might say, such as 'download spreadsheet', 'convert to CSV', 'save as .csv', or 'Google Sheets to local file'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Sheets) and a specific action (export as CSV), but describes only a single action rather than listing multiple concrete capabilities. | 2 / 3 |
Completeness | Clearly answers 'what' (export Google Sheets as CSV for backup/processing) but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Google Sheets', 'CSV', 'export', 'backup', and 'processing', but misses common variations users might say such as 'download', 'convert', 'spreadsheet to csv', or '.csv file'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Google Sheets' and 'CSV export' is a clear, narrow niche that is unlikely to conflict with other skills. It is distinctly scoped to a specific platform and output format. | 3 / 3 |
Total | 9 / 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.
A concise, actionable skill that provides specific commands for exporting Google Sheets as CSV. The main weakness is the workflow clarity: step 3 is presented as an alternative rather than a sequential step, which could confuse the numbered list format, and there's no verification that the export was successful.
Suggestions
Separate the two approaches (Drive export vs Sheets read) into distinct subsections rather than mixing alternatives into a numbered sequence (e.g., '## Option A: Export via Drive' and '## Option B: Read values directly').
Add a brief verification step such as confirming the output file exists or checking its content, e.g., 'Verify: check that the exported CSV file is non-empty and contains expected headers.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. The prerequisite note is necessary context, and every line serves a purpose. No unnecessary explanations of what CSV is or how Google Sheets works. | 3 / 3 |
Actionability | Provides specific, copy-paste ready commands with concrete parameter syntax. Offers two alternative approaches (export via Drive vs read values directly), both with executable commands. | 3 / 3 |
Workflow Clarity | Steps are listed but the relationship between steps 2 and 3 is ambiguous—step 3 says 'Or' suggesting it's an alternative to step 2, but it's presented as a sequential step. There's no validation step to confirm the export succeeded or that the CSV content is correct. | 2 / 3 |
Progressive Disclosure | For this simple, single-purpose skill under 50 lines, the structure is appropriate. It references prerequisite skills clearly and the content is well-organized with a clear header and steps section. | 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.