CtrlK
BlogDocsLog inGet started
Tessl Logo

google-sheets-automation

Lightweight Google Sheets integration with standalone OAuth authentication. No MCP server required. Full read/write access.

54

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/google-sheets-automation/SKILL.md

The canonical home for this skill is google-sheets-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

76%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 highly actionable, well-organized command reference with copy-paste-ready invocations for the common Google Sheets operations. Its main weaknesses are the absence of validation/verification checkpoints around destructive and batch writes, and a vague boilerplate 'When to Use' closing line.

Suggestions

Add an explicit validation/verify step after write and batch operations (e.g. re-fetch the range with get-range to confirm the change landed, or show how to inspect the returned response for errors).

Replace the generic 'When to Use' paragraph with concrete trigger phrasing tied to the documented commands.

For batch-update, include an example of validating the request body before submission and handling the batch response for per-request failures.

DimensionReasoningScore

Conciseness

The body is a lean command reference with executable snippets and minimal preamble, but the closing 'When to Use' boilerplate ('Use this skill when tackling tasks related to its primary domain or functionality as described above') is vague filler, fitting 'Efficient; minor instances of over-explanation that could be trimmed'.

4 / 5

Actionability

Every operation ships as a concrete, copy-paste-ready invocation (e.g. `python scripts/sheets.py get-text SPREADSHEET_ID --format csv`, `update-range SPREADSHEET_ID "Sheet1!A1:B2" '[["Hello","World"]]'`) covering the common read/write cases, matching the top anchor.

5 / 5

Workflow Clarity

Setup is sequenced (login/status/logout) and read/write commands are grouped, but destructive and batch operations (clear-range, update-range, append-rows, batch-update) include no validation or verification step, so per the guideline workflow clarity is capped at 3.

3 / 5

Progressive Disclosure

No references/scripts/assets bundle files exist and the content is appropriately self-contained in well-labeled sections (First-Time Setup, Read Commands, Write Commands, Output Formats), matching 'Good structure; most content is appropriately placed'; minor gap is that the referenced scripts/auth.py and scripts/sheets.py are not present in the bundle.

4 / 5

Total

16

/

20

Passed

Description

48%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 identifies its Google Sheets niche and key technical differentiator (standalone OAuth, no MCP), but stays at a generic capability level and omits any explicit 'Use when...' trigger guidance. It is distinct enough to avoid most conflicts yet not as actionable or trigger-rich as the top anchors.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to read, write, search, or update Google Sheets / spreadsheets.'

Replace the generic 'Full read/write access' with a few concrete actions (get ranges, append rows, clear ranges, batch update) to lift specificity.

Include natural synonyms users say, such as 'spreadsheet' and '.gsheet', alongside 'Google Sheets'.

DimensionReasoningScore

Specificity

Names the domain ('Google Sheets integration') and a couple of generic capabilities ('standalone OAuth authentication', 'Full read/write access'), but these are abstract labels rather than concrete enumerated actions, matching the 'Names the domain but actions are minimal or generic' anchor.

2 / 5

Completeness

Clearly states what the skill does (Google Sheets integration with OAuth read/write access) but provides no 'Use when...' trigger clause, so per the guideline completeness is capped at 3 ('Has a clear what but when is missing or only weakly implied').

3 / 5

Trigger Term Quality

Includes the natural term 'Google Sheets' plus 'OAuth' and 'MCP server', but misses common synonyms and variations a user might say ('spreadsheet', 'spreadsheets', '.gsheet'), fitting 'Some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

The 'Google Sheets' + 'standalone OAuth authentication' + 'No MCP server required' framing carves a clear niche with only minor overlap risk against other Sheets-related skills, matching 'Mostly distinct; minor overlap risk with closely related skills'.

4 / 5

Total

12

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 17 missing

Warning

Total

14

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.