CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

71

2.87x
Quality

58%

Does it follow best practices?

Impact

95%

2.87x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

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

Quality

Content

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 that covers Google Sheets operations comprehensively with good structure and specific tool/parameter documentation. Its main weaknesses are the lack of concrete executable examples (actual MCP call payloads), missing validation/verification steps in workflows, and some content redundancy between per-workflow pitfalls and the consolidated Known Pitfalls section.

Suggestions

Add at least one concrete, complete MCP call example per core workflow showing actual input parameters and expected response structure (e.g., a full RUBE tool invocation with sample spreadsheet_id, ranges, and values).

Add explicit validation/verification steps to workflows — e.g., after BATCH_UPDATE, read back with BATCH_GET to confirm; before DELETE_DIMENSION, read the range to verify what will be deleted.

Remove the duplicated 'Known Pitfalls' summary section and keep pitfalls only under their respective workflows to reduce redundancy and token usage.

Consider splitting the Quick Reference table into a separate REFERENCE.md file to keep the main SKILL.md focused on workflows and reduce its length.

DimensionReasoningScore

Conciseness

The skill is fairly comprehensive but includes some redundancy — the 'Known Pitfalls' section largely repeats pitfalls already listed under each workflow, and the quick reference table duplicates tool names and params already covered. Some sections could be tightened, but it doesn't over-explain concepts Claude already knows.

2 / 3

Actionability

The skill provides specific tool names, parameter names, and clear sequences, which is good. However, it lacks concrete executable examples — no actual MCP call examples with sample payloads or responses are shown. The guidance is specific but not copy-paste ready; it describes what to pass rather than showing complete invocations.

2 / 3

Workflow Clarity

Multi-step workflows are clearly sequenced with labeled steps (Prerequisite, Required, Optional, Alternative), which is helpful. However, there are no explicit validation checkpoints or feedback loops — for example, after writing data there's no 'read back to verify' step, and the destructive DELETE_DIMENSION operation only gets a brief mention in Known Pitfalls rather than a proper validation workflow.

2 / 3

Progressive Disclosure

The content is well-structured with clear sections and a useful quick reference table. However, at ~180 lines it's a monolithic file with no bundle files to offload detailed content. The pitfalls are duplicated inline and in a summary section, and the quick reference table could potentially be a separate file. The external link to Composio docs is helpful but the skill itself could benefit from splitting detailed workflow content.

2 / 3

Total

8

/

12

Passed

Description

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. However, it lacks an explicit 'Use when...' clause which caps completeness, and some of the language (e.g., 'Rube MCP (Composio)', 'programmatically') is more technical than what users would naturally say.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to read, update, or manage Google Sheets, or mentions spreadsheet automation, Google Sheets formatting, or tab management.'

Replace technical jargon like 'Rube MCP (Composio)' and 'programmatically' with user-facing language, or move implementation details out of the description to focus on user-facing trigger terms.

DimensionReasoningScore

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 users.

2 / 3

Distinctiveness Conflict Risk

Clearly scoped to Google Sheets specifically (not Excel, not generic spreadsheets), and the mention of Rube MCP (Composio) as the integration method further distinguishes it. Unlikely to conflict with other spreadsheet skills.

3 / 3

Total

10

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
davepoon/buildwithclaude
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.