CtrlK
BlogDocsLog inGet started
Tessl Logo

google-drive-automation

Automate Google Drive file operations (upload, download, search, share, organize) via Rube MCP (Composio). Upload/download files, manage folders, share with permissions, and search across drives programmatically.

80

1.36x
Quality

71%

Does it follow best practices?

Impact

97%

1.36x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/google-drive-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 well-structured, action-dense, and respectful of Claude's competence, with clear tool sequences. The main gaps are missing validation feedback loops for destructive/batch operations and some duplicated pitfall content.

Suggestions

Add explicit validate-then-retry checkpoints to destructive/batch workflows (e.g., after DELETE_PERMISSION verify with LIST_PERMISSIONS; after MOVE_FILE verify single parent with GET_FILE_METADATA).

De-duplicate pitfalls: keep them only in the per-workflow sections or only in "Known Pitfalls", not both, to save tokens.

DimensionReasoningScore

Conciseness

Dense and assumes Claude's intelligence with no padding about Drive or OAuth, but pitfalls are repeated in both per-workflow sections and the consolidated "Known Pitfalls" section, and the Quick Reference table re-lists tool slugs.

4 / 5

Actionability

Provides concrete tool slugs, exact parameter names, working query-syntax examples, and export mime types; falls short of 5 only because there is no full end-to-end worked example.

4 / 5

Workflow Clarity

Numbered tool sequences with role tags are clear and Setup includes connection-status verification, but destructive/batch operations (delete permission, move with multi-parent, anyone-sharing) lack explicit validate-and-retry feedback loops, capping the score at 3.

3 / 5

Progressive Disclosure

Self-contained SKILL.md with well-organized sections (Prerequisites, Setup, Workflows, Patterns, Pitfalls, Quick Reference) and one external toolkit-docs link; minor gap is the inlined/duplicated Known Pitfalls content that could be consolidated.

4 / 5

Total

15

/

20

Passed

Description

75%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 and well-scoped to Google Drive automation, listing concrete actions and a distinct niche. Its main weakness is the missing "Use when..." trigger guidance, which limits completeness.

Suggestions

Add an explicit "Use when..." clause naming natural triggers, e.g., "Use when the user wants to upload, download, search, or share files in Google Drive, or manage Drive folders."

Include a few more natural user phrasings and synonyms (e.g., "Drive files", "share files", ".gdoc") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("upload, download, search, share, organize", "manage folders", "share with permissions", "search across drives") giving comprehensive coverage of the domain.

5 / 5

Completeness

Clearly states the "what" but has no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Good natural-term coverage ("Google Drive", "upload", "download", "search", "share") but missing common variations like "Drive files" or "share files".

4 / 5

Distinctiveness Conflict Risk

Scoped to Google Drive via Rube MCP/Composio, giving it a clear niche with minimal overlap risk.

5 / 5

Total

17

/

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.

Validation15 / 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
davepoon/buildwithclaude
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.