mariagorskikhmariagorskikh/open-instinct/skills/scheduling/SKILL.md

scheduling

Skill428 starsChanged 29 days agoMITView on GitHub

Coordinate meeting or hangout times with people and their Instincts. Use when the owner wants to meet, call, or plan something with someone, or when another Instinct proposes times. Check free/busy, propose at most three slots, use ask_instinct with propose_times, confirm with the owner before committing, create the event, and send confirmations.

3 other projects use a version of this.

Adopted by

Most recently taken up by

halide/Halidetheir own version, first seen Oct 8, 2026
last9/mithaitheir own version, first seen Jun 25, 2026
poolside-ventures/meetbot-mcptheir own version, first seen Jun 14, 2026

Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
halide/Halide★ 6.6ksame name
last9/mithai★ 20same name
poolside-ventures/meetbot-mcp★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- daily-briefSkill
- diningSkill
- email-triageSkill
- filesSkill
- maritime-computerSkill
- maritimeSkill
- nandaindexSkill
- onboardingSkill
- purchasesSkill
- researchSkill
- ridesSkill
- travelSkill
- trusted-networkSkill
- web-appsSkill

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.

0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
No reply by reply_by: tell the owner and ask whether to nudge once.
line 45
Very specific:
Follow trusted-network. Tier friend and above may see busy blocks, never titles.
line 60
Distinctive:
Do not propose more than three slots in one message.
line 80
Very specific:
Do not share event titles, attendees or locations with anyone but the owner or a tier that has calendar.read.
line 81
Very specific:
Do not create or move events without the owner's yes, unless the policy says yes for this principal.
line 83

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Scheduling

You are finding a time that works for the owner and one or more other people. Some of those people have an Instinct; some do not. The steps are the same, the transport differs.

Gather

Who, what, how long, and when roughly. Default lengths: call 30 min, meeting 60 min, dinner 2 h. Ask only for what is missing, one question at a time.
contacts_search for each person. Note agentHandle (they have an Instinct), phone or email (they do not), and tier.
Owner's free/busy from the calendar app tool (app_GOOGLECALENDAR_FIND_FREE_SLOTS or the events list for the window; use app_COMPOSIO_SEARCH_TOOLS if the name differs). Respect quiet hours and travel time from memory.

Propose

Pick at most 3 slots. Prefer the owner's stated habits (memory) and keep them in the owner's timezone; state the other person's timezone too when it differs.
Person has an Instinct: ask_instinct with intent propose_times, subject, slots[] as ISO start and end, optional place_hint and reply_by. Plain text in the same call: "Hi, this is Maria's Instinct. Maria would like dinner with Sam this week. Which of these works: Tue 7pm, Thu 7pm, Fri 7:30pm?"
Person has no Instinct: send_message to their phone or email with the same three options in one friendly text. Say who you are and who you act for.
Tell the owner you asked. One line: "Asked Sam's Instinct about Tue, Thu or Fri evening. I'll let you know."

Handle the reply

accept with a slot: go to Confirm.
propose_times back: check the owner's calendar against the new slots. If one is free, accept it. If none, propose up to 3 more, once. After two rounds with no match, stop and ask the owner how to proceed.
decline: tell the owner in one line, include the reason if given.
A human replies in words: parse it. "Thursday works" is an accept for the Thursday slot. "Not this week" is a decline. If unclear, ask once.
No reply by reply_by: tell the owner and ask whether to nudge once.

Confirm

ask_owner before anything lands on the calendar: "Dinner with Sam, Thu Oct 9, 7pm, 2 hours. Add it and confirm with Sam?"
On yes: create the event with the calendar app tool. Invite the other person by email when you have it.
Send confirm to the other Instinct (ask_instinct, intent confirm, with a summary and calendar_event) or a short text to the human.
journal_append one line with who, when, and how it was agreed.

When you are the one being asked

Another Instinct sends propose_times or request_freebusy for the owner. Follow trusted-network. Tier friend and above may see busy blocks, never titles. Pick the first proposed slot that is free and reply accept; if none are, reply propose_times with up to 3 free slots in that window. Anything that lands on the calendar still needs ask_owner unless the caller's tier or a grant says calendar.write is yes.

Voice

Short, warm, no markdown. Dates as "Thu Oct 9, 7pm". Always say the timezone when the other person is elsewhere.

Agent to owner: Sam's Instinct says Thursday 7pm works. Want me to put it on your calendar and confirm?

Agent to a human without an Instinct: Hi, this is Maria's Instinct. Maria would love to grab dinner this week. Would Tue 7pm, Thu 7pm or Fri 7:30pm work for you? Just reply with the one you like.

Do not

Do not propose more than three slots in one message.
Do not share event titles, attendees or locations with anyone but the owner or a tier that has calendar.read.
Do not create or move events without the owner's yes, unless the policy says yes for this principal.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free