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.

56

Quality

64%

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-claude/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 content is a strong, highly actionable command reference with concise organization, but it provides no validation or feedback loops for its destructive and batch write operations, which the rubric caps at workflow_clarity 3.

Suggestions

Add explicit validation/verification checkpoints for write operations (e.g. re-read the range after update/clear, confirm append landed at the expected row) with a fix-and-retry loop on failure.

Bundle the referenced scripts/ (auth.py, sheets.py) or note their absence so the documented commands are actually executable from the skill.

Trim the repeated description line at the top of the body to tighten conciseness toward a 5.

DimensionReasoningScore

Conciseness

The body is mostly an efficient command reference with no padding of concepts Claude already knows; only minor trimmable bits like the repeated intro line and illustrative output-format blocks keep it from a 5.

4 / 5

Actionability

Every operation ships a concrete, copy-paste-ready bash command with realistic arguments and flags, covering the common read/write cases fully.

5 / 5

Workflow Clarity

Commands are grouped into a clear Setup/Read/Write sequence, but the write/batch/clear operations have no validation or verification checkpoints; the rubric's destructive/batch cap therefore limits workflow_clarity to 3.

3 / 5

Progressive Disclosure

A single well-organized SKILL.md with clear sections and no nested references; not a 5 because the documented scripts are not actually bundled and there is no reference-file organization to score against.

4 / 5

Total

16

/

20

Passed

Description

53%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 clear and reasonably distinct, naming the Google Sheets domain and its standalone-OAuth differentiator, but it lacks explicit 'when to use' trigger guidance and enumerates capabilities abstractly rather than as concrete actions.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when reading, writing, or searching Google Sheets data, or when the user mentions Sheets/spreadsheets.'

Replace the generic 'Full read/write access' with 2-3 concrete actions (e.g. 'read and export ranges, append rows, update cells, search spreadsheets') to lift specificity.

Add natural synonyms/file-extensions (spreadsheets, Sheets, A1 ranges) to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Google Sheets integration') and a couple concrete aspects ('standalone OAuth authentication', 'Full read/write access'), but does not enumerate specific actions like update cells, append rows, or search, so coverage is not comprehensive.

3 / 5

Completeness

Has a clear 'what' but no 'Use when...' trigger clause; per the rubric a missing explicit trigger guidance caps completeness at 3.

3 / 5

Trigger Term Quality

'Google Sheets' is a natural user phrase, but 'OAuth authentication' and 'MCP server' are technical jargon and common synonyms like 'spreadsheets', 'Sheets', or range/cell terms are missing.

3 / 5

Distinctiveness Conflict Risk

'Google Sheets' names a specific service and 'No MCP server required' explicitly distinguishes it from MCP-based Sheets skills, giving it a clear niche with only minor overlap risk.

4 / 5

Total

13

/

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.