CtrlK
BlogDocsLog inGet started
Tessl Logo

google-drive

Google Drive integration. Manage Drives, Users, Permissions. Use when the user wants to interact with Google Drive data.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

75%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 highly actionable with executable commands and a well-sequenced connection workflow, though it opens with unnecessary introductory fluff and ships a sizable inline actions table that a references file could absorb.

Suggestions

Cut the introductory paragraph ("cloud-based file storage… virtual hard drive in the cloud") — Claude already knows what Google Drive is.

Add a verification/warning step before destructive actions, e.g. confirm file ID and note that delete bypasses trash before running delete-file.

Move the Popular actions and proxy flag tables into a references/ file, keeping only the few most common actions inline in SKILL.md.

DimensionReasoningScore

Conciseness

The bulk is efficient concrete commands, but the opening "Think of it as a virtual hard drive in the cloud" and the redundant Google Drive Overview bullets explain concepts Claude already knows.

3 / 5

Actionability

Commands like `membrane connection ensure`, `membrane action list --intent`, and `membrane action run ... --input` are copy-paste ready and cover install, auth, connect, search, run, and proxy cases.

5 / 5

Workflow Clarity

The connect→search→run sequence is explicit with a state-machine (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a polling feedback loop, but destructive actions like "Delete File (bypasses trash)" lack verification guidance.

4 / 5

Progressive Disclosure

Well-organized sections with clear headers and no nested references, but the large Popular actions table and proxy flag table are inline reference material that could live in a dedicated reference file.

4 / 5

Total

16

/

20

Passed

Description

66%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 cleanly states both capability and trigger for a well-scoped product integration, but leans on the generic verb "Manage" and a somewhat vague "Use when" clause rather than concrete operations and trigger phrases.

Suggestions

Replace the generic "Manage" with concrete verbs, e.g. "List, create, update, and delete files, folders, and permissions".

Expand the "Use when" clause with concrete triggers users say, e.g. "when the user mentions Google Drive, Drive files, folders, sharing, or permissions".

Add common synonyms/extensions ("Drive", ".gdoc", "shared drives") to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

"Manage Drives, Users, Permissions" names the domain and three concrete entities, but the single generic verb "Manage" leaves the actions underspecified compared to listing distinct operations.

3 / 5

Completeness

Both halves are present — "Manage Drives, Users, Permissions" (what) and "Use when the user wants to interact with Google Drive data" (when) — but the trigger clause is generic rather than concrete phrases.

4 / 5

Trigger Term Quality

"Google Drive" / "Google Drive data" are relevant natural keywords, but common variations like "Drive", "files", "folders", or "sharing" are missing.

3 / 5

Distinctiveness Conflict Risk

Naming the specific product "Google Drive" with a targeted interaction trigger carves a clear niche with minimal overlap against other skills.

5 / 5

Total

15

/

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
membranedev/application-skills
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.