Find meeting times through Superhuman by checking existing events and participants' availability. Present options with clear time zones, then create the event after the user chooses a slot, or update an existing meeting.
Find a time and put a meeting on the calendar through Superhuman — read what is already booked, check the participants' availability, propose slots, and create the event only once the user picks one. Use when the user asks what is on their calendar, when they are free, to find a time with someone, or to schedule, move, or set up a call.
Review the instructions the agent will receive before you install.
An invite reaches every attendee the moment the event is created, so the order is fixed: know the user's calendar, find slots, show them, and create the event only once a slot is chosen.
query_email_and_calendar answers "what is on my calendar Thursday", "when is
my next call with Acme", and "am I free Friday afternoon". It reads mail and
calendar together, so it also finds the thread where a meeting was proposed.
The account matters: list_accounts first, and ask with acting_email when
the meeting belongs to an inbox other than the primary one.
get_availability takes participant emails, a window, and a duration, and
returns free slots. Pass timezone when the user named one or the participants
span zones, and write the window as RFC3339 with an offset, because a bare date
is a guess. It keeps to 9 to 5 in the user's zone by default; set
working_hours_only: false when the user asked for evenings or another zone's
hours.
Offer two or three slots with the day, time, and zone written out, and stop.
create_or_update_event needs title, start, end, and timezone. Add
attendees for the people to invite, conference: true for a video link, a
description with context from the thread, and location for anything in
person. Attendees go on the event only when the user asked to invite them,
because the invite goes out on creation. Pass event_id to move or edit an
event. A recurrence can only be set when the event is created, and editing a
recurring event changes its first occurrence only. A new event takes up to a
minute to show up in queries, so do not re-query to confirm it.
Report the event as created: title, time with zone, attendees, and whether a conference link was added.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Review how you use Superset and identify unused features that fit your workflow. Get a short list of suggestions, learn about each option, and set up selected features such as scheduled agents, parallel workspaces, or shared tasks.
Set up recurring tasks in Superset with an agent prompt, a schedule or event trigger, and a chosen execution workspace. After explicit confirmation, create the automation, check its saved settings, and review a real first run.
Browse pages, click controls, fill fields, and inspect screenshots or console messages through Superset's browser pane. Use it to preview a running web app, check interface behavior, and work through browser tasks in a visible session.
Build Stripe payments, subscriptions, and invoicing using verified documentation and API parameter definitions. The skill guides product selection, sandbox testing, and webhook handling, where server notifications determine payment and subscription state.
Verify desktop UI changes through the Chrome DevTools Protocol, a connection for controlling the running app. Reproduce the user’s actual steps and compare screenshots, measured state, and console errors to establish evidence before and after a fix.
Diagnose failed GitHub Actions runs by finding the first meaningful error, separating code problems from infrastructure issues and intermittent failures, and comparing the base branch. Get a focused report explaining the PR’s involvement and recommended next steps.