gws-tasks

Google Tasks: Manage task lists and tasks.

Quality

40%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/gws-tasks/SKILL.md

Quality

Discovery

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. While it correctly identifies the domain (Google Tasks), it fails to enumerate specific capabilities and completely lacks trigger guidance. It would benefit significantly from listing concrete actions and adding explicit 'Use when...' conditions.

Suggestions

List specific concrete actions such as 'Create, update, complete, and delete tasks; manage task lists; set due dates and notes' instead of the vague 'manage'.

Add a 'Use when...' clause with trigger terms like 'Use when the user mentions Google Tasks, to-do lists, task management, checklists, or wants to organize tasks with due dates.'

Include common user-facing synonyms and variations like 'to-do', 'todo', 'checklist', 'reminders' 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') and there is no 'when' clause at all. The absence of a 'Use when...' clause caps this at 2 per the guidelines, but the 'what' is also too vague, bringing it to 1.	1 / 3
Trigger Term Quality	It includes 'Google Tasks', 'task lists', and 'tasks' which are relevant keywords a user might say. However, it's missing common variations like 'to-do', 'todo', 'checklist', 'due date', or specific actions users would request.	2 / 3
Distinctiveness Conflict Risk	'Google Tasks' is a specific product name which helps distinguish it from generic task management skills, but 'manage task lists and tasks' is generic enough that it could overlap with other task/todo management skills.	2 / 3
	Total	6 / 12 Passed

Implementation

57%

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

This skill provides a reasonable reference for Google Tasks CLI usage with good progressive disclosure via the shared skill reference. However, it lacks concrete executable examples of actual task operations (e.g., creating a task list, inserting a task with specific params), and the verbose method descriptions duplicate information already available through the built-in `gws schema` and `--help` commands.

Suggestions

Add 2-3 concrete, copy-paste-ready 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 API method descriptions to just the method names or one-line summaries, since detailed behavior is discoverable via `gws schema tasks.<resource>.<method>`.

Add a brief workflow example showing a common multi-step sequence like: list task lists → get list ID → insert task → verify with list.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but includes verbose API method descriptions that Claude could discover via `gws schema` or `--help`. The descriptions of each method (e.g., explaining what delete does for assigned tasks) add bulk that could be trimmed since the skill already teaches how to discover commands.	2 / 3
Actionability	Provides concrete CLI commands for discovery (`gws schema`, `--help`) but lacks any executable examples of actually creating, listing, or managing tasks. No example `--params` or `--json` usage is shown, leaving the user to figure out the actual invocation patterns.	2 / 3
Workflow Clarity	The discovery workflow (help → schema → build command) is implied but not explicitly sequenced. For a relatively simple CLI wrapper skill this is adequate, but there are no validation steps or examples of complete task management workflows (e.g., create list → add task → verify).	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 one-level-deep references.	3 / 3
	Total	9 / 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: c7c6646

Reviewed: about 8 hours 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.