Names the domain (Google Workflow) and describes the output (standup summary from today's meetings and open tasks), but doesn't list multiple concrete actions like fetching calendar events, querying task lists, or formatting the summary.

Describes what it does (generates a standup summary from meetings and tasks) but has no explicit 'Use when...' clause or trigger guidance, which per the rubric should cap completeness at 2, and the 'what' is also fairly thin, placing this at 1.

Includes some natural keywords like 'meetings', 'tasks', 'standup summary', and 'Google', but misses common variations users might say such as 'daily standup', 'calendar', 'Google Calendar', 'Google Tasks', 'morning briefing', or 'status update'.

The combination of Google + standup summary is somewhat distinctive, but 'meetings' and 'tasks' are generic enough to potentially overlap with other calendar or task management skills. The lack of specificity about which Google services (Calendar, Tasks, etc.) increases conflict risk.

Very lean and efficient. No unnecessary explanations of what a standup report is or how calendars/tasks work. Every section earns its place.

Provides concrete CLI commands and flag documentation, but lacks example output showing what the standup report actually looks like. There's no sample JSON/table output to set expectations for the result format.

This is a simple single-command, read-only skill with no multi-step process or destructive operations. The single action is unambiguous and the read-only nature is explicitly noted.

Clear, well-organized sections with appropriate one-level-deep references to the shared skill and parent workflow skill. The prerequisite callout is well-signaled.