gws-sheets-read
Google Sheets: Read values from a spreadsheet.
72
66%
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/gws-sheets-read/SKILL.mdQuality
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 is very terse—it identifies the platform and a single action but lacks a 'Use when' clause, multiple concrete capabilities, and sufficient trigger terms. It would benefit significantly from expanded action coverage and explicit trigger guidance to help Claude distinguish this skill from others.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks to read, fetch, or retrieve data from a Google Sheets spreadsheet.'
List additional concrete actions if applicable (e.g., 'read cell values, retrieve ranges, fetch sheet metadata') to improve specificity.
Include natural keyword variations such as 'gsheet', 'Google spreadsheet', 'cell values', 'sheet data' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Sheets) and one action (read values from a spreadsheet), but only describes a single capability rather than listing multiple concrete actions. | 2 / 3 |
Completeness | Answers 'what' (read values from a spreadsheet) but completely lacks any 'Use when...' clause or explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also quite thin—so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes 'Google Sheets' and 'spreadsheet' which are natural terms users would say, but misses common variations like 'gsheet', 'cells', 'ranges', 'fetch data', or '.gsheet' file references. | 2 / 3 |
Distinctiveness Conflict Risk | Specifying 'Google Sheets' and 'read values' provides some distinction from generic spreadsheet or Excel skills, but could overlap with other Google Sheets skills that write or manipulate data, and the scope is not clearly delineated. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent, well-crafted simple skill. It is maximally concise, provides fully actionable CLI examples with a clear flag reference table, and appropriately delegates shared concerns (auth, global flags) to a referenced skill file. The read-only safety note and cross-references are well-placed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every token earns its place. No unnecessary explanations of what Google Sheets is or how APIs work. The content is lean, assumes Claude's competence, and focuses purely on usage specifics. | 3 / 3 |
Actionability | Provides exact CLI commands with flag descriptions, required/default columns, and concrete examples that are copy-paste ready. The flag table is specific and complete. | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose read-only skill with no multi-step process or destructive operations. The single action is unambiguous, and the read-only safety note is appropriately included. | 3 / 3 |
Progressive Disclosure | Clear prerequisite reference to shared auth skill, well-signaled 'See Also' links to related skills one level deep, and the content is appropriately scoped without inlining shared concerns. | 3 / 3 |
Total | 12 / 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.