recipe-backup-sheet-as-csv
Export a Google Sheets spreadsheet as a CSV file for local backup or processing.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-backup-sheet-as-csv65
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%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 capability (exporting Google Sheets to CSV) but lacks the explicit trigger guidance needed for Claude to reliably select this skill. It's functional but incomplete—the absence of a 'Use when...' clause is a significant gap that would make skill selection unreliable in a multi-skill environment.
Suggestions
Add a 'Use when...' clause with explicit triggers like '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: 'download', 'convert to CSV', 'save as CSV', 'gsheet', '.csv file'
Consider expanding capabilities if applicable (e.g., 'Export single sheets or entire workbooks') to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Sheets) and a specific action (export as CSV), but only describes one action rather than multiple concrete capabilities. The purpose 'for local backup or processing' adds some context but doesn't expand the action set. | 2 / 3 |
Completeness | Describes what the skill does (export Google Sheets as CSV) but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no trigger guidance at all. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Google Sheets', 'spreadsheet', 'CSV', and 'export', but missing common variations users might say such as 'download', 'convert', '.csv', 'save locally', or 'gsheet'. | 2 / 3 |
Distinctiveness Conflict Risk | Reasonably specific to Google Sheets CSV export, but could overlap with general spreadsheet skills, file conversion skills, or Google Workspace skills. The narrow focus on export helps, but lack of explicit triggers weakens distinctiveness. | 2 / 3 |
Total | 7 / 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 immediately actionable commands for exporting Google Sheets to CSV. The main weakness is ambiguity in the workflow—it's unclear whether steps 2 and 3 are alternatives or sequential, and there's no error handling or validation guidance for common issues like permissions or empty sheets.
Suggestions
Clarify whether steps 2 and 3 are alternatives (use 'Option A' / 'Option B' formatting) or sequential steps
Add a brief note on verifying the export succeeded (e.g., checking file size or row count)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what Google Sheets or CSV files are. Every line serves a purpose with concrete commands. | 3 / 3 |
Actionability | Provides three concrete, copy-paste ready commands with clear parameter syntax. Users can immediately execute these commands with their own SHEET_ID. | 3 / 3 |
Workflow Clarity | Steps are numbered but the relationship between steps 2 and 3 is unclear (are they alternatives?). No validation step to confirm the export succeeded or handle errors like permission issues. | 2 / 3 |
Progressive Disclosure | For this simple, single-purpose skill under 50 lines, the structure is appropriate. Clear prerequisite callout and well-organized steps without unnecessary nesting. | 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 | |
- 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.