Skip to content
skillsafebeta
← Report library
Purpose / Other

Recipe Block Focus Time Skill Security Audit

What the author says it does (original text)

Create recurring focus time blocks on Google Calendar to protect deep work hours.

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

Verification may read agenda details unrelated to the new block

Source references: 1
What we found

After creating the event, the workflow invokes the general `gws calendar +agenda` command instead of querying the newly created event by identifier. The provided instructions do not restrict its date range or event scope.

Why this matters

Titles, times, or scheduling details from other calendar events could enter the agent context, command output, or associated logs beyond what is needed to verify one Focus Time event.

What this evidence establishes

The verification command has no visible event ID, date range, or other filter, so it might read calendar entries beyond the newly created block. However, the source does not define `+agenda` defaults or its output, so the extent of unrelated access cannot be established. Reading calendar data is also relevant to verification, and there is no evidence that results are sent to a third party. The user can ask for lookup by the created event ID or explicit limits on agenda dates and returned fields.

This assessment concerns the code and conditions shown, not proof that harm has occurred.
SKILL.md:25In the instructionsOpen original file
1. Create recurring focus block: `gws calendar events insert --params '{"calendarId": "primary"}' --json '{"summary": "Focus Time", "description": "Protected deep work block", "start": {"dateTime": "2025-01-20T09:00:00", "timeZone": "America/New_York"}, "end": {"dateTime": "2025-01-20T11:00:00", "timeZone": "America/New_York"}, "recurrence": ["RRULE:FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR"], "transparency": "opaque"}'`2. Verify it shows as busy: `gws calendar +agenda`
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

Creates an indefinite recurring busy block in the primary calendar without confirmation

Source references: 2
What we found

The step directly inserts into the `primary` calendar using a fixed January 20, 2025 start date, America/New_York time zone, and Monday-to-Friday rule. The recurrence has no end date, and the workflow does not require confirmation of the user’s dates, time zone, workdays, or authorization to create it.

Why this matters

Execution could continuously reserve 09:00–11:00 every weekday in the wrong time zone or on unsuitable dates, affecting availability, meeting scheduling, and automations that depend on calendar free/busy status.

This is an active write to the primary calendar, not an example or warning. It uses a fixed, already-past start date, New York time, and a Monday–Friday recurrence with no COUNT or UNTIL, so it may create indefinitely recurring busy blocks. Creating focus time matches the stated purpose, but the text does not first confirm the user's dates, time zone, workdays, or consent to modify the primary calendar. This could distort availability and booking decisions. The user can require a preview and confirmation of these parameters and an explicit recurrence end.

SKILL.md:24In the instructionsOpen original file
1. Create recurring focus block: `gws calendar events insert --params '{"calendarId": "primary"}' --json '{"summary": "Focus Time", "description": "Protected deep work block", "start": {"dateTime": "2025-01-20T09:00:00", "timeZone": "America/New_York"}, "end": {"dateTime": "2025-01-20T11:00:00", "timeZone": "America/New_York"}, "recurrence": ["RRULE:FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR"], "transparency": "opaque"}'`2. Verify it shows as busy: `gws calendar +agenda`
Show 1 other places
SKILL.md:20In the instructionsOpen original file
Create recurring focus time blocks on Google Calendar to protect deep work hours.

Inside this skill

1 instruction sections

The Skill’s live workflow creates a recurring weekday “Focus Time” event directly in the user’s primary Google Calendar and marks the time as busy; it does not merely produce a suggestion or draft.

View source
SKILL.md:24In the instructionsOpen original file
1. Create recurring focus block: `gws calendar events insert --params '{"calendarId": "primary"}' --json '{"summary": "Focus Time", "description": "Protected deep work block", "start": {"dateTime": "2025-01-20T09:00:00", "timeZone": "America/New_York"}, "end": {"dateTime": "2025-01-20T11:00:00", "timeZone": "America/New_York"}, "recurrence": ["RRULE:FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR"], "transparency": "opaque"}'`2. Verify it shows as busy: `gws calendar +agenda`

Execution depends on the `gws` command and the `gws-calendar` Skill with Google Workspace calendar capability, then reads the agenda to verify that the event appears as busy.

View source
SKILL.md:9In the instructionsOpen original file
    domain: "scheduling"    requires:      bins:        - gws      skills:        - gws-calendar---
SKILL.md:25In the instructionsOpen original file
1. Create recurring focus block: `gws calendar events insert --params '{"calendarId": "primary"}' --json '{"summary": "Focus Time", "description": "Protected deep work block", "start": {"dateTime": "2025-01-20T09:00:00", "timeZone": "America/New_York"}, "end": {"dateTime": "2025-01-20T11:00:00", "timeZone": "America/New_York"}, "recurrence": ["RRULE:FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR"], "transparency": "opaque"}'`2. Verify it shows as busy: `gws calendar +agenda`
Start here · InstructionsSKILL.md
recipe-block-focus-time
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
27
File checksum (to compare versions)
5671d4ff9fea3c9a52e4104861040e46c4d1c3c128b8602c98ace2421a34c9d5