gws-workflow-weekly-digest

Google Workflow: Weekly summary: this week's meetings + unread email count.

Quality

58%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/gws-workflow-weekly-digest/SKILL.md

Quality

Content

85%

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

A well-structured, concise skill for a simple read-only CLI command. It effectively delegates shared concerns (auth, global flags) to a referenced skill and keeps the content focused. The main gap is the absence of example output, which would help Claude understand and present the digest results correctly.

Suggestions

Add a sample output example (e.g., a JSON snippet showing meetings and unread count) so Claude knows what the command returns and can format/interpret results correctly.

Dimension	Reasoning	Score
Conciseness	Very lean and efficient. No unnecessary explanations of what weekly digests are or how Gmail/Calendar APIs work. Every line serves a purpose.	3 / 3
Actionability	Provides clear CLI commands and flag documentation, but lacks concrete example output showing what the weekly digest actually looks like (e.g., sample JSON/table output). The user/Claude can run the command but doesn't know what to expect.	2 / 3
Workflow Clarity	This is a simple single-command skill (read-only) with no multi-step process or destructive operations. The single action is unambiguous, and the read-only nature is explicitly noted.	3 / 3
Progressive Disclosure	Clear, concise overview with well-signaled one-level-deep references to gws-shared for auth/global flags and gws-workflow for related commands. Appropriately delegates shared concerns to the prerequisite file.	3 / 3
	Total	11 / 12 Passed

Description

32%

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 very terse and reads more like a label than a proper skill description. While it hints at specific capabilities (weekly summary, meetings, unread email count), it lacks explicit trigger guidance, comprehensive action listing, and natural user-facing keywords. It would benefit significantly from expansion to help Claude reliably select it from a pool of skills.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks for a weekly summary, wants to see this week's calendar meetings, or needs an unread email count from Gmail.'

Include more natural trigger terms users would say, such as 'calendar', 'Gmail', 'inbox', 'schedule', 'weekly recap', 'week overview'.

Expand the 'what' portion to list concrete actions, e.g., 'Fetches this week's Google Calendar meetings and counts unread Gmail messages, then compiles them into a formatted weekly summary.'

Dimension	Reasoning	Score
Specificity	Names the domain (Google Workflow) and specific actions (weekly summary, meetings, unread email count), but the description is terse and doesn't elaborate on concrete operations like fetching calendar events, counting emails, or formatting the summary.	2 / 3
Completeness	Describes what it does (weekly summary of meetings and unread email count) but has no explicit 'Use when...' clause or trigger guidance, which per the rubric should cap completeness at 2, and the 'what' is also quite thin, placing this at a 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'meetings', 'unread email count', and 'weekly summary', but misses common user variations such as 'calendar', 'Gmail', 'inbox', 'schedule', 'this week', or 'recap'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'weekly summary', 'meetings', and 'unread email count' is somewhat specific to this workflow, but 'Google Workflow' is broad and could overlap with other Google-related skills for calendar or email tasks.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: googleworkspace/cli
Commit: a3768d0

Reviewed: 3 months 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.