gws-sheets-append
Google Sheets: Append a row to a spreadsheet.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill gws-sheets-append70
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 minimal and functional but incomplete. It clearly identifies the tool (Google Sheets) and a specific action (append a row), but lacks explicit trigger guidance and comprehensive keyword coverage. The absence of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill over others.
Suggestions
Add a 'Use when...' clause with trigger terms like 'add row to Google Sheets', 'insert data into spreadsheet', 'append to gsheet'
Include common keyword variations users might say: 'add row', 'insert row', 'gsheet', 'Google spreadsheet', 'add data'
Consider expanding capabilities if the skill does more than just appending rows, or clarify the specific use case more precisely
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Sheets) and one specific action (append a row), but only describes a single capability rather than multiple concrete actions. | 2 / 3 |
Completeness | Describes what it does (append a row) but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Google Sheets', 'append', 'row', and 'spreadsheet' which are relevant keywords, but missing common variations like 'add row', 'insert data', 'gsheet', or '.gsheet'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'Google Sheets' and 'append a row' specificity helps distinguish it from general spreadsheet skills, but could overlap with other Google Sheets skills that handle row operations or data entry. | 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 a well-crafted skill that exemplifies good documentation practices. It's concise, provides executable examples for both simple and bulk operations, includes appropriate safety warnings for write operations, and properly references shared context without duplicating it. The structure is clean and navigable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what Google Sheets is or how APIs work. Every line serves a purpose - flags, examples, and tips are all actionable. | 3 / 3 |
Actionability | Provides copy-paste ready bash commands with clear flag documentation. Both simple (--values) and complex (--json-values) use cases have concrete, executable examples. | 3 / 3 |
Workflow Clarity | For a single-action skill (append row), the workflow is unambiguous. Includes appropriate caution about write operations requiring user confirmation, which serves as a validation checkpoint. | 3 / 3 |
Progressive Disclosure | Excellent structure with prerequisite reference to shared auth/flags, clear 'See Also' section pointing to related skills one level deep, and appropriately scoped content for this specific command. | 3 / 3 |
Total | 12 / 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.