Skip to content
skillsafebeta
← Report library
Purpose / Other

Recipe Plan Weekly Schedule Skill Security Audit

What the author says it does (original text)

Review your Google Calendar week, identify gaps, and add events to fill them.

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

Full agenda content is read into the session running the Skill

Source references: 4
What we found

The workflow calls the agenda command both before and after the change, although the free/busy query can identify open periods by itself. An agenda can expose more scheduling context than busy intervals require. The provided source does not show transmission to an outside recipient.

Why this matters

Event titles and other agenda details may enter the agent context, terminal output, or associated logs and become subject to those environments' retention and access policies.

Legitimate use of this code

The agenda commands would expose calendar details to the agent executing the Skill, but that access directly matches the stated purpose of reviewing the week, finding gaps, and checking the updated schedule. The two reads serve planning and post-write verification rather than clearly unrelated collection. The supplied source contains no instruction to transmit the agenda to a third party, save it, or read other weeks. A user who only wants busy intervals exposed can restrict execution to free/busy queries, but the evidence does not show additional disclosure.

This assessment concerns the code and conditions shown, not proof that harm has occurred.
SKILL.md:24In the instructionsOpen original file
1. Check this week's agenda: `gws calendar +agenda`2. Check free/busy for the week: `gws calendar freebusy query --json '{"timeMin": "2025-01-20T00:00:00Z", "timeMax": "2025-01-25T00:00:00Z", "items": [{"id": "primary"}]}'`3. Add a new event: `gws calendar +insert --summary 'Deep Work Block' --start '2026-01-21T14:00:00' --end '2026-01-21T16:00:00'`
Show 3 other places
SKILL.md:27In the instructionsOpen original file
3. Add a new event: `gws calendar +insert --summary 'Deep Work Block' --start '2026-01-21T14:00:00' --end '2026-01-21T16:00:00'`4. Review updated schedule: `gws calendar +agenda`
SKILL.md:20In the instructionsOpen original file
Review your Google Calendar week, identify gaps, and add events to fill them.
SKILL.md:25In the instructionsOpen original file
1. Check this week's agenda: `gws calendar +agenda`2. Check free/busy for the week: `gws calendar freebusy query --json '{"timeMin": "2025-01-20T00:00:00Z", "timeMax": "2025-01-25T00:00:00Z", "items": [{"id": "primary"}]}'`3. Add a new event: `gws calendar +insert --summary 'Deep Work Block' --start '2026-01-21T14:00:00' --end '2026-01-21T16:00:00'`
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.Risks found: 1
Medium risk

A hard-coded event can be written without confirmation and outside the checked date range

Source references: 2
What we found

The workflow executes event creation without asking the user to choose a gap, verify the time zone, or approve the write. The availability query covers January 20–25, 2025, while the event is created on January 21, 2026, so the query does not establish that the inserted time is free.

Why this matters

Running the step could add an unwanted event to the user's primary calendar or conflict with an existing 2026 commitment. The incorrect entry could also affect reminders, displayed availability, and scheduling decisions.

These are live execution steps, not an example or warning. The workflow queries availability for January 20–25, 2025, then directly creates a fixed event on January 21, 2026. Because the dates do not overlap, the query cannot establish that the inserted time is free. The source also does not require confirmation of the date, time, or timezone. If followed, it could add an unintended event to the user's primary calendar. The user can ask that candidate slots come from the query and that calendar, timezone, start, and end be confirmed before writing.

SKILL.md:25In the instructionsOpen original file
1. Check this week's agenda: `gws calendar +agenda`2. Check free/busy for the week: `gws calendar freebusy query --json '{"timeMin": "2025-01-20T00:00:00Z", "timeMax": "2025-01-25T00:00:00Z", "items": [{"id": "primary"}]}'`3. Add a new event: `gws calendar +insert --summary 'Deep Work Block' --start '2026-01-21T14:00:00' --end '2026-01-21T16:00:00'`4. Review updated schedule: `gws calendar +agenda`
Show 1 other places
SKILL.md:26In the instructionsOpen original file
2. Check free/busy for the week: `gws calendar freebusy query --json '{"timeMin": "2025-01-20T00:00:00Z", "timeMax": "2025-01-25T00:00:00Z", "items": [{"id": "primary"}]}'`3. Add a new event: `gws calendar +insert --summary 'Deep Work Block' --start '2026-01-21T14:00:00' --end '2026-01-21T16:00:00'`4. Review updated schedule: `gws calendar +agenda`

Inside this skill

1 instruction sections

The Skill requires `gws-calendar` and uses `gws` to access the user's Google Calendar; its prerequisite indicates reliance on an existing calendar integration and the associated account permissions.

View source
SKILL.md:9In the instructionsOpen original file
    domain: "scheduling"    requires:      bins:        - gws      skills:        - gws-calendar---
SKILL.md:18In the instructionsOpen original file
> **PREREQUISITE:** Load the following skills to execute this recipe: `gws-calendar`

The workflow reads the weekly agenda and free/busy status, directly creates a two-hour event named “Deep Work Block,” and then reads the agenda again.

View source
SKILL.md:24In the instructionsOpen original file
1. Check this week's agenda: `gws calendar +agenda`2. Check free/busy for the week: `gws calendar freebusy query --json '{"timeMin": "2025-01-20T00:00:00Z", "timeMax": "2025-01-25T00:00:00Z", "items": [{"id": "primary"}]}'`3. Add a new event: `gws calendar +insert --summary 'Deep Work Block' --start '2026-01-21T14:00:00' --end '2026-01-21T16:00:00'`4. Review updated schedule: `gws calendar +agenda`
Start here · InstructionsSKILL.md
recipe-plan-weekly-schedule
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
Lines read
29
File checksum (to compare versions)
c9042140860800fd941f4e8b76ef5faaf372c89d07dd70bf582f91ba1e907eb2