gws-sheets-append
Google Sheets: Append a row to a spreadsheet.
67
60%
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-append/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, natural trigger term variations, and multiple capability details. It would be difficult for Claude to confidently select this skill over other Google Sheets-related skills in a large skill library.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to add, append, or insert a new row of data into a Google Sheets spreadsheet.'
Include natural trigger term variations such as 'add row', 'insert row', 'new entry', 'add data to spreadsheet', and 'gsheet'.
Clarify how this skill differs from other Google Sheets operations (read, update, delete) to reduce conflict risk with similar skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Sheets) and one specific action (append a row), but only describes a single capability rather than listing multiple concrete actions. | 2 / 3 |
Completeness | Describes what it does (append a row to a spreadsheet) but has no 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also minimal, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes 'Google Sheets', 'append', 'row', and 'spreadsheet' which are relevant keywords, but misses common variations like 'add row', 'insert row', 'new row', or 'gsheet'. | 2 / 3 |
Distinctiveness Conflict Risk | Specifying 'Google Sheets' and 'append a row' provides some distinctiveness, but could overlap with other Google Sheets skills (e.g., read, update, delete rows) since it doesn't clearly delineate its narrow scope versus broader spreadsheet manipulation skills. | 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 for a single-purpose CLI command. It excels at actionability with copy-paste-ready examples and a clear flag reference table. The main weakness is the lack of an explicit verification step after the write operation (e.g., checking the append succeeded or handling errors), which is important for destructive/write commands.
Suggestions
Add a verification step after the append command, such as checking the API response or reading back the appended row to confirm success.
Consider adding brief error handling guidance (e.g., what happens if the spreadsheet ID is invalid or the user lacks write permissions).
| 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, with a clear flag table, examples, and tips—nothing superfluous. | 3 / 3 |
Actionability | Provides fully executable CLI commands with concrete examples for both simple and bulk appends. The flag table gives all necessary details including which flags are required. | 3 / 3 |
Workflow Clarity | This is a write/destructive command and the caution box reminds to confirm with the user, but there's no explicit validation or verification step after the append (e.g., confirming the row was appended, checking for errors). For a write operation, the lack of a feedback loop caps this at 2. | 2 / 3 |
Progressive Disclosure | Clear prerequisite reference to shared auth skill, well-organized sections, and 'See Also' links to related skills—all one level deep and clearly signaled. Content is appropriately scoped for this single-purpose skill. | 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.