Name: google-sheets
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

google-sheets

Google Sheets integration. Manage analytics data, records, and workflows. Use when the user wants to interact with Google Sheets data.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/google-sheets/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable Membrane CLI commands and a clear connect-state workflow, but it opens with unnecessary background, lacks validation for batch/destructive data operations, and inlines reference material that could be split out.

Suggestions

Remove or drastically shrink the opening paragraph defining Google Sheets; Claude already knows this, so start directly at the integration workflow.

Add a read-after-write verification step for batch and destructive actions (e.g. after batch-update-values or clear-values, run get-values to confirm the change) so the workflow clears the batch/destructive validation cap.

Consider moving the full clientAction state-machine detail and the proxy-flag reference table into a separate REFERENCES.md linked from the body, so the main skill stays a concise overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with executable commands and tables, but the opening paragraph explaining what Google Sheets is ("a web-based spreadsheet program... Think of it as Google's version of Microsoft Excel") is common knowledge Claude already has, which is explicitly penalized and pushes this to anchor 3 rather than the minor-trimming anchor 4.	3 / 5
Actionability	Copy-paste-ready commands cover the full flow (install, login, connection ensure, action list, action run with --input, request proxy) plus action and flag tables, fitting anchor 4; it falls short of anchor 5 because CONNECTION_ID and actionId placeholders are never bridged to concrete values and action input schemas are not shown.	4 / 5
Workflow Clarity	The connect step has a clear state-machine sequence with a poll-until-ready feedback loop, but the popular batch/destructive actions (clear-values, batch-update-values, append-values) ship with no read-after-write validation, which the rubric caps at 3 for batch/destructive operations.	3 / 5
Progressive Disclosure	No bundle files exist and the body is well-sectioned with clear headers, fitting anchor 4; it does not reach anchor 5 because reference material (the full clientAction state machine and the proxy-flag table) is inlined rather than split into one-level-deep reference files.	4 / 5
	Total	14 / 20 Passed

Description

62%Weight 40%Scale 1-5

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 clearly names the Google Sheets niche and includes an explicit Use-when trigger, but its action list is abstract rather than concrete and it lacks common trigger synonyms like "spreadsheets" or ".xlsx".

Suggestions

Replace the generic phrase "Manage analytics data, records, and workflows" with concrete spreadsheet actions, e.g. "Read and write cell ranges, append rows, create spreadsheets, copy sheets, and batch-update values."

Add natural trigger terms users actually say, such as "spreadsheets", "spreadsheet data", "cells", or ".xlsx", alongside "Google Sheets".

Tighten the Use-when clause to name concrete triggers, e.g. "Use when the user wants to read, write, or update Google Sheets data or spreadsheet ranges."

Dimension	Reasoning	Score
Specificity	Names the domain ("Google Sheets") and offers a few actions ("Manage analytics data, records, and workflows"), but the actions are abstract categories rather than concrete spreadsheet verbs like read/write cells or create sheets, matching anchor 3 and falling short of the several-specific-actions anchor 4.	3 / 5
Completeness	It states what the skill does ("Manage analytics data, records, and workflows") and an explicit "Use when the user wants to interact with Google Sheets data" trigger, satisfying both what and when; the when is somewhat generic, matching anchor 4 rather than the concrete-trigger-phrases anchor 5.	4 / 5
Trigger Term Quality	"Google Sheets" and "interact with Google Sheets data" are relevant keywords, but common variations users say ("spreadsheets", "spreadsheet", ".xlsx", "cells", "rows") are missing, fitting anchor 3 rather than the broader coverage of anchor 4.	3 / 5
Distinctiveness Conflict Risk	The "Google Sheets" niche is mostly distinct with minor overlap risk against a generic spreadsheets/analytics skill, fitting anchor 4; it does not reach anchor 5 because the broad "analytics data, records, and workflows" framing could overlap with analytics tools.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/google-sheets/SKILL.md
Commit: f484c82

Reviewed: 5 days 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.