CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

google-drive-sheets

Find, read, export, edit, and manage the user's Google Drive, Docs, Sheets, and Slides through their own Google connection.

Quality

76%

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 ./skills-seed/google-drive-sheets/SKILL.md
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.

This is a highly actionable, token-efficient API skill: every operation is a ready-to-run curl command, guidance sticks to non-obvious gotchas (allDrives params, supportsAllDrives on per-file calls, trash-over-delete), and safety gating on writes is consistently applied. The main gap is verification: destructive and document-editing workflows end at 'report what changed' without an explicit re-read-to-confirm step or error-recovery loop, which the rubric caps at 3 for workflow clarity. Consolidating the repeated approval phrasing and splitting the Docs/Slides sections into reference files would push conciseness and progressive disclosure to the top of the scale.

Suggestions

Add an explicit post-write verification step for destructive and edit workflows, e.g. after a Sheets PUT or Docs batchUpdate, re-read the range/document to confirm the change landed before reporting success.

Document an error-recovery loop for failed writes (409/412 responses on Drive PATCH or batchUpdate: re-fetch current state, re-apply the change, retry) so destructive operations have a validate→fix→retry path.

State the approval-before-write rule once in '## Writes require approval' and reference it tersely from each write section instead of repeating the full sentence four times, trimming ~100 tokens.

DimensionReasoningScore

Conciseness

The body is command-first with no padding — it never explains what Drive/Sheets is or how OAuth works, and gotcha notes like "The three `allDrives` params matter: without them the API searches only 'My Drive'" are exactly the non-obvious knowledge that earns its tokens. It falls short of 5 because "This is a write — summarize... and get approval first" is repeated nearly verbatim across four sections and could be consolidated into the approval section once.

4 / 5

Actionability

Every section provides copy-paste-ready curl commands with real endpoints, query parameters, headers, and JSON bodies — e.g. the files list search with `q=name contains 'deadline'`, the multipart upload with `-F "metadata=..." -F "file=@report.pdf"`, and the Docs `:batchUpdate` `insertText` body — with clearly marked placeholders (FILE_ID, SPREADSHEET_ID). Coverage spans search, read, export, values update, upload, rename/move/trash/delete, and Docs/Slides edits, matching the 'fully executable, covers common cases' anchor.

5 / 5

Workflow Clarity

Sequences are clear and mostly checkpointed: read-before-edit for Docs ("First read the document to find the character indexes"), approval gates before every write, pagination guard ("If the response has a `nextPageToken`, keep fetching... before concluding anything is missing"), and post-action reporting ("Always report the file id/link and the modified range"). However, destructive and document-manipulation workflows (permanent DELETE, Docs/Slides `:batchUpdate`) lack explicit post-write verification (e.g. re-read the range or document to confirm the change) and any validate→fix→retry feedback loop for failed writes, which caps workflow clarity at 3 per the rubric's destructive/batch-operation guideline.

3 / 5

Progressive Disclosure

Nine well-labeled sections in logical order (connection → find → read → write), everything one level deep, no buried or nested references, and each curl block is compact enough to stay inline. It is not 5 because at ~220 lines spanning four distinct APIs, the Docs and Slides editing detail could arguably live in one-level-deep reference files, and the under-50-lines simple-skill exception does not apply; it is well above 3 because structure is clean and nothing that clearly belongs elsewhere is inlined.

4 / 5

Total

16

/

20

Passed

Description

66%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, third-person, and clearly scoped to Google's four productivity services with concrete action verbs, giving it low conflict risk. Its main weakness is the complete absence of any 'when to use' trigger guidance, which caps completeness and slightly undersells the skill's actual coverage (create, upload, share, delete). Adding a Use-when clause with natural synonyms would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions Google Drive, a Google Doc/Sheet/Slides presentation, or asks to find, share, or edit files in their Drive."

Name the write-side capabilities explicitly (create, upload, share, rename, move, delete) instead of the generic "manage" so the description matches what the skill body actually delivers.

Include common synonyms users say naturally — "spreadsheet", "presentation", "deck", "Google Workspace" — alongside the product names to broaden trigger coverage.

DimensionReasoningScore

Specificity

"Find, read, export, edit, and manage the user's Google Drive, Docs, Sheets, and Slides" lists several concrete actions (find, read, export, edit) across four named products, matching the 'several specific actions' anchor. It is not 5 because "manage" is generic and capabilities the body actually covers (create, upload, share, rename, delete) are never named explicitly; it is well above 3 because far more than 1-2 actions are listed.

4 / 5

Completeness

The 'what' is clear ("Find, read, export, edit, and manage" across the four services), but there is no "Use when..." clause or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. Not 4 because 'when' is entirely absent rather than merely imprecise; not 2 because the 'what' half is fully explicit.

3 / 5

Trigger Term Quality

Natural product names users would actually say are present: "Google Drive", "Docs", "Sheets", "Slides". It falls short of 5 because common synonyms and variations are missing ("spreadsheet", "presentation", "deck", "Google Workspace", file extensions), and sits above 3 because the terms present are the primary natural phrasings rather than technical jargon.

4 / 5

Distinctiveness Conflict Risk

Naming "Google Drive, Docs, Sheets, and Slides" carves a mostly distinct niche with minor overlap risk against generic file-management or adjacent Google-workspace skills. Not 5 because the missing trigger clause weakens distinct triggering and "manage" could pull in unrelated file skills; not 3 because the four product names are far more specific than "Works with document files".

4 / 5

Total

15

/

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.

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

yc-software/qm

Path

skills-seed/google-drive-sheets/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.