CtrlK
BlogDocsLog inGet started
Tessl Logo

google-drive

Use connected Google Drive as the single entrypoint for Drive, Docs, Sheets, and Slides work. Use when the user wants to find, fetch, organize, share, export, copy, or delete Drive files, or summarize and edit Google Docs, Google Sheets, and Google Slides through one unified Google Drive plugin.

69

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

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

A well-structured, highly actionable router with explicit validation checkpoints in its workflows. Its weaknesses are redundant routing between the Workflow and Routing Rules sections, and a bundle whose reference and asset files are not wired into the body.

Suggestions

Collapse the per-type create/import cases from "Routing Rules" into Workflow step 3 (or vice versa) to remove the duplicated routing list and tighten conciseness.

Either link the references/slides/*.md guidance and assets/ images from the body where relevant, or move them to the google-slides skill bundle so this skill's bundle matches what the body actually references.

Add a one-line pointer in Routing Rules to the slides reference docs (e.g. deck-scope-verification, visual-change-loop) when routing Slides write work, so the existing bundle is discoverable.

DimensionReasoningScore

Conciseness

The body is mostly tight and free of concept-explanation fluff, but the per-type create/import routing in "Routing Rules" repeats what "Workflow" step 3 already covers, so it could be tightened.

2 / 3

Actionability

Names specific tools and parameters ("update_file with addParents/removeParents", "export_file", "fetch(download_raw_file=True)", "list_file_revisions") plus concrete MIME-type-based decision rules, giving fully actionable guidance.

3 / 3

Workflow Clarity

A clear numbered 1-2-3 sequence with explicit validation checkpoints — "verify the move by reading metadata or listing the target folder before the final response" and "verify the created file with connector readback... before returning the URL".

3 / 3

Progressive Disclosure

Sibling-skill links are clean and one level deep, but the bundle contains four references/slides/*.md files and four image assets that the body never references or navigates to, so disclosure against the actual bundle is incomplete.

2 / 3

Total

10

/

12

Passed

Description

92%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, explicit description with concrete actions, natural trigger terms, and clear what/when guidance. Its one weakness is overlap risk: it claims edit/summarize coverage for Docs, Sheets, and Slides that the dedicated sibling skills also own.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "find, fetch, organize, share, export, copy, or delete Drive files, or summarize and edit" — rather than vague language, matching the level-3 anchor.

3 / 3

Completeness

Explicitly answers what ("Use connected Google Drive as the single entrypoint for Drive, Docs, Sheets, and Slides work") and when ("Use when the user wants to find, fetch, organize..."), satisfying both halves.

3 / 3

Trigger Term Quality

Phrases like "find, fetch, organize, share, export, copy, or delete" and "summarize and edit Google Docs, Google Sheets, and Google Slides" are natural terms users would say, giving good coverage.

3 / 3

Distinctiveness Conflict Risk

The Drive file-lifecycle triggers are distinct, but the claim to "summarize and edit Google Docs, Google Sheets, and Google Slides" directly overlaps the dedicated sibling skills it routes to, so it could still trigger for the wrong skill.

2 / 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

relative_links

Relative link issues: 9 suspicious

Warning

Total

15

/

16

Passed

Repository
openai/plugins
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.