gws-workflow-email-to-task
Google Workflow: Convert a Gmail message into a Google Tasks entry.
64
56%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gws-workflow-email-to-task/SKILL.mdQuality
Discovery
40%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 clearly identifies a specific integration between Gmail and Google Tasks, giving it good distinctiveness. However, it lacks an explicit 'Use when...' clause and covers only a single action without listing variations or broader capabilities. Adding trigger guidance and more natural user terms would significantly improve skill selection accuracy.
Suggestions
Add a 'Use when...' clause with trigger terms like 'email to task', 'create task from Gmail', 'turn email into todo', 'Gmail to Google Tasks'.
Expand the description to mention related capabilities or variations, such as setting due dates, preserving email links, or handling multiple messages.
Include common user phrasings and synonyms like 'email', 'todo', 'task list', and 'convert' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Workflow) and a specific action (convert Gmail message into Google Tasks entry), but describes only a single action rather than listing multiple concrete capabilities. | 2 / 3 |
Completeness | Describes what the skill does (convert Gmail to Google Tasks) but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also quite thin—so this lands at 1. | 1 / 3 |
Trigger Term Quality | Includes natural keywords like 'Gmail', 'Google Tasks', and 'message', but misses common variations users might say such as 'email to task', 'create task from email', 'todo from Gmail', or 'convert email'. | 2 / 3 |
Distinctiveness Conflict Risk | The description targets a very specific niche—converting Gmail messages to Google Tasks entries—which is unlikely to conflict with other skills due to the narrow, well-defined scope involving two specific Google products. | 3 / 3 |
Total | 8 / 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 is a concise, well-structured skill with good progressive disclosure and clean formatting. However, it lacks explicit workflow sequencing (fetch → parse → confirm → create) and doesn't provide the actual implementation code or API calls needed to execute the conversion, limiting its actionability for Claude.
Suggestions
Add an explicit numbered workflow: 1. Fetch message via Gmail API, 2. Extract subject/snippet, 3. Confirm with user, 4. Create task via Tasks API, 5. Return task ID confirmation.
Include the actual API calls or code snippets showing how to fetch the Gmail message and create the Google Tasks entry, rather than only documenting the CLI surface.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section serves a purpose—flags table, examples, tips—with no unnecessary explanation of what Gmail or Google Tasks are. No wasted tokens. | 3 / 3 |
Actionability | Provides CLI commands and flag descriptions, but lacks the actual implementation details—there's no executable code showing how the Gmail message is fetched, parsed, and converted into a task via API calls. It describes the workflow at a CLI surface level only. | 2 / 3 |
Workflow Clarity | The workflow is implicit rather than explicitly sequenced. There's no clear step-by-step process (fetch email → extract subject/snippet → create task → confirm). The tip mentions confirming with the user but doesn't integrate this into a defined workflow with validation checkpoints. | 2 / 3 |
Progressive Disclosure | Clear overview with well-signaled one-level-deep references to gws-shared and gws-workflow. The prerequisite callout is prominent and the See Also section provides clean navigation to related skills. | 3 / 3 |
Total | 10 / 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
c7c6646
- 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.