Skip to content
cccskills
FreePublished on GitHubEnglish overview

schedule-with-superhuman

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.

OriginalShow the original description

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.

ParadevAI/Paradev15,724 stars(GitHub 15,724 + cccskills 0)

Run score Not tested

See how to install

Good for

  • Check upcoming events and free time
  • Find meeting times across time zones
  • Book a call at a chosen time
  • Reschedule an existing meeting

Overview

What it does

This skill checks calendar events and participant availability through Superhuman. Based on attendee email addresses, meeting length, and the search window, it offers two or three options with the weekday, time, and time zone stated. After you choose a slot, it creates the event. It can also add a video meeting link, an in-person location, or relevant context from an email thread. It can move or edit existing events as well.

When it helps

Use it to check this week’s schedule or find a time to meet with someone in another country. Since it can search email and calendar together, it can also find the conversation where a meeting was proposed.

Example requests

  • “Check when I’m free Friday afternoon.”
  • “Find times for a 30-minute meeting with these two people next week, in Japan time.”
  • “Create a video meeting at the time I chose.”

Notes

This skill uses Superhuman integration tools. Creating an event sends invitations, so the event is created only after you choose a time. The default search looks between 9 a.m. and 5 p.m. in your time zone. Recurrence can be set only when creating an event; editing a recurring event affects only its first occurrence.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Document check

AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).

SafetyAre sending data, deleting files, and running commands disclosed?
AGoodIt states that creation sends invitations and requires slot selection before booking.
Easy setupDoes it need few tools or API keys, and are they documented?
BPartly lackingSuperhuman integration tools are required; setup steps are not provided.

Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 29, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (1)

  • SKILL.md2.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Propose, then book

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.

1. Read the calendar through the question tool

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.

2. Find slots, in the right time zone

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.

3. Create the event once a slot is chosen

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.

Anti-patterns

  • Creating the event to show the user the options. Proposals are text; the event is the booking.
  • Assuming the user's time zone for someone else. Name the zone in every slot.
  • Inviting the whole thread. Attendees are the people the user named.
  • Booking outside the window the user gave. Widen the search only when the user agrees there was nothing inside it.

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

10x

FreeSummary

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.

  • Find unused Superset features worth exploring
  • Set up scheduled agent tasks
  • Start parallel work in separate workspaces
ParadevAI/Paradev15.7KUpdated Oct 29, 2026

automate

FreeSummary

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.

  • Scheduling a daily or weekly agent task
  • Starting agent work when a GitHub pull request opens
  • Triggering tasks from selected Slack reactions
ParadevAI/Paradev15.7KUpdated Oct 29, 2026

browser

FreeSummary

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.

  • Preview a locally running web app
  • Capture screenshots of a page
  • Inspect console errors
ParadevAI/Paradev15.7KUpdated Oct 29, 2026

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.

  • Choose Stripe products for payments or recurring billing
  • Implement Checkout or invoice flows
  • Investigate Stripe code that compiles but behaves incorrectly
ParadevAI/Paradev15.7KUpdated Oct 29, 2026

cdp-verification

FreeSummary

Verify a UI change or reproduce a bug in the running desktop app using the Chrome DevTools Protocol (CDP), a browser debugging interface. Follow the real user journey and compare screenshots with measurements such as route, scroll position, and persisted state.

  • Reproducing a UI bug in the running app
  • Verifying a UI change end to end
  • Checking behavior after a route or workspace switch
ParadevAI/Paradev15.7KUpdated Oct 29, 2026

ci-triage

FreeSummary

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.

  • Investigating failed PR checks
  • Separating intermittent test failures from code defects
  • Checking whether the base branch already fails
ParadevAI/Paradev15.7KUpdated Oct 29, 2026

See all skills by ParadevAI

Report a problem with this skill