Google Workflow: Today's meetings + open tasks as a standup summary.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill gws-workflow-standup-report71
Quality
58%
Does it follow best practices?
Impact
100%
2.70xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gws-workflow-standup-report/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 the basic purpose (generating standup summaries from Google calendar and tasks) but lacks explicit trigger guidance, which is critical for skill selection. It uses appropriate third-person voice and is concise, but would benefit from more specific action verbs and a clear 'Use when...' clause.
Suggestions
Add a 'Use when...' clause with trigger terms like 'standup', 'daily summary', 'what's on my calendar', 'morning briefing', or 'agenda for today'.
Expand trigger terms to include common variations: 'calendar', 'agenda', 'daily standup', 'to-do list', 'Google Calendar', 'Google Tasks'.
Specify concrete actions: 'Fetches today's calendar events and open tasks from Google Workspace to generate a standup summary.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Workflow) and specific outputs (today's meetings, open tasks, standup summary), but doesn't detail concrete actions like 'fetches calendar events' or 'queries task lists'. | 2 / 3 |
Completeness | Describes what it does (meetings + tasks as standup summary) 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 useful terms like 'meetings', 'tasks', and 'standup summary' that users might say, but misses common variations like 'daily standup', 'calendar', 'agenda', 'to-do', or 'morning briefing'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Google Workflow' + 'standup summary' provides some distinctiveness, but 'meetings' and 'tasks' are generic enough to potentially conflict with other calendar or task management skills. | 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 command. It efficiently documents usage, flags, and examples without unnecessary verbosity. The main weakness is the lack of example output showing what a standup report looks like, which would help Claude understand the expected format and content.
Suggestions
Add an example output showing what the standup report looks like (sample meeting entries + tasks format)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient - no unnecessary explanations, assumes Claude understands CLI patterns, every section serves a purpose without padding. | 3 / 3 |
Actionability | Provides concrete CLI commands and flag documentation, but lacks example output showing what the standup report actually looks like, making it harder to understand expected behavior. | 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, eliminating need for validation checkpoints. | 3 / 3 |
Progressive Disclosure | Appropriately structured with clear one-level-deep references to shared auth/flags and related workflow commands; content is well-organized for a simple skill. | 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 | |
Table of Contents
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.