CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

google-sheets-automation

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

Quality

70%

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

65%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 command reference with copy-paste examples, but it pads out sections with concepts Claude already knows, omits verification steps for destructive operations, and references script files that are missing from the bundle. It reads as a solid API quick-reference that needs tightening and a validation checkpoint.

Suggestions

Drop the "A1 Notation Examples" section (or reduce it to the skill-specific forms) and replace the boilerplate "When to Use" section with real trigger guidance or remove it.

Add a verification step after writes, e.g. re-run `get-range SPREADSHEET_ID "Sheet1!A1:B2"` to confirm values landed, especially before/after destructive `clear-range` and `batch-update` calls.

Ship the referenced `scripts/auth.py` and `scripts/sheets.py` in the bundle's scripts/ directory (or note their external source) so the documented commands are actually executable.

DimensionReasoningScore

Conciseness

The command reference is lean, but the "A1 Notation Examples" section explains basics Claude already knows ("Sheet1!A1:B10 - Range A1 to B10 on Sheet1") and "When to Use" is boilerplate padding ("Use this skill when tackling tasks related to its primary domain or functionality as described above."). Two padded sections go beyond the 'minor instances' of anchor 4.

3 / 5

Actionability

Every command is copy-paste ready with realistic arguments and flags, e.g. `python scripts/sheets.py update-range SPREADSHEET_ID "Sheet1!A1:B2" '[["Hello","World"],["Foo","Bar"]]'` and `find "budget 2024" --limit 5`, fully matching the anchor for executable, example-covered guidance.

5 / 5

Workflow Clarity

The sequence is clear (login/status/logout setup, then read and write commands with auto-authentication), but destructive and batch operations ("clear-range", "batch-update") include no validation or verification steps, and the rubric caps this dimension at 3 for such operations.

3 / 5

Progressive Disclosure

The body is organized into clear sections of appropriate size, but it references `scripts/auth.py` and `scripts/sheets.py`, which are not present in the bundle (no scripts/ directory exists), leaving dangling references. Scored against the actual bundle structure, this fits the 'some structure but could be better organized' anchor rather than anchor 4's well-placed references.

3 / 5

Total

14

/

20

Passed

Description

65%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 concise, third-person, and clearly identifies its niche, but it lacks an explicit 'Use when' trigger clause and lists no concrete operations beyond generic read/write. Adding trigger conditions and enumerating the main operations would strengthen it.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to read, write, or update Google Sheets spreadsheets or mentions Sheets URLs."

Enumerate concrete capabilities in the description (e.g., update ranges, append rows, clear ranges, search spreadsheets) instead of the generic "Full read/write access".

Include the synonym "spreadsheet" so searches not phrased as "Google Sheets" also surface the skill.

DimensionReasoningScore

Specificity

The description names the domain ("Google Sheets integration") and a couple of concrete aspects ("standalone OAuth authentication", "Full read/write access"), matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It falls short of 4 because it never lists the specific operations the skill performs (update ranges, append rows, search spreadsheets).

3 / 5

Completeness

There is a clear "what" (Google Sheets integration with OAuth, full read/write) but no "Use when..." clause or equivalent explicit trigger guidance anywhere; the rubric explicitly caps this dimension at 3 in that case.

3 / 5

Trigger Term Quality

"Google Sheets" and "read/write" are natural phrases users would say, giving good keyword coverage, but common synonyms like "spreadsheet(s)" are missing, so it does not reach the comprehensive coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Google Sheets" names a specific product forming a clear niche, and "No MCP server required" explicitly distinguishes it from MCP-based Sheets integrations, so the conflict risk with other skills is minimal.

5 / 5

Total

15

/

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.

Validation — 14 / 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

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/google-sheets-automation/SKILL.md

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.