recipe-create-task-list
Set up a new Google Tasks list with initial tasks.
67
60%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/recipe-create-task-list/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 is brief and identifies the core domain (Google Tasks) and a basic action (setting up a new list with tasks), but it lacks depth in specifying capabilities and entirely omits explicit trigger guidance. It would benefit significantly from a 'Use when...' clause and more specific action details to help Claude distinguish this skill from others.
Suggestions
Add a 'Use when...' clause with trigger terms like 'create a new Google Tasks list', 'set up tasks', 'initialize a to-do list in Google Tasks'.
Expand the capability description with more specific actions, e.g., 'Creates a new Google Tasks list, populates it with initial tasks including titles, due dates, and notes.'
Include common user-facing synonyms and variations such as 'to-do list', 'task list', 'Google task manager' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Tasks) and two actions (set up a new list, add initial tasks), but doesn't elaborate on specific capabilities like setting due dates, organizing subtasks, or configuring task properties. | 2 / 3 |
Completeness | Describes what it does (set up a Google Tasks list with initial tasks) but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' itself is also quite thin, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes 'Google Tasks' and 'tasks list' which are relevant keywords, but misses common variations like 'to-do list', 'task manager', 'Google task list', or 'create tasks'. Coverage of natural user language is limited. | 2 / 3 |
Distinctiveness Conflict Risk | Specifying 'Google Tasks' provides some distinctiveness from generic task or to-do skills, but could overlap with other Google Tasks skills (e.g., editing tasks, managing existing lists) since the scope isn't sharply delineated. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a concise, actionable recipe-style skill that provides concrete commands for creating a Google Tasks list with initial tasks. Its main weakness is the lack of explicit guidance on capturing the TASKLIST_ID from step 1's output and no validation that operations succeeded, which is a gap for a multi-step workflow involving API calls.
Suggestions
Add an explicit note after step 1 to capture the TASKLIST_ID from the response, e.g., 'Extract the `id` field from the response to use as TASKLIST_ID in subsequent steps.'
Add a brief validation checkpoint, such as verifying the task list was created before adding tasks, or noting expected response indicators of success.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what Google Tasks is or how APIs work. Every line serves a purpose with concrete commands. | 3 / 3 |
Actionability | Fully concrete, copy-paste ready commands with specific JSON payloads and parameters. Each step has an executable command with realistic example data. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and logical, but there's no validation or error handling. The TASKLIST_ID placeholder is used in steps 2-4 without explicitly stating to capture it from step 1's response, which could cause confusion. No feedback loop for verifying task creation succeeded. | 2 / 3 |
Progressive Disclosure | For this simple, single-purpose skill under 50 lines, the structure is appropriate. It has a clear prerequisite reference to the gws-tasks skill and well-organized sequential steps. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%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
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.