googlesheets-automation

Automate Google Sheets operations (read, write, format, filter, manage spreadsheets) via Rube MCP (Composio). Read/write data, manage tabs, apply formatting, and search rows programmatically.

2.87x

Quality

70%

Does it follow best practices?

Impact

95%

2.87x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/googlesheets-automation/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 body is a well-organized, highly actionable reference for the Rube MCP Google Sheets toolkit: named tool sequences, precise parameters, and useful pitfalls. Its weaknesses are redundancy between per-workflow pitfalls and the 'Known Pitfalls' section, and missing validation/feedback loops around destructive and batch operations.

Suggestions

Remove the duplicated 'Known Pitfalls' section (or reduce it to a one-line pointer to per-workflow pitfalls) to cut repeated tokens.

Add an explicit validation step before destructive calls, e.g. read back the range with BATCH_GET before GOOGLESHEETS_DELETE_DIMENSION, forming a validate → act → verify loop.

Move the full parameter detail for less-common workflows (e.g., formatting, filters) into a references file to slim the main SKILL.md.

Dimension	Reasoning	Score
Conciseness	Mostly dense and reference-style with tool slugs, params, and pitfalls, but the 'Known Pitfalls' section repeats seven items (tab names, range quoting, unbounded ranges, 2D arrays, colors, formatting IDs, rate limits) already covered per-workflow, which could be consolidated.	3 / 5
Actionability	Concrete tool slugs, exact parameter names, A1 notation examples, and format specifics ('2D array', '0.0-1.0 floats', 'USER_ENTERED') give mostly executable guidance; minor gaps such as no example payloads keep it below fully copy-paste ready.	4 / 5
Workflow Clarity	Sequences are explicit with tagged prerequisites and some verification hints ('use returned updatedRange to verify placement', 'verify formatting via readback'), but destructive operations like DELETE_DIMENSION get only 'double-check bounds' with no validate-then-act loop, and batch workflows lack systematic validation checkpoints.	3 / 5
Progressive Disclosure	A single well-sectioned file with clear per-workflow organization, tagged roles, and a Quick Reference table for navigation; no nested references. The detailed tool reference bulk (~195 lines) could arguably live in a separate reference file, which keeps it below a 5.	4 / 5
	Total	14 / 20 Passed

Description

66%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 names the domain, the mechanism (Rube MCP/Composio), and a solid set of concrete operations, making it specific and reasonably distinct. Its main weakness is the absence of any 'when to use this' trigger guidance, which caps completeness, and slight redundancy that limits breadth of coverage.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions Google Sheets, spreadsheet data, or asks to read, write, filter, or format sheet data.'

Replace the redundant second sentence with uncovered capabilities (e.g., append/upsert rows, create spreadsheets) to broaden coverage.

Include common synonyms such as 'worksheet' or 'tabs' to strengthen natural trigger matching.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('read, write, format, filter, manage spreadsheets', 'manage tabs, apply formatting, and search rows'), but the second sentence partially repeats the first rather than broadening coverage, and append/upsert workflows are absent — minor gaps rather than comprehensive coverage.	4 / 5
Completeness	The 'what' is explicit and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3.	3 / 5
Trigger Term Quality	Good natural keywords users would say ('Google Sheets', 'spreadsheet', 'tabs', 'rows', 'format', 'filter'), but misses common synonyms like 'worksheet' or file extensions like '.gsheet'.	4 / 5
Distinctiveness Conflict Risk	'via Rube MCP (Composio)' plus Google Sheets scoping carves a clear niche with mostly distinct triggers, though the generic 'manage spreadsheets' phrasing leaves minor overlap risk with generic spreadsheet/Excel skills.	4 / 5
	Total	15 / 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: davepoon/buildwithclaude
Path: plugins/all-skills/skills/googlesheets-automation/SKILL.md
Commit: 10bfc43

Reviewed: 8 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.