CtrlK
BlogDocsLog inGet started
Tessl Logo

recipe-share-folder-with-team

Share a Google Drive folder and all its contents with a list of collaborators.

57

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/recipe-share-folder-with-team/SKILL.md

The canonical home for this skill is pleaseai/google-workspace

SKILL.md
Quality
Evals
Security

Quality

Content

80%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 exemplarily concise and provides concrete executable commands with a verification step, but as a batch permission operation it lacks an explicit feedback loop and the wiring from the folder lookup to the share steps (and across a list of collaborators) is only implicit.

Suggestions

Add an explicit instruction to substitute the folder id from step 1 into FOLDER_ID for steps 2-4.

Show how to iterate over a list of collaborators rather than hardcoding two example emails.

Add a feedback loop after step 4, e.g. "If a collaborator's permission is missing or wrong, re-run step 2/3 for that address and re-verify."

DimensionReasoningScore

Conciseness

The body is extremely lean — a prerequisite line, one summary sentence, and four numbered commands — with zero padding or explanation of concepts Claude already knows, matching the 5 anchor of "lean and efficient; every token earns its place"; it is not below 5 because nothing is over-explained.

5 / 5

Actionability

Steps 1-4 give concrete, executable `gws` commands with real params covering the editor and viewer common cases, but the FOLDER_ID placeholder wiring from step 1 to steps 2-4 is implicit and the steps hardcode two example emails rather than showing how to handle "a list of collaborators", leaving minor gaps that fit the 4 anchor.

4 / 5

Workflow Clarity

The sequence is clear (find → share editor → share viewer → verify) and a verification step exists, but this is a batch permission operation with no feedback loop (no "if permission missing, re-add and re-verify" path) and the list-iteration handling is implicit; per the scoring notes, missing feedback loops in batch contexts cap workflow_clarity at 3.

3 / 5

Progressive Disclosure

This is a sub-50-line single-purpose skill with no need for external references and no bundle files present; it is well-organized under a clear ## Steps section, so per the simple-skill guideline progressive disclosure scores 5 with just well-organized sections.

5 / 5

Total

17

/

20

Passed

Description

53%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 is concise and third-person with a clear "what", but it omits any explicit "when"/trigger guidance and offers only moderate keyword coverage. Adding a "Use when..." clause with natural synonyms would lift completeness and trigger quality.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants to share a Google Drive folder with a team or set collaborator access."

Add natural synonyms users say — "team", "permissions", "access", "share Drive folder" — to broaden trigger-term coverage.

Consider naming additional concrete actions (e.g., granting editor vs viewer roles) to raise specificity beyond one action.

DimensionReasoningScore

Specificity

Quotes "Share a Google Drive folder and all its contents with a list of collaborators" — it names the domain (Google Drive folder) and one concrete action (share with collaborators), but coverage is not comprehensive (no mention of removing/editing permissions or other share operations), matching the 3 anchor of domain plus 1-2 concrete actions.

3 / 5

Completeness

The what is clear ("Share a Google Drive folder and all its contents with a list of collaborators") but there is no "when"/"Use when..." clause at all; per the guideline a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms "Google Drive folder", "share", and "collaborators", but misses common variations users would say ("team", "permissions", "access", file extensions), so it sits at the 3 anchor of relevant keywords with missing synonyms rather than the broader 4 coverage.

3 / 5

Distinctiveness Conflict Risk

The niche is fairly specific — sharing Drive folders with collaborators — so it is mostly distinct with only minor overlap risk against a general Drive-management skill, fitting the 4 anchor; it is not a 5 because it lacks explicit trigger phrases that fully separate it from sibling Drive recipes.

4 / 5

Total

13

/

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

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository
googleworkspace/cli
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.