google-drive-automation

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

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

The canonical home for this skill is google-drive in sanjay3290/ai-skills

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 that respects Claude's competence and stays lean. Its main weakness is the absence of validation/verification steps around destructive operations (trash, move), which caps workflow clarity.

Suggestions

Add a validation checkpoint for destructive ops, e.g. after `move`/`trash` run `python scripts/drive.py list <folder>` or `status` to confirm the result, and suggest confirming the FILE_ID via `search` before trashing.

Remove the duplicated one-line description at the top of the body (it repeats the frontmatter) to tighten conciseness.

Consider a short 'Common workflow' subsection showing a sequenced end-to-end example (find folder -> upload -> verify) to make multi-step flows explicit.

Dimension	Reasoning	Score
Conciseness	The body is a lean command reference with brief inline comments and no padding or explanation of concepts Claude already knows; the only minor trim is the duplicated intro line that repeats the frontmatter description, fitting 'Efficient; minor instances of over-explanation that could be trimmed.'	4 / 5
Actionability	Dozens of copy-paste-ready commands with concrete arguments (e.g. `python scripts/drive.py download 1ABC123xyz ./downloads/report.pdf`) cover search, upload, download, move, copy, rename, and trash, matching 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases.'	5 / 5
Workflow Clarity	The setup sequence (login/status/logout) is clear and commands are grouped, but destructive operations (trash, move, rename) have no validation or verification steps, so per the destructive-operations cap workflow_clarity cannot exceed 3 ('Steps listed but validation gaps; checkpoints missing or implicit').	3 / 5
Progressive Disclosure	Content is organized into well-labeled sections (Setup, Read, Write, Search Formats, File ID, Limitations, Token Management) with no nested references; at ~135 lines all content is appropriately inline, matching 'Good structure; most content is appropriately placed; minor organization gaps.'	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 the niche (Google Drive, standalone OAuth) but stops short of listing concrete actions or providing any 'Use when' trigger guidance. It is specific enough to avoid most conflicts yet generic in what it claims the skill does.

Suggestions

Add 2-3 concrete actions to the description (e.g., 'search, download, upload, and organize files in Google Drive') to lift specificity.

Append a 'Use when...' clause naming natural triggers (e.g., 'Use when the user asks to search, upload, or download files from Google Drive or mentions Drive URLs').

Include natural synonyms/extensions users say (Drive, Google Docs, share files) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("Google Drive integration") but the only actions named are generic ("Full read/write access", "OAuth authentication"); no concrete operations like upload/download/search are listed, matching the score-2 anchor 'Names the domain but actions are minimal or generic.'	2 / 5
Completeness	There is a clear 'what' (Google Drive integration with standalone OAuth) but no 'Use when...' or equivalent trigger guidance, so per the missing-trigger cap completeness stays at 3 ('Has a clear what but when is missing or only weakly implied').	3 / 5
Trigger Term Quality	"Google Drive" is a natural term a user would say, but common variations and action verbs (upload, download, share, files, docs) are absent, fitting the score-3 anchor 'Some relevant keywords but missing common variations or synonyms.'	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "Google Drive" gives it a clear niche with only minor overlap risk against other Google-related skills, matching the score-4 anchor 'Mostly distinct; minor overlap risk with closely related skills.'	4 / 5
	Total	12 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 23 missing	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/google-drive-automation/SKILL.md
Commit: 57c135b

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.