Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sonichi/meeting-scheduler
Schedule a small meeting end-to-end: resolve attendee emails, check the owner's calendar for the slot, dedup-check, then create + email the Google Calendar invite. The mechanical core only — cross-person availability negotiation stays interactive.
Passed 12 of 17 test cases with the skill, and 7 of 17 without it.
and 5 more in the full report
8 fixed8 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
If no custom timezone flag is provided and the local host environment does not expose an IANA timezone, which fallback timezone string is selected?
| Checked | Without skill | With skill |
|---|---|---|
| Falls back to America/Los_Angeles | Missed | Passed |
The instructions your model reads when the skill loads.
Encapsulates the ~10 manual steps of "set up a quick meeting" into one command: resolve attendee emails → check the owner's calendar for the slot → dedup-check → create the event + send invites → report the link.
Usage: /meeting-scheduler [what to schedule]
ARGUMENTS: $ARGUMENTS
This skill handles the mechanical core only. It does NOT negotiate availability across people — proposing times, collecting "does 3pm work?", juggling everyone's free/busy stays an interactive conversation you have with the owner (and, if asked, the attendees). Once a concrete slot is chosen, this skill does the rote work.
Authority note. Creating and sending a calendar invite is an owner action.
Run the create+send step only when the owner has invoked this skill for a concrete
meeting. Never auto-send speculatively — default to a dry-run and show the plan
first. The helper enforces this: it defaults to --dry-run and only creates with
an explicit --send.
| Input | Required | Notes |
|---|---|---|
| title | yes | Event summary, e.g. "Sutando sync" |
| attendees | yes | Either explicit emails (--attendees) or names to resolve (--resolve) |
| when | yes | Start time — ISO 8601 (2026-07-25T15:00) or today/tomorrow HH[:MM][am/pm] |
| duration | no | Minutes; default 30 |
| location | no | Room, address, or a video link |
| description | no | Agenda / notes |
Emails must come from a Gmail lookup — the identity map
(workspace/.claude-sutando/projects/<slug>/memory/reference_identity_map.md)
resolves a name to a person (and their Discord/GitHub ids) but does not
store email addresses. Use the map to disambiguate who is meant; get the address
from Gmail.
test cases passed, vs 7 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.