Skip to content
skillsafebeta
← Report library
Purpose / Other

Gws Calendar Insert Skill Security Audit

What the author says it does (original text)

Google Calendar: Create a new event.

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.Risks found: 1
Medium risk

A missing shared instruction file triggers an extra generator command

Source references: 1
What we found

The Skill requires a sibling shared Skill to be read and says to run `gws generate-skills` if it is absent. This execution is not an event-creation parameter step, and the supplied source does not describe what the command generates or changes.

Why this matters

When the shared file is missing, the agent could run an unaudited local generator under the user's permissions before creating the event, causing unspecified environment or file changes.

What this evidence establishes

Line 16 actively directs the agent to run `gws generate-skills` when shared instructions are missing, which may create local files and is separate from inserting one event. However, the supplied source does not show the command's implementation, output scope, permissions, or whether it overwrites anything, so material harm cannot be established. A user can ask for the exact output paths and overwrite behavior and require separate approval before it runs.

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.
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
Medium risk

Incomplete confirmation can place an event in the wrong primary calendar or include unintended attendees

Source references: 3
What we found

`--calendar` is optional and defaults to the primary calendar, while the command accepts multiple attendee addresses, a description, and a location. Although confirmation is required, the Skill does not require the confirmation to show the resolved account, calendar, or complete attendee list.

Why this matters

For users with multiple accounts or calendars, an event containing meeting details and email addresses could be stored in the wrong primary calendar. An incorrect attendee could also receive event information or calendar-related notifications.

What this evidence establishes

The source documents that omitting `--calendar` targets the primary calendar and that attendees may be repeated, so a misunderstood request could affect the wrong calendar or invite unintended people. These are normal, disclosed event-creation features, and the skill explicitly requires confirmation before execution. The alleged incomplete confirmation is not shown, and no actual invocation or confirmation text is provided, so the risk depends on how the skill is used. Users can require confirmation to list the account, calendar, times, and every attendee.

This assessment concerns the code and conditions shown, not proof that harm has occurred.
SKILL.md:30In the instructionsOpen original file
|------|----------|---------|-------------|| `--calendar` | — | primary | Calendar ID (default: primary) || `--summary` | ✓ | — | Event summary/title || `--start` | ✓ | — | Start time (ISO 8601, e.g., 2024-01-01T10:00:00Z) || `--end` | ✓ | — | End time (ISO 8601) || `--location` | — | — | Event location || `--description` | — | — | Event description/body || `--attendee` | — | — | Attendee email (can be used multiple times) || `--meet` | — | — | Add a Google Meet video conference link |
Show 2 other places
SKILL.md:52In the instructionsOpen original file
> [!CAUTION]> This is a **write** command — confirm with the user before executing.
SKILL.md:36In the instructionsOpen original file
| `--description` | — | — | Event description/body || `--attendee` | — | — | Attendee email (can be used multiple times) || `--meet` | — | — | Add a Google Meet video conference link |
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.No risks found
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

The Skill's live purpose is to create a Google Calendar event through `gws`; the title, start time, and end time are required.

View source
SKILL.md:18In the instructionsOpen original file
create a new event## Usage```bashgws calendar +insert --summary <TEXT> --start <TIME> --end <TIME>```

If `--calendar` is omitted, the event is written to the primary calendar. The Skill can also add a location, description, attendee email addresses, and a Google Meet link.

View source
SKILL.md:30In the instructionsOpen original file
|------|----------|---------|-------------|| `--calendar` | — | primary | Calendar ID (default: primary) || `--summary` | ✓ | — | Event summary/title || `--start` | ✓ | — | Start time (ISO 8601, e.g., 2024-01-01T10:00:00Z) || `--end` | ✓ | — | End time (ISO 8601) || `--location` | — | — | Event location || `--description` | — | — | Event description/body || `--attendee` | — | — | Attendee email (can be used multiple times) || `--meet` | — | — | Add a Google Meet video conference link |

The Skill explicitly labels this as a write command and requires the agent to obtain user confirmation before execution.

View source
SKILL.md:52In the instructionsOpen original file
> [!CAUTION]> This is a **write** command — confirm with the user before executing.
Start here · InstructionsSKILL.md
gws-calendar-insert
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 calendar +insert --summary <TEXT> --start <TIME> --end <TIME>
SKILL.md:41In the instructionsOpen original file
```bashgws calendar +insert --summary 'Standup' --start '2026-06-17T09:00:00-07:00' --end '2026-06-17T09:30:00-07:00'
Lines read
59
File checksum (to compare versions)
0b69bcd5f252789db5a201ec83337672c466d41bbf45734e1303e3a417a57afa