Menu
Configure Google Calendar Browser with /connect and use Calendar ConnectorAct actions through the global Puffer browser profile.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Recipe for rendering a code review as a Canvas — compose findings with evidence and actions into a scannable page instead of a long text answer.
Use when the user asks to create a short drama from a prompt — e.g. "生成短剧", "制作微短剧", "make a short drama", "turn this script into a short drama", "ショートドラマを生成", "숏드라마를 만들어". Orchestrates script, storyboard, optional character images, per-shot video clips, and ffmpeg composition through the existing media tools.
Configure Gmail Browser with /connect and use Gmail ConnectorAct actions through the global Puffer browser profile.
Authenticate Lark with /connect (delegated to the official lark-cli), then send/react/reply through the connector and consume incoming Lark messages as a stream. Two connectors mirror Telegram — lark-login (your user account; monitor + act as you) and lark-bot (the app bot; auto-reply). Use lark-cli directly from Bash for chat/user lookup and any API not exposed as a connector action.
Configure SlackApp or SlackLogin with /connect, then resolve Slack users/channels and search/read Slack messages through the internal CLI.
Configure Telegram with /connect, then resolve Telegram user/group ids and search Telegram messages through the internal Telegram CLI.
| name | gcal-browser |
| description | Configure Google Calendar Browser with /connect and use Calendar ConnectorAct actions through the global Puffer browser profile. |
| allowed-tools | ["Bash"] |
| argument-hint | [Google Calendar Browser task] |
| arguments | target |
| user-invocable | true |
| disable-model-invocation | false |
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.