How do I install the Gcal Browser skill?

Run npx skillmds@latest add berabuddies/gcal-browser in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gcal Browser safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gcal Browser?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gcal Browser free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gcal Browser?

berabuddies (@berabuddies) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gcal Browser by berabuddies — Agent Skill

Name: Gcal Browser
Author: berabuddies

File contents

Use /connect gcal-browser <connection> when the user needs Google Calendar Browser setup or auth repair. The flow opens Google Calendar in the global Puffer browser profile, lets the user sign in, discovers logged-in Google accounts, and saves the accounts selected for monitoring.

Target: $target

Configuration command:

/connect gcal-browser <connection>

Use ConnectorAct for configured Google Calendar Browser connections instead of opening a separate browser session. Google Calendar Browser actions are:

list_events to list visible Calendar agenda rows, optionally filtered by query, title, event_id, url, when, location, and limit.
get_detail to open a monitored event and return the visible event details.
accept to RSVP yes to a Calendar invitation.
deny to RSVP no or decline a Calendar invitation.
requestuserbrowseraction only when the connector needs the user to complete sign-in or approval in the global Puffer browser profile.

Newly observed visible Calendar events are emitted by the subscriber every 30 seconds. Include account with the Google account address when a connection monitors multiple accounts. Event actions need one of event_id, title, or url; call list_events first when you need to discover one. Event payloads emitted by the subscriber include event.id and url.

Connector action examples:

{"connector_slug":"gcal-browser","connection_slug":"gcal-browser","action":"list_events","input":{"account":"cs@agentenv.io","query":"planning","limit":10}}
{"connector_slug":"gcal-browser","connection_slug":"gcal-browser","action":"get_detail","input":{"account":"cs@agentenv.io","event_id":"event-123"}}
{"connector_slug":"gcal-browser","connection_slug":"gcal-browser","action":"accept","input":{"account":"cs@agentenv.io","event_id":"event-123"}}
{"connector_slug":"gcal-browser","connection_slug":"gcal-browser","action":"deny","input":{"account":"cs@agentenv.io","url":"https://calendar.google.com/calendar/event?..."}}

Do not use Gmail action names such as list_emails or draft_reply for Google Calendar Browser. Use only the Calendar action surface above.

---name: gcal-browserdescription: Configure Google Calendar Browser with /connect and use Calendar ConnectorAct actions through the global Puffer browser profile.---Use `/connect gcal-browser <connection>` when the user needs Google CalendarBrowser setup or auth repair. The flow opens Google Calendar in the globalPuffer browser profile, lets the user sign in, discovers logged-in Googleaccounts, and saves the accounts selected for monitoring.Target: $targetConfiguration command:```text/connect gcal-browser <connection>```Use `ConnectorAct` for configured Google Calendar Browser connections insteadof opening a separate browser session. Google Calendar Browser actions are:- `list_events` to list visible Calendar agenda rows, optionally filtered by `query`, `title`, `event_id`, `url`, `when`, `location`, and `limit`.- `get_detail` to open a monitored event and return the visible event details.- `accept` to RSVP yes to a Calendar invitation.- `deny` to RSVP no or decline a Calendar invitation.- `requestuserbrowseraction` only when the connector needs the user to complete sign-in or approval in the global Puffer browser profile.Newly observed visible Calendar events are emitted by the subscriber every 30seconds. Include `account` with the Google account address when a connectionmonitors multiple accounts. Event actions need one of `event_id`, `title`, or`url`; call `list_events` first when you need to discover one. Event payloadsemitted by the subscriber include `event.id` and `url`.Connector action examples:```json{"connector_slug":"gcal-browser","connection_slug":"gcal-browser","action":"list_events","input":{"account":"cs@agentenv.io","query":"planning","limit":10}}{"connector_slug":"gcal-browser","connection_slug":"gcal-browser","action":"get_detail","input":{"account":"cs@agentenv.io","event_id":"event-123"}}{"connector_slug":"gcal-browser","connection_slug":"gcal-browser","action":"accept","input":{"account":"cs@agentenv.io","event_id":"event-123"}}{"connector_slug":"gcal-browser","connection_slug":"gcal-browser","action":"deny","input":{"account":"cs@agentenv.io","url":"https://calendar.google.com/calendar/event?..."}}```Do not use Gmail action names such as `list_emails` or `draft_reply` forGoogle Calendar Browser. Use only the Calendar action surface above.

Frequently asked questions

Gcal Browser