gws-workflow-email-to-task
Google Workflow: Convert a Gmail message into a Google Tasks entry.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill gws-workflow-email-to-task59
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
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 identifies a specific integration between Gmail and Google Tasks, which provides some clarity on its purpose. However, it lacks a 'Use when...' clause, covers only a single action, and misses common trigger terms users might naturally use like 'email' or 'to-do'. The description needs explicit trigger guidance and broader keyword coverage.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to create a task from an email, convert Gmail messages to to-dos, or add email items to their task list'
Include natural keyword variations users would say: 'email', 'task', 'to-do', 'reminder', 'action item'
Consider expanding capabilities or clarifying if this handles related actions like viewing tasks, updating task status, or working with multiple emails
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Workflow) and describes one specific action (convert Gmail to Google Tasks), but only lists a single capability rather than multiple concrete actions. | 2 / 3 |
Completeness | Describes what it does (convert Gmail to Tasks) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Gmail', 'Google Tasks', and 'message' that users might say, but missing common variations like 'email', 'task', 'to-do', 'reminder', or 'convert email to task'. | 2 / 3 |
Distinctiveness Conflict Risk | The specific Gmail-to-Tasks conversion is fairly distinct, but 'Google Workflow' prefix is generic and could overlap with other Google-related skills; lacks explicit triggers to differentiate. | 2 / 3 |
Total | 7 / 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 well-structured, concise skill that effectively documents a CLI workflow command. Its main weakness is the lack of concrete implementation details showing how the email-to-task conversion actually works, and the user confirmation step is mentioned but not integrated into a clear workflow sequence.
Suggestions
Add a brief code snippet or API call sequence showing how the message is read and task is created, making the implementation more transparent
Integrate the user confirmation step into a numbered workflow sequence (e.g., '1. Fetch message, 2. Display preview, 3. Confirm with user, 4. Create task')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting only essential information without explaining concepts Claude already knows. Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | Provides concrete CLI commands and flag documentation, but lacks executable code showing the actual implementation or API calls. The 'Tips' section describes behavior rather than showing how it works. | 2 / 3 |
Workflow Clarity | The workflow is simple (single command), but the user confirmation step mentioned in Tips is not integrated into a clear sequence. For an operation that creates tasks, explicit validation/confirmation flow would strengthen this. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear one-level-deep references to prerequisite (gws-shared) and related skills (gws-workflow). Content is appropriately scoped for a single-purpose workflow skill. | 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.