CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

google-drive-upload

Upload files directly to Google Drive via a deployed Google Apps Script web app. Trigger on: upload to Drive, save to Drive, send to Drive, put this in Drive. Also Hebrew: "תעלה לדרייב", "שמור בדרייב", "העלה לגוגל דרייב". Use proactively when a workflow produces a file the user might want in Drive.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/google-drive-upload/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.

A compact, well-structured body for a simple single-purpose skill: concrete bash commands carry the workflow and nothing bulky is inlined. The main gaps are the unresolved 'included' Apps Script prerequisite, placeholder-laden (not copy-paste ready) upload commands, and the absence of any response-validation or error-handling step.

Suggestions

Bundle or inline the Google Apps Script deployment code (or point the Prerequisites step directly at the GitHub setup guide) so "Deploy the included Google Apps Script" resolves to a real file.

Add an explicit validation step after the curl POST — check the response for the returned Drive file URL and handle auth or upload failures before reporting success.

Make the upload command copy-paste ready by showing how to substitute the scriptUrl and apiKey values read from ~/.cowork-gdrive-config.json into the curl call, and use the actual filename for fileName.

DimensionReasoningScore

Conciseness

The body is lean and code-forward with no explanations of concepts Claude already knows; the main trimmable content is the promotional attribution "Built by MSApps — AI Automation & Application Development" and a "When to Use This Skill" section that largely repeats the frontmatter triggers. This matches 'efficient; minor instances that could be trimmed' rather than the fully lean anchor (5), and is well above noticeably verbose (3).

4 / 5

Actionability

The upload workflow gives real, concrete commands — `B64=$(base64 "$FILE" | tr -d '\n')`, `MIME=$(file --mime-type -b "$FILE")`, and a full curl POST — but they are not copy-paste ready: placeholders "SCRIPT_URL", "KEY", and the literal `"fileName":"name"` need substitution, and the prerequisite "Deploy the included Google Apps Script as a web app" has no bundled script code to deploy. This sits between concrete-with-minor-gaps (4) and missing-key-details (3); the commands are genuinely executable rather than pseudocode, so 4 fits best.

4 / 5

Workflow Clarity

The sequence is clear and consistent across sections (read config → base64-encode → POST to the Apps Script → return the Drive URL), each step backed by a concrete command. It falls short of the top anchor because there is no explicit validation checkpoint — nothing checks the curl response for the returned file URL or handles auth/upload failures before reporting success. Upload is neither destructive nor batch, so the workflow-clarity cap does not apply.

4 / 5

Progressive Disclosure

Sections are well organized (When to Use / What This Skill Does / How to Use / Tips / Source) and the bulk setup material is appropriately deferred to a clearly signaled one-level source: "Full plugin with setup guide and Apps Script code: https://github.com/msmobileapps/google-drive-upload-plugin". It is not a 5 because "Deploy the included Google Apps Script" references an 'included' script that is not present in the skill bundle (no references/, scripts/, or assets/ files exist), leaving that pointer unresolved.

4 / 5

Total

16

/

20

Passed

Description

78%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.

A strong description that clearly and explicitly states both what the skill does and when to use it, with unusually good bilingual (English/Hebrew) trigger coverage. The main weakness is specificity: only the single 'upload' action is named, leaving capabilities like folder targeting, overwrite behavior, and the size limit unstated.

Suggestions

List the skill's concrete capabilities in the description (e.g., organizing uploads into folder paths, overwriting existing files, the ~50MB size limit) to raise specificity beyond the single 'upload' action.

Add missing natural English trigger variations such as 'back up to Drive', 'move to Drive', or 'add to Drive' alongside the existing upload/save/send/put set.

DimensionReasoningScore

Specificity

The description gives one concrete action — "Upload files directly to Google Drive via a deployed Google Apps Script web app" — naming both the action and the mechanism, matching the anchor for 1-2 concrete actions without comprehensive coverage. It is not a 4 because it does not list several specific actions (folder organization, overwrite behavior, size limits are absent), and not a 2 because the action stated is concrete rather than generic domain-naming.

3 / 5

Completeness

Both questions are answered explicitly: the 'what' is "Upload files directly to Google Drive via a deployed Google Apps Script web app" and the 'when' is given with concrete trigger phrases ("Trigger on: upload to Drive, save to Drive..." and "Use proactively when a workflow produces a file the user might want in Drive"), matching the top anchor. It is not a 4 because the 'when' clause is already explicit and trigger-phrase-based, not merely adequate.

5 / 5

Trigger Term Quality

Good natural-phrase coverage with verb variations — "upload to Drive, save to Drive, send to Drive, put this in Drive" — plus Hebrew synonyms "תעלה לדרייב", "שמור בדרייב", "העלה לגוגל דרייב". It falls short of the comprehensive anchor (5) because common variations like "back up to Drive", "move to Drive", or "add to Drive" are missing, but it clearly exceeds 'some relevant keywords' (3).

4 / 5

Distinctiveness Conflict Risk

The Google Drive niche is distinct and its triggers ("upload to Drive", "put this in Drive") are unlikely to fire for unrelated skills, giving mostly-distinct coverage with minor overlap risk against generic file-saving skills. It is not a 5 because the proactive clause "when a workflow produces a file the user might want in Drive" is broad enough to overlap with any file-producing workflow.

4 / 5

Total

16

/

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.

Validation — 15 / 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

Path

plugins/all-skills/skills/google-drive-upload/SKILL.md

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.