gws-sheets-append

Google Sheets: Append a row to a spreadsheet.

Quality

66%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/gws-sheets-append/SKILL.md

Quality

Content

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, concise skill for a single-purpose CLI command. It provides all necessary information — flags, examples, tips, and safety warnings — without any bloat. The progressive disclosure is excellent with clear references to shared infrastructure and related skills.

Dimension	Reasoning	Score
Conciseness	Every section earns its place — flags table, examples, and tips are all necessary and tightly written. No unnecessary explanations of what spreadsheets are or how APIs work.	3 / 3
Actionability	Provides fully executable CLI commands with concrete examples covering single-row, multi-row, and specific-tab scenarios. The flags table gives all needed parameters with clear descriptions.	3 / 3
Workflow Clarity	This is a single-action command skill, so complex multi-step workflows aren't needed. The caution callout about confirming with the user before executing serves as an appropriate validation checkpoint for a write operation.	3 / 3
Progressive Disclosure	Clean structure with prerequisite reference to shared auth skill, well-organized sections, and clear 'See Also' links to related skills — all one level deep with no nesting.	3 / 3
	Total	12 / 12 Passed

Description

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 or to know the full scope of when it applies.

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', 'gsheet'.

Clarify scope boundaries to distinguish from other Google Sheets skills, e.g., 'Does not read, update, or delete existing rows.'

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, so this scores 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, format) since the scope is narrowly stated without clear boundary triggers.	2 / 3
	Total	7 / 12 Passed

Validation

90%

Warnings & errors only

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: 3 months ago

Table of Contents

Discovery Implementation Validation

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.