Skip to content
skillsafebeta
← Report library
Purpose / Other

Gws Workflow Email To Task Skill Security Audit

What the author says it does (original text)

Google Workflow: Convert a Gmail message into a Google Tasks entry.

Independent security check

Security risks found

Files checked
1
Risks found
2
Could it run dangerous commands?Looks for programs run straight after downloading, remote control of your computer, and hidden commands.No risks found
Could it expose your files or keys?Looks for uploads of files containing passwords or keys, and keys written directly in the code.Risks found: 1
Low risk

Email subjects and snippets are copied into persistent Google Tasks data

Source references: 2
What we found

The command uses the email subject as the task title and its snippet as task notes, creating another stored copy outside Gmail.

Why this matters

If another person can access the selected task list, Google account, or a later export, they may see sensitive email text. Restricting or deleting the original email does not establish that the task copy was also handled.

The skill explicitly copies the email subject into the task title and the snippet into task notes, then creates a new Google Tasks item. This creates a copy of some email content outside Gmail. The source specifies no retention period, so “long-term” only plausibly means the task persists until deleted, not that any fixed retention is proven. The user should confirm execution and can restrict the selected message and task list.

SKILL.md:31In the instructionsOpen original file
| `--message-id` | ✓ | — | Gmail message ID to convert || `--tasklist` | — | @default | Task list ID (default: @default) |
Show 1 other places
SKILL.md:42In the instructionsOpen original file
- Reads the email subject as the task title and snippet as notes.- Creates a new task — confirm with the user before executing.
Could it delete files or keep running?Looks for broad file deletion, disk overwrites, and programs set to start automatically.No risks found
Could it bypass safety checks?Looks for skipped website security checks, excessive file access, or actions that skip your approval.No risks found
Could it mislead the AI or hide text?Checks the skill instructions for requests to ignore you, influence the report, or hide text in invisible characters.Risks found: 1
Medium risk

Authentication and security behavior depends on an external Skill file not included in this audit

Source references: 2
What we found

The Skill tells the agent to read the adjacent `gws-shared/SKILL.md` and to run a generator if it is absent. That file and the generated result were not supplied, so their authentication, global-flag, and security instructions cannot be reviewed here.

Why this matters

If the adjacent file has been replaced, or the generator produces unsafe instructions, the agent could handle authentication or subsequent commands according to unaudited rules. The visible evidence does not show that such tampering occurred.

What this evidence establishes

This is an active prerequisite: the agent must read a neighboring shared skill and run a generation command if it is absent. Neither that file nor generated output is included, so its authentication permissions, global flags, security behavior, and generated content cannot be assessed. The user can ask the author to supply the dependency and generated files for review and prohibit automatic generation or execution meanwhile.

This assessment concerns the code and conditions shown, not proof that harm has occurred.
SKILL.md:16In the instructionsOpen original file
> **PREREQUISITE:** Read `../gws-shared/SKILL.md` for auth, global flags, and security rules. If missing, run `gws generate-skills` to create it.
Show 1 other places
SKILL.md:47In the instructionsOpen original file
- [gws-shared](../gws-shared/SKILL.md) — Global flags and auth- [gws-workflow](../gws-workflow/SKILL.md) — All cross-service productivity workflows commands
Could it change links or payment recipients without asking?Looks for forced referral or payment changes combined with instructions to hide the change.No risks found

Inside this skill

5 instruction sections

This Skill invokes `gws` to create a Google Tasks entry from a Gmail message ID, using the default task list unless another list is specified.

View source
SKILL.md:23In the instructionsOpen original file
```bashgws workflow +email-to-task --message-id <ID>```
SKILL.md:30In the instructionsOpen original file
|------|----------|---------|-------------|| `--message-id` | ✓ | — | Gmail message ID to convert || `--tasklist` | — | @default | Task list ID (default: @default) |

The instructions require user confirmation before execution, so task creation is not presented as a silent action.

View source
SKILL.md:43In the instructionsOpen original file
- Reads the email subject as the task title and snippet as notes.- Creates a new task — confirm with the user before executing.
Start here · InstructionsSKILL.md
gws-workflow-email-to-task
Lines connect the instruction file to its sections, not an observed execution order. Select a section to read the source.
Files and check records1 files

Coverage and gaps

Content covered in each file

These are the source ranges included in this check, not a guarantee that every issue has been resolved.

  • SKILL.mdFull text included

This report is for the version above. We read the available code and instructions without running the skill or checking extra packages it installs. This is not a promise of safety: a different version or setup may behave differently.

  • SKILL.mdInstructions

Operations mentioned in code and instructions

Run commands
SKILL.md:22In the instructionsOpen original file
```bashgws workflow +email-to-task --message-id <ID>
SKILL.md:35In the instructionsOpen original file
```bashgws workflow +email-to-task --message-id MSG_ID
Lines read
49
File checksum (to compare versions)
74a2b9f777539981cef6c1616a69a24046b08e323d27cced70445a1cc0c19262