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

58%

Does it follow best practices?

Impact

95%

2.87x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/googlesheets-automation/SKILL.md

Quality

Discovery

67%

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 does a good job listing specific capabilities for Google Sheets automation and is clearly distinguishable from other skills due to the Google Sheets + Composio scoping. However, it lacks an explicit 'Use when...' clause which caps completeness, and the trigger terms could be broader to capture more natural user language. The technical reference to 'Rube MCP (Composio)' adds distinctiveness but doesn't help with user-facing trigger matching.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to read, write, update, or automate Google Sheets, or mentions spreadsheet operations, Google Sheets formatting, or managing sheet tabs.'

Include more natural user trigger terms such as 'cells', 'columns', 'Google spreadsheet', 'sheet data', and 'update spreadsheet' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: read, write, format, filter, manage spreadsheets, manage tabs, apply formatting, search rows. These are clear, actionable capabilities.	3 / 3
Completeness	Clearly answers 'what does this do' with specific operations, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the capabilities listed.	2 / 3
Trigger Term Quality	Includes good terms like 'Google Sheets', 'spreadsheets', 'read', 'write', 'format', 'filter', but misses common user variations like '.gsheet', 'cells', 'columns', 'rows', 'spreadsheet data', or 'Google Sheets API'. The mention of 'Rube MCP (Composio)' is technical jargon unlikely to be used by most users.	2 / 3
Distinctiveness Conflict Risk	Clearly scoped to Google Sheets specifically (not Excel or generic spreadsheets) and mentions the specific integration (Rube MCP/Composio), making it highly distinguishable from other spreadsheet or data skills.	3 / 3
	Total	10 / 12 Passed

Implementation

50%

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

This is a solid reference skill for Google Sheets automation via Rube MCP with good coverage of tools, parameters, and pitfalls. Its main weaknesses are the lack of executable call examples (showing actual MCP tool invocations with sample payloads), redundant pitfall documentation across sections, and missing explicit validation/verification steps in workflows involving writes or destructive operations. The content would benefit from being more concise by eliminating duplication and adding concrete invocation examples.

Suggestions

Add at least one concrete, copy-paste-ready MCP tool invocation example per core workflow (e.g., showing actual RUBE_SEARCH_TOOLS and GOOGLESHEETS_BATCH_GET calls with realistic parameters)

Consolidate pitfalls into a single section rather than repeating them per-workflow AND in a summary section — or keep only per-workflow pitfalls and remove the consolidated list

Add explicit validation checkpoints to write/delete workflows (e.g., 'Read back the updated range to confirm write succeeded' after BATCH_UPDATE, 'Verify row count before and after DELETE_DIMENSION')

Consider moving the quick reference table and detailed per-workflow parameter lists to a separate REFERENCE.md file to reduce the main skill's token footprint

Dimension	Reasoning	Score
Conciseness	The skill is fairly comprehensive but has some redundancy — pitfalls are repeated in both per-workflow sections and a consolidated 'Known Pitfalls' section. The quick reference table duplicates information already covered in workflows. However, it mostly avoids explaining concepts Claude already knows and stays focused on tool-specific details.	2 / 3
Actionability	The skill provides specific tool names, parameter names, and clear descriptions of what each does, but lacks executable code examples or copy-paste-ready tool invocation snippets. The guidance is concrete in terms of naming tools and parameters but stops short of showing actual MCP call examples with realistic payloads.	2 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with labeled steps (Prerequisite, Required, Optional, Alternative), but validation checkpoints are largely missing. For destructive operations like DELETE_DIMENSION, there's only a warning but no explicit verify-before-proceeding step. The 'read before writing' pattern is mentioned but not embedded as a mandatory validation step in write workflows.	2 / 3
Progressive Disclosure	The content is well-structured with clear sections and a useful quick reference table, but it's quite long (~200+ lines) with all content inline. The toolkit docs link is provided but there are no references to separate files for advanced topics, detailed examples, or edge cases that could reduce the main file's token footprint.	2 / 3
	Total	8 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: davepoon/buildwithclaude
Commit: 7cc63f3

Reviewed: about 4 hours 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.