gws-workflow-weekly-digest
Google Workflow: Weekly summary: this week's meetings + unread email count.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill gws-workflow-weekly-digest64
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 provides a basic understanding of the skill's function but is too terse and lacks explicit trigger guidance. It names specific outputs (meetings, unread email count) which helps, but the absence of a 'Use when...' clause and limited trigger terms significantly reduce its effectiveness for skill selection among many options.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks for a weekly overview, wants to see their calendar summary, or needs to check their email status'
Include natural keyword variations users would say: 'calendar', 'schedule', 'inbox', 'Gmail', 'this week's appointments', 'email summary'
Expand the capability description to clarify outputs: 'Generates a weekly summary showing upcoming/past meetings from Google Calendar and unread email count from Gmail'
| 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 what 'weekly summary' entails or what outputs are produced. | 2 / 3 |
Completeness | Describes what it does (weekly summary of meetings and email count) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'meetings', 'email', 'weekly summary', but missing common variations users might say like 'calendar', 'inbox', 'this week', 'schedule', or 'Gmail'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Google Workflow' with 'weekly summary' and 'meetings + email' provides some distinctiveness, but could overlap with other Google/calendar/email skills without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill for a simple CLI workflow command. It excels at token efficiency and appropriate cross-referencing. The main weakness is the lack of concrete output examples showing what the weekly digest actually produces, which would help Claude understand the expected response format.
Suggestions
Add a sample output example showing what the weekly digest returns (e.g., JSON structure with meeting count, unread email count, etc.)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, with no unnecessary explanations. Every section serves a purpose and assumes Claude understands CLI tools and workflows. | 3 / 3 |
Actionability | Provides clear CLI commands and flag documentation, but lacks concrete output examples showing what the weekly digest actually returns. No sample output format is shown. | 2 / 3 |
Workflow Clarity | This is a simple single-command skill with no multi-step process. The usage is unambiguous and the read-only nature is clearly stated, making validation unnecessary. | 3 / 3 |
Progressive Disclosure | Appropriately structured with clear one-level-deep references to shared auth/flags and related workflow commands. The prerequisite is clearly signaled at the top. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- 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.