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.

79

2.87x
Quality

71%

Does it follow best practices?

Impact

95%

2.87x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/googlesheets-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-structured, concise, and actionable, with strong progressive disclosure for a standalone skill. The main gap is the lack of explicit validation/feedback-loop checkpoints for batch and destructive operations, which caps workflow clarity at 3.

Suggestions

Add explicit validation checkpoints to batch and destructive workflows (e.g., 'read back the range after BATCH_UPDATE' and 'confirm bounds before DELETE_DIMENSION, since it is irreversible').

Reduce duplication between the per-workflow 'Pitfalls' subsections and the consolidated 'Known Pitfalls' section to tighten token efficiency.

Provide at least one fully copy-pasteable example tool call (with parameter JSON) for the highest-frequency workflow to lift actionability to 5.

DimensionReasoningScore

Conciseness

The body is mostly lean tool sequences, parameter lists, and pitfalls without explaining concepts Claude already knows; minor redundancy (pitfalls repeated across per-workflow and Known Pitfalls sections) keeps it just short of 5.

4 / 5

Actionability

Concrete tool slugs, exact parameter names, A1-notation examples, and a Quick Reference table give largely executable guidance, though it relies on tool calls rather than copy-paste code and a few parameter value examples are illustrative only.

4 / 5

Workflow Clarity

Each workflow lists a numbered tool sequence with [Required]/[Optional] tags, but batch/destructive operations (BATCH_UPDATE, UPSERT_ROWS, DELETE_DIMENSION) lack explicit validate-then-retry feedback loops, and the destructive-cap guidance caps this at 3.

3 / 5

Progressive Disclosure

For a single SKILL.md with no bundle files, the content is well-organized into clearly headed sections (Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, Quick Reference) with one-level structure and easy navigation, meeting the simple-skill exception.

5 / 5

Total

16

/

20

Passed

Description

71%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 is specific and well-scoped to Google Sheets via Rube MCP, with concrete enumerated actions. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness at 3.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user wants to automate Google Sheets tasks such as reading, writing, formatting, or filtering data.'

Add natural synonym keywords users say (e.g. 'Google Sheets', 'tabs', 'rows', 'spreadsheet automation') to improve trigger term coverage.

Keep third-person voice but fold a brief 'when' phrase into the same sentence to satisfy both 'what' and 'when' concisely.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'read, write, format, filter, manage spreadsheets' plus 'manage tabs, apply formatting, and search rows' — giving comprehensive coverage of the toolkit's capabilities.

5 / 5

Completeness

It clearly answers 'what' (the enumerated operations) but has no explicit 'Use when...' or 'when should Claude use it' trigger clause, which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Natural terms like 'spreadsheets', 'format', 'filter', and 'search rows' are present, but it lacks common synonyms or file-type cues (e.g., 'Google Sheets', 'tabs', 'rows') and a natural 'when the user mentions X' phrasing, so a few terms are missing.

4 / 5

Distinctiveness Conflict Risk

'Google Sheets operations ... via Rube MCP (Composio)' carves a clear niche distinct from generic spreadsheet skills, with only minor overlap risk against other productivity/spreadsheet skills.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.