agentleFS
mihirkavimihirkavi/open-media/skills/event-planning/SKILL.md

event-planning

Skill1 starsChanged 10 days agoMITView on GitHub

Check availability and travel, and place or release calendar holds for events using Open Media Events. Use when the person asks "am I free?", "hold that", "put it on my calendar", "what am I doing Saturday?", or wants to plan several events across a week.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. cubexteam/claude-sandbox-env★ 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 repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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
  1. Very specific:

    Call check_schedule. Report conflicts (calendar and other Open Media plans), the proposed block including travel, and that travel time is …

    line 13
  2. Very specific:

    If calendar.checked is false, say that existing calendar commitments were not checked.

    line 14
  3. Very specific:

    Ask: "Hold <local block> for <title>?" Only after a clear yes, call plan_event with state: "held" and user_approved: true.

    line 15
  4. Very specific:

    If the person has not subscribed to the plan calendar yet, call get_calendar_feed once and walk them through subscribing.

    line 17
  5. Distinctive:

    When asked for several events in a week ("two events, don't fill every evening"), pick a mix (for example one professional and one …

    line 23
  6. Distinctive:

    Never place a hold without a yes for that specific block.

    line 27
  7. Distinctive:

    Never modify or describe calendar entries that Open Media did not create.

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Event planning

Tools: check_schedule, plan_event, save_event, get_my_events, get_calendar_feed.

Steps

  1. Resolve the event id from the conversation (ids look like evt_…). If it is ambiguous, ask which one.
  2. Call check_schedule. Report conflicts (calendar and other Open Media plans), the proposed block including travel, and that travel time is an estimate.
  3. If calendar.checked is false, say that existing calendar commitments were not checked.
  4. Ask: "Hold <local block> for <title>?" Only after a clear yes, call plan_event with state: "held" and user_approved: true.
  5. Say what happened exactly: a tentative hold on the "Open Media plans" calendar. Holds are not registrations.
  6. If the person has not subscribed to the plan calendar yet, call get_calendar_feed once and walk them through subscribing.
  7. To release a hold, call plan_event with declined (they changed their mind) or cancelled.
  8. For "what am I doing …?", call get_my_events with the date range. Report the plan state, registration label and any detected changes (time, venue, cancellation).

Planning several events

When asked for several events in a week ("two events, don't fill every evening"), pick a mix (for example one professional and one recurring social activity) on different evenings. Check each one, and confirm the set before holding anything.

Rules

  • Never place a hold without a yes for that specific block.
  • Never modify or describe calendar entries that Open Media did not create.
  • "I changed my mind" means declined. Do not claim a provider-side cancellation happened.

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.