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.

Install with Tessl CLI

npx tessl i github:Lingjie-chen/MT5 --skill google-drive-automation
What are skills?

77

1.36x

Quality

67%

Does it follow best practices?

Impact

97%

1.36x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./.trae/skills/google-drive-automation/SKILL.md
SKILL.md
Review
Evals

Discovery

50%

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 excels at listing specific capabilities and is clearly scoped to Google Drive operations, making it distinctive. However, it critically lacks any 'Use when...' guidance, which means Claude won't have explicit triggers for when to select this skill over others. The trigger terms are adequate but could include more natural user language variations.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions Google Drive, needs to upload/download files to Drive, wants to share documents, or asks about cloud file management.'

Include common user language variations such as 'gdrive', 'cloud storage', 'Google Docs', 'sharing links', or 'Drive permissions' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'upload, download, search, share, organize', 'manage folders', 'share with permissions', and 'search across drives programmatically'. Uses third person voice correctly.

3 / 3

Completeness

Clearly describes WHAT the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for WHEN Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, but this has no 'when' at all.

1 / 3

Trigger Term Quality

Includes good keywords like 'Google Drive', 'upload', 'download', 'search', 'share', 'folders', but missing common variations users might say like 'gdrive', 'cloud storage', 'file sharing', or specific file type mentions.

2 / 3

Distinctiveness Conflict Risk

Clearly scoped to 'Google Drive' and 'Rube MCP (Composio)' which creates a distinct niche. Unlikely to conflict with generic file operations or other cloud storage skills due to explicit Google Drive focus.

3 / 3

Total

9

/

12

Passed

Implementation

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured, comprehensive skill for Google Drive automation that excels in organization and workflow clarity. The content efficiently covers multiple workflows with clear tool sequences and pitfall warnings. The main weakness is the lack of executable code examples showing actual tool invocations with sample parameters, which would make the guidance more immediately actionable.

Suggestions

Add 1-2 concrete tool call examples with actual parameter values (e.g., a complete GOOGLEDRIVE_FIND_FILE call with a sample query string and expected response structure)

Include a sample workflow showing the exact tool calls for a common task like 'upload a file to a specific folder' with realistic parameter values

DimensionReasoningScore

Conciseness

The content is lean and efficient, avoiding explanations of concepts Claude already knows. Every section provides actionable information without padding or unnecessary context about what Google Drive is or how APIs work.

3 / 3

Actionability

While the skill provides specific tool names, parameters, and sequences, it lacks executable code examples. The guidance is concrete but relies on tool slugs and parameter descriptions rather than copy-paste ready examples showing actual tool calls with sample data.

2 / 3

Workflow Clarity

Multi-step processes are clearly sequenced with labeled steps (Prerequisite, Required, Optional, Fallback). Each workflow includes validation checkpoints like verifying connection status is ACTIVE before proceeding and checking file metadata after operations.

3 / 3

Progressive Disclosure

Content is well-organized with clear sections progressing from prerequisites to setup to core workflows to common patterns. The quick reference table at the end provides excellent navigation, and external toolkit docs are linked without deep nesting.

3 / 3

Total

11

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

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.