Convert Gmail messages into Google Tasks entries with subject-to-title mapping.
Works with
Extracts email subject as task title and message snippet as task notes
Supports custom task list selection via --tasklist flag; defaults to @default list
Requires Gmail message ID as input; recommends user confirmation before task creation
Depends on gws-shared for authentication and global workflow flags
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
Convert a Gmail message into a Google Tasks entry
gws workflow +email-to-task --message-id <ID>
| Flag | Required | Default | Description |
|---|---|---|---|
--message-id |
✓ | — | Gmail message ID to convert |
--tasklist |
— | @default | Task list ID (default: @default) |
gws workflow +email-to-task --message-id MSG_ID
gws workflow +email-to-task --message-id MSG_ID --tasklist LIST_ID
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongws-workflow-email-to-taskExecute the skills CLI command in your project's root directory to begin installation:
Fetches gws-workflow-email-to-task from googleworkspace/cli and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate gws-workflow-email-to-task. Access via /gws-workflow-email-to-task in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
23.9K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
23.9K
stars
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
shadowcz007/skills
aaronontheweb/dotnet-skills
whyashthakker/agent-skills-marketing
mattpocock/skills
davila7/claude-code-templates
intellectronica/agent-skills
Keeps context tight: gws-workflow-email-to-task is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for gws-workflow-email-to-task matched our evaluation — installs cleanly and behaves as described in the markdown.
We added gws-workflow-email-to-task from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: gws-workflow-email-to-task is focused, and the summary matches what you get after install.
gws-workflow-email-to-task has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend gws-workflow-email-to-task for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
gws-workflow-email-to-task reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in gws-workflow-email-to-task — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
gws-workflow-email-to-task fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
gws-workflow-email-to-task has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 35