gws-sheets
Google Sheets: Read and write spreadsheets.
59
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.
This description is too minimal to effectively guide skill selection. While it correctly identifies the platform (Google Sheets) and basic operations, it lacks specific capabilities, natural trigger terms, and crucially missing explicit 'when to use' guidance that would help Claude choose this skill appropriately.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Google Sheets', 'gsheet', 'spreadsheet data', 'cells', 'rows and columns'
Expand specific capabilities beyond 'read and write' to include actions like 'create formulas', 'format cells', 'filter data', 'create charts'
Differentiate from Excel by explicitly mentioning Google-specific features or file references like 'Google Drive spreadsheets' or 'online spreadsheets'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Sheets) and two actions (read and write), but lacks comprehensive detail about specific capabilities like formatting, formulas, data analysis, or chart creation. | 2 / 3 |
Completeness | Answers 'what' minimally (read and write spreadsheets) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Google Sheets' and 'spreadsheets' which are relevant keywords, but misses common variations like 'gsheet', 'sheets', 'Google spreadsheet', 'cells', 'rows', or 'columns'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Sheets' is specific enough to distinguish from generic document skills, but 'spreadsheets' could overlap with Excel-related skills without clearer differentiation. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
72%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-structured reference skill that efficiently documents the Google Sheets API wrapper. Its strengths are conciseness and progressive disclosure with clear navigation to related skills. The main weakness is limited actionability - adding 1-2 concrete examples of common operations would significantly improve usability.
Suggestions
Add 1-2 executable examples showing common operations (e.g., reading a range, creating a spreadsheet) with actual --params usage
Include a brief example showing the discovery workflow: gws schema -> building the command -> executing it
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only essential information: command syntax, helper commands table, API resources list, and discovery commands. No unnecessary explanations of what Google Sheets is or how APIs work. | 3 / 3 |
Actionability | Provides concrete command syntax and discovery commands, but lacks executable examples showing actual usage (e.g., creating a spreadsheet, reading values with specific parameters). The helper command references are useful but the main API methods lack copy-paste examples. | 2 / 3 |
Workflow Clarity | The discovery workflow (help -> schema -> build params) is implied but not explicitly sequenced. For a reference skill this is acceptable, but there's no validation guidance for operations like batchUpdate which could benefit from error handling steps. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear references to prerequisite shared skill, helper commands linked to separate files, and a logical organization from basic syntax to discovery commands. One-level-deep references are well-signaled. | 3 / 3 |
Total | 10 / 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.