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.

85

1.36x
Quality

Does it follow best practices?

Impact

97%

1.36x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is highly actionable with clear, validated multi-step workflows, but it loses conciseness through a redundant consolidated pitfalls section and does not split detailed reference material into separate files. Trimming duplication and extracting reference tables would improve both lowest dimensions.

Suggestions

Remove the standalone 'Known Pitfalls' section or reduce it to a one-line pointer, since each pitfall already appears in its workflow's Pitfalls list.

Move the Query Syntax, Export Formats, and Quick Reference material into a separate references file linked one level deep from the overview.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's competence (no explaining what Google Drive is), but the 'Known Pitfalls' section redundantly restates pitfalls already covered in each workflow's Pitfalls list, adding tokens that could be trimmed.

2 / 3

Actionability

Provides concrete, specific guidance throughout — exact tool slugs, parameter names, query-string examples, and a quick-reference table — which is copy-paste-ready for an MCP-driven (instruction-only) skill.

3 / 3

Workflow Clarity

Each workflow is a numbered tool sequence with prerequisite/required/optional/fallback labels, plus explicit validation checkpoints ('Confirm connection status shows ACTIVE', 'verify file after upload/download', 'Always verify parent folder exists') and confirmation prompts for risky sharing.

3 / 3

Progressive Disclosure

Well-organized single-file structure, but it is a ~190-line monolith with no bundle files; content such as the full query-syntax reference, quick-reference table, and consolidated pitfalls is inline that could be split into one-level-deep reference files.

2 / 3

Total

10

/

12

Passed

Description

82%

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, uses natural trigger terms, and is clearly niched to Google Drive via Rube MCP, but it omits an explicit 'Use when...' trigger clause, which caps completeness at 2. Adding a use-when clause would likely raise it to a top score.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user wants to upload, download, search, share, or organize files in Google Drive.'

Include common phrasings users say ('share a Drive file', 'search my Drive', 'move files between folders') to strengthen trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'upload, download, search, share, organize' plus 'manage folders, share with permissions, and search across drives' — matching the multiple-concrete-actions anchor.

3 / 3

Completeness

Clearly answers 'what' but lacks an explicit 'Use when...' trigger clause, so per the rubric guideline a missing trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

Uses natural terms a user would say ('upload/download files', 'search', 'share', 'organize', 'folders', 'permissions', 'Google Drive') with good coverage of common variations; not merely technical jargon.

3 / 3

Distinctiveness Conflict Risk

Scoped to 'Google Drive file operations via Rube MCP (Composio)' — a clear niche with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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.