gws-tasks

Google Tasks: Manage task lists and tasks.

Quality

40%

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-tasks/SKILL.md

Quality

Content

57%

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

This is a functional API reference skill that provides good structure and appropriate progressive disclosure via the shared skill file. However, it lacks concrete executable examples showing actual task operations with real parameters, and the verbose method descriptions duplicate information discoverable via `gws schema`. Adding 1-2 concrete examples and trimming the API descriptions would significantly improve it.

Suggestions

Add 1-2 concrete executable examples showing common operations (e.g., `gws tasks tasklists insert --params title='My List'` and `gws tasks tasks insert --params tasklist=<id> --json '{"title": "Buy groceries"}'`)

Trim the method descriptions to just the method names or one-line summaries, since detailed behavior can be discovered via `gws schema tasks.<resource>.<method>`

Add a brief note about validation or caution for destructive operations like `clear` and `delete`, especially given that delete affects assigned tasks in Docs/Chat Spaces

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but includes some verbose API descriptions (e.g., explaining what delete does for assigned tasks, limits like '2000 lists at a time') that could be trimmed. The method descriptions are essentially API documentation that Claude could discover via `gws schema`.	2 / 3
Actionability	Provides the CLI syntax and discovery commands (`gws schema`, `--help`), but lacks concrete executable examples of actual task operations (e.g., creating a task list, inserting a task with specific `--params`/`--json` flags). The guidance tells you how to discover commands but doesn't show copy-paste-ready usage.	2 / 3
Workflow Clarity	The 'Discovering Commands' section provides a two-step discovery workflow (browse then inspect), but there's no workflow for common multi-step operations like 'create a task list then add tasks to it.' For a simple reference skill this is adequate but lacks validation or error handling guidance for destructive operations like `delete` and `clear`.	2 / 3
Progressive Disclosure	Cleanly references the shared skill file (`../gws-shared/SKILL.md`) for auth and global flags, keeping this file focused on Tasks-specific content. The structure is well-organized with clear sections and the content is appropriately scoped for a single skill file.	3 / 3
	Total	9 / 12 Passed

Description

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too terse and vague to be effective for skill selection. It names the product (Google Tasks) but fails to enumerate specific capabilities and completely lacks trigger guidance. In a pool of many skills, Claude would struggle to confidently select this skill over other task-management-related skills.

Suggestions

List specific concrete actions such as 'create tasks, mark tasks complete, set due dates, list task lists, delete tasks, move tasks between lists'.

Add a 'Use when...' clause with natural trigger terms like 'Use when the user mentions Google Tasks, to-do lists, task management, checking off items, or due dates'.

Include common user phrasings and file/service identifiers such as 'to-do', 'todo list', 'Google to-do', 'gtasks' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description says 'Manage task lists and tasks' which is extremely vague. It doesn't list any concrete actions like creating tasks, marking tasks complete, setting due dates, moving tasks between lists, etc.	1 / 3
Completeness	The 'what' is very weak ('manage task lists and tasks' is barely descriptive), and there is no 'when' clause or explicit trigger guidance at all. The missing 'Use when...' clause caps this at 2, but the weak 'what' brings it to 1.	1 / 3
Trigger Term Quality	It includes 'Google Tasks', 'task lists', and 'tasks' which are relevant keywords, but misses common variations like 'to-do', 'todo', 'checklist', 'due date', 'reminders', or specific actions users might request.	2 / 3
Distinctiveness Conflict Risk	'Google Tasks' is a specific product name which helps distinguish it from generic task management, but 'manage task lists and tasks' could overlap with other task/project management skills (e.g., Todoist, Asana integrations).	2 / 3
	Total	6 / 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.