Google Workspace
yc-software/qm
Read and act on the user's Gmail, Google Calendar, and Google Tasks through per-user OAuth.
Google Workflow: Convert a Gmail message into a Google Tasks entry.
Install Gws Workflow Email To Task
$ npx skills add googleworkspace/cli --skill gws-workflow-email-to-task -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install googleworkspace/cli gws-workflow-email-to-task --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/googleworkspace/cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/gws-workflow-email-to-task .claude/skills/gws-workflow-email-to-task && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "gws-workflow-email-to-task" agent skill from https://github.com/googleworkspace/cli/tree/main/skills/gws-workflow-email-to-task into .claude/skills/gws-workflow-email-to-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gws-workflow-email-to-task", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/googleworkspace/cli/tree/main/skills/gws-workflow-email-to-taskType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add googleworkspace/cli --skill gws-workflow-email-to-task -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install googleworkspace/cli gws-workflow-email-to-task --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/googleworkspace/cli.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/gws-workflow-email-to-task .agents/skills/gws-workflow-email-to-task && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "gws-workflow-email-to-task" agent skill from https://github.com/googleworkspace/cli/tree/main/skills/gws-workflow-email-to-task into .agents/skills/gws-workflow-email-to-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gws-workflow-email-to-task", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add googleworkspace/cli --skill gws-workflow-email-to-task -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install googleworkspace/cli gws-workflow-email-to-task --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/googleworkspace/cli.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/gws-workflow-email-to-task .cursor/skills/gws-workflow-email-to-task && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "gws-workflow-email-to-task" agent skill from https://github.com/googleworkspace/cli/tree/main/skills/gws-workflow-email-to-task into .cursor/skills/gws-workflow-email-to-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gws-workflow-email-to-task", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/googleworkspace/cli.git --path skills/gws-workflow-email-to-task--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add googleworkspace/cli --skill gws-workflow-email-to-task -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install googleworkspace/cli gws-workflow-email-to-task --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/googleworkspace/cli.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/gws-workflow-email-to-task .gemini/skills/gws-workflow-email-to-task && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "gws-workflow-email-to-task" agent skill from https://github.com/googleworkspace/cli/tree/main/skills/gws-workflow-email-to-task into .gemini/skills/gws-workflow-email-to-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gws-workflow-email-to-task", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install googleworkspace/cli gws-workflow-email-to-taskInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add googleworkspace/cli --skill gws-workflow-email-to-task -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/googleworkspace/cli.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/gws-workflow-email-to-task .github/skills/gws-workflow-email-to-task && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "gws-workflow-email-to-task" agent skill from https://github.com/googleworkspace/cli/tree/main/skills/gws-workflow-email-to-task into .github/skills/gws-workflow-email-to-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gws-workflow-email-to-task", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add googleworkspace/cli --skill gws-workflow-email-to-task -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install googleworkspace/cli gws-workflow-email-to-task --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/googleworkspace/cli.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/gws-workflow-email-to-task .opencode/skills/gws-workflow-email-to-task && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "gws-workflow-email-to-task" agent skill from https://github.com/googleworkspace/cli/tree/main/skills/gws-workflow-email-to-task into .opencode/skills/gws-workflow-email-to-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gws-workflow-email-to-task", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
gws-workflow-email-to-task- GitHub stars
- 31k
- Token cost
- ~313 tokens
- SKILL.md length
- 85 words
- Files
- 1
- Skills in repo
- 77
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Google Workflow: Convert a Gmail message into a Google Tasks entry.
- Tasks that involve Email management
- SKILL.md covers Usage, Flags, Examples and Tips, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Cloud office suites
What it does
Gws Workflow Email To Task is an agent skill from googleworkspace/cli. Google Workflow: Convert a Gmail message into a Google Tasks entry.
Its SKILL.md is about 310 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Productivity & Automation, covering Email management and Cloud office suites. It works with Google Workspace and Gmail. The repository describes itself as: Google Workspace CLI — one command-line tool for Drive, Gmail, Calendar, Sheets, Docs, Chat, Admin, and more. Dynamically built from Google Discovery Service. Includes AI agent… The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Email management
- Tasks that involve Cloud office suites
Example prompts
- “/gws-workflow-email-to-task”
What it can do on your machine
Read from SKILL.md and the folder at commit a3768d0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Gws Workflow Email To Task loads about 313 tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 85 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from googleworkspace/cli at commit a3768d0, republished under its Apache-2.0 licence (© googleworkspace). 85 words, ~313 tokens.
Download SKILL.mdSave it as
.claude/skills/gws-workflow-email-to-task/SKILL.md (or your agent's skills folder).- name
- gws-workflow-email-to-task
- description
- Google Workflow: Convert a Gmail message into a Google Tasks entry.
- metadata.version
- 0.22.5
workflow +email-to-task
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
Usage
gws workflow +email-to-task --message-id <ID>Flags
| Flag | Required | Default | Description |
|---|---|---|---|
--message-id | ✓ | — | Gmail message ID to convert |
--tasklist | — | @default | Task list ID (default: @default) |
Examples
gws workflow +email-to-task --message-id MSG_ID
gws workflow +email-to-task --message-id MSG_ID --tasklist LIST_IDTips
- Reads the email subject as the task title and snippet as notes.
- Creates a new task — confirm with the user before executing.
See Also
- gws-shared — Global flags and auth
- gws-workflow — All cross-service productivity workflows commands
© googleworkspace, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/gws-workflow-email-to-task of googleworkspace/cli.
Open the folder on GitHubat commit a3768d0
Compare with similar skills
Gws Workflow Email To Task next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Gws Workflow Email To Task this skillgoogleworkspace/cli | 31k | — | ~313 | Automated safety check: Pass | Apache-2.0 | |
| Google Workspaceyc-software/qm | 15k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Gogtrpc-group/trpc-agent-go | 1.9k | 15 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Googleletta-ai/lettabot | 327 | — | ~774 | Automated safety check: Notes | Apache-2.0 | |
| Gsuite Setupswyxio/skills | 175 | — | ~951 | Automated safety check: Pass | MIT | |
| Xs Google Workspacekaraage0703/ai-assistant-workspace | 136 | — | ~691 | Automated safety check: Pass | MIT |
Similar skills
Gog
trpc-group/trpc-agent-go
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
Google
letta-ai/lettabot
Google Workspace CLI (gog) for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
Gsuite Setup
swyxio/skills
Configure or audit Google Workspace (formerly G Suite) organization settings for open collaboration, user autonomy, external sharing, Groups privacy, Gmail delegation, Calendar, Meet, Chat, Drive…
Xs Google Workspace
karaage0703/ai-assistant-workspace
gogcli経由でGmail・Google Drive・Google Calendarを操作するスキル。複数Googleアカウント対応。「メールチェック」「メール確認して」「Driveにアップロード」「Driveのファイル」「Gmailで検索」で使用。
Gws
glebis/claude-skills
This skill should be used when interacting with Google Workspace services via the gws CLI — Gmail (search, triage, send, labels, filters, drafts), Calendar (agenda, events, Meet conferencing), Drive…
More from googleworkspace/cli
All 77 skills in this repoGmail Inbox Watcher
googleworkspace/cli
Streams new Gmail messages as NDJSON from the gws command line tool using Google Pub/Sub, with label filters, batch settings and optional per-message files.
Workspace Events Subscribe
googleworkspace/cli
Subscribes to Google Workspace events with the gws CLI and streams them as NDJSON, with flags for the target resource, event types, Pub/Sub project and output directory.
Gmail Message Forwarder
googleworkspace/cli
Forwards an existing Gmail message to new recipients from the command line with the gws CLI, with options for notes, attachments, CC, BCC and drafts.
Gmail Reply via gws
googleworkspace/cli
Replies to a Gmail message from the gws CLI with automatic threading, plus CC, BCC, extra recipients, attachments, HTML bodies and draft or dry-run modes.
Gws Calendar Agenda
googleworkspace/cli
Google Calendar: Show upcoming events across all calendars. An agent skill from googleworkspace/cli.
Gmail Reply-All Command
googleworkspace/cli
Replies to everyone on a Gmail message through the gws CLI, with threading handled automatically, options to add or drop recipients, and a draft mode.
Related
Works with
Questions about Gws Workflow Email To Task
What does Gws Workflow Email To Task do?
Google Workflow: Convert a Gmail message into a Google Tasks entry. Gws Workflow Email To Task is an agent skill from googleworkspace/cli. Google Workflow: Convert a Gmail message into a Google Tasks entry.
When should I use Gws Workflow Email To Task?
Gws Workflow Email To Task fits situations like: tasks that involve Email management; tasks that involve Cloud office suites.
How do I install Gws Workflow Email To Task in Claude Code?
Run `npx skills add googleworkspace/cli --skill gws-workflow-email-to-task -a claude-code`. Or copy the skill folder (skills/gws-workflow-email-to-task in googleworkspace/cli) into .claude/skills/gws-workflow-email-to-task in your project. Claude Code loads it when a task matches its description.
How do I install Gws Workflow Email To Task in Codex?
Run `npx skills add googleworkspace/cli --skill gws-workflow-email-to-task -a codex`. Or copy the skill folder (skills/gws-workflow-email-to-task in googleworkspace/cli) into .agents/skills/gws-workflow-email-to-task in your project. Codex loads it when a task matches its description.
Can I use Gws Workflow Email To Task in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add googleworkspace/cli --skill gws-workflow-email-to-task -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gws-workflow-email-to-task, .gemini/skills/gws-workflow-email-to-task, .github/skills/gws-workflow-email-to-task and .opencode/skills/gws-workflow-email-to-task in your project.
What does Gws Workflow Email To Task need to run?
SKILL.md names no scripts, command-line tools or credentials: Gws Workflow Email To Task is instructions for the agent only.
Does Gws Workflow Email To Task access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Gws Workflow Email To Task safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Gws Workflow Email To Task use?
Gws Workflow Email To Task is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Gws Workflow Email To Task use?
About 313 tokens (SKILL.md is roughly 1.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Gws Workflow Email To Task?
Skills that share tags, products or a category with Gws Workflow Email To Task: Google Workspace (yc-software/qm, 15k stars), Gog (trpc-group/trpc-agent-go, 1.9k stars), Google (letta-ai/lettabot, 327 stars) and Gsuite Setup (swyxio/skills, 175 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Gws Workflow Email To Task?
googleworkspace (a GitHub organization) maintains it in googleworkspace/cli, which has 31,280 GitHub stars. The repository holds 77 skills in this directory. The repository was last updated on October 6, 2026.
Source: googleworkspace/cli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.