gws-tasks
Google Tasks: Manage task lists and tasks.
55
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
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 minimal to effectively guide skill selection. It lacks specific actions, explicit trigger conditions, and natural language variations users would employ. The 'Google Tasks' prefix helps with distinctiveness but the rest is too vague for reliable skill matching.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions Google Tasks, to-do lists, task management, or wants to create/complete/organize tasks'.
Replace vague 'Manage' with specific actions: 'Create, complete, and organize tasks; set due dates; manage multiple task lists'.
Include natural trigger terms users would say: 'to-do', 'todo', 'checklist', 'reminders', 'add task', 'mark done'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Manage task lists and tasks' which is vague and abstract. It doesn't list concrete actions like 'create tasks', 'set due dates', 'mark complete', or 'organize into lists'. | 1 / 3 |
Completeness | The description weakly answers 'what' with generic 'manage' language and completely lacks any 'when' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | 'Google Tasks', 'task lists', and 'tasks' are relevant keywords users might say, but missing common variations like 'to-do', 'todo', 'reminders', 'checklist', or action verbs like 'add task' or 'check off'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Tasks' provides some specificity to the Google ecosystem, but 'manage task lists and tasks' is generic enough to potentially conflict with other task management or to-do list skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-structured and concise, effectively documenting the Google Tasks API resources and methods. However, it lacks concrete executable examples showing actual task operations with parameters, and missing validation guidance for destructive operations that can affect linked documents.
Suggestions
Add 1-2 concrete examples showing common operations like creating a task or listing tasks with actual `--params` values
Add a warning or validation checkpoint for destructive operations (delete, clear) that affect linked Docs/Chat Spaces content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only essential information about API resources and methods without explaining what tasks are or how APIs work. Every section serves a clear purpose. | 3 / 3 |
Actionability | Provides concrete CLI commands for discovery (`gws tasks --help`, `gws schema`) but lacks executable examples showing actual task creation, listing, or manipulation with real parameters. | 2 / 3 |
Workflow Clarity | The discovery workflow is clear (browse -> inspect -> build params), but there are no validation steps or feedback loops for destructive operations like `delete` or `clear` which affect both Tasks and linked Docs/Chat Spaces. | 2 / 3 |
Progressive Disclosure | Appropriately references the shared skill file for auth and global flags, keeps the main content focused on Tasks-specific resources, and provides clear navigation via `--help` and `gws schema` commands. | 3 / 3 |
Total | 10 / 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.