recipe-share-event-materials

Share Google Drive files with all attendees of a Google Calendar event.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/recipe-share-event-materials/SKILL.md

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

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 a lean, well-structured recipe with concrete executable commands and a verification step, but its batch-sharing workflow lacks an explicit iteration pattern and a failure-recovery feedback loop.

Suggestions

Show how to iterate over the returned attendees (e.g., loop the permissions create call for each emailAddress) rather than a single placeholder example.

Add a feedback loop after the verify step: confirm each attendee appears in the permissions list and re-share any that are missing.

Clarify handling for external (non-domain) attendees and failure cases, since batch permission grants can partially fail.

Dimension	Reasoning	Score
Conciseness	The body is lean: a title, one prerequisite note, a single restatement of the task, and three numbered steps with concrete commands — no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Each step provides concrete, executable `gws` commands with full JSON params, but placeholders (EVENT_ID, FILE_ID, attendee@company.com) require substitution and step 2 does not show how to iterate over each attendee.	4 / 5
Workflow Clarity	The three-step sequence is clear and includes a verify step, but this is a batch operation (sharing with each attendee) with no per-attendee confirmation and no retry/fix feedback loop, which caps workflow clarity at 3 per the batch-operations rule.	3 / 5
Progressive Disclosure	The skill is under 50 lines, needs no external references (none exist), and is organized into a prerequisite note and a Steps section, satisfying the simple-skill exception for a top score.	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 specific and clearly states a single concrete cross-product action, but it omits any "Use when…" trigger guidance and lacks keyword synonyms, leaving it mid-tier rather than exemplary.

Suggestions

Add a "Use when…" clause naming natural trigger phrases (e.g., "Use when a user wants to share Drive files with everyone invited to a Calendar meeting.").

Include synonym keywords such as meeting, invite, attendees, and permissions to improve trigger-term coverage.

Mention the concrete sub-actions (e.g., list attendees, then grant reader access to each) to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	"Share Google Drive files with all attendees of a Google Calendar event" names the domain plus one concrete action (sharing files), but lists only a single action so it is not comprehensive enough for a 4.	3 / 5
Completeness	The description gives a clear "what" but no "Use when…" trigger guidance, which per the rubric caps completeness at 3 even though the action statement is clear.	3 / 5
Trigger Term Quality	It has relevant natural terms (Share, Google Drive files, attendees, Google Calendar event) but lacks common synonyms and variations a user might say such as meeting, invite, permissions, or collaborators.	3 / 5
Distinctiveness Conflict Risk	Combining Drive sharing with Calendar attendees is a clear cross-product niche, but it carries minor overlap risk with generic drive-sharing or calendar skills and lacks an explicit distinct trigger phrase, keeping it below 5.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: googleworkspace/cli
Path: skills/recipe-share-event-materials/SKILL.md
Commit: a3768d0

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.