gws-workflow-weekly-digest
Google Workflow: Weekly summary: this week's meetings + unread email count.
61
52%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gws-workflow-weekly-digest/SKILL.mdQuality
Discovery
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 conveys a narrow, specific workflow (weekly summary with meetings and email count) but is too terse and lacks explicit trigger guidance. It reads more like a label than a proper skill description, missing a 'Use when...' clause and richer keyword coverage that would help Claude select it appropriately.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks for a weekly summary, wants to see this week's meetings, or needs an overview of their Google Calendar and Gmail inbox.'
Include more natural trigger terms and variations such as 'calendar', 'Gmail', 'inbox', 'schedule', 'this week's agenda', and 'email summary'.
Expand the 'what' portion to describe concrete actions, e.g., 'Fetches this week's Google Calendar events and counts unread Gmail messages to produce a consolidated 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 1. | 1 / 3 |
Trigger Term Quality | Includes some natural keywords like 'meetings', 'unread email', and 'weekly summary', but misses common variations users might say such as 'calendar', 'Gmail', 'inbox', 'this week', or 'schedule overview'. | 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; the narrow scope of weekly summary helps but isn't strongly delineated. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A concise, well-structured skill that effectively uses progressive disclosure and respects token budget. However, it lacks example output showing what the weekly digest actually produces, and the actionability is limited since the skill is essentially a CLI reference card without showing concrete results or implementation details.
Suggestions
Add an example output block showing what the weekly digest returns (e.g., sample JSON with meetings list and unread count) to improve actionability.
Briefly describe the workflow sequence (e.g., 'Fetches this week's calendar events via Calendar API, then queries Gmail for unread count') to clarify what the combined workflow does.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what a weekly digest is or how Google APIs work. Every line serves a purpose — usage, flags, examples, tips, and references. | 3 / 3 |
Actionability | Provides clear CLI commands and flag documentation, but the actual implementation details are entirely deferred to the shared skill and other references. There's no concrete code or detailed steps showing what the workflow actually does or how to build/extend it. | 2 / 3 |
Workflow Clarity | This is a simple single-command skill, but it combines two services (calendar + gmail) without explaining the sequence or what the output looks like. No example output is provided, making it unclear what the user/Claude should expect. | 2 / 3 |
Progressive Disclosure | Clean structure with well-signaled one-level-deep references to gws-shared and gws-workflow. The prerequisite is clearly called out at the top, and the See Also section provides clear navigation. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%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
c7c6646
- 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.