agentleFS
Sign inStart free
dmzoneilldmzoneill/skills/schedule-meeting/SKILL.md

schedule-meeting

Skill2 starsChanged 22 days agoApache-2.0View on GitHub

Schedule a meeting by finding mutual availability and creating a calendar event. Uses Google Calendar API. Use when user says "schedule meeting", "find time", or "book a meeting".

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Time selection: Use preferred_time if provided.

    line 54
  2. Very specific:

    OAuth: If "unauthorized" or "token" in output → learn_tool_fix("google_calendar_schedule_meeting", "oauth token", "Token expired", "Run …

    line 55

“Common” is measured: kept by at least 6 in 10 of the 6 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

Schedule Meeting

Find available time slots and create a Google Calendar event. Requires meetings persona for google_calendar_* tools.

Inputs

InputTypeDefaultPurpose
titlestringrequiredMeeting title
duration_minutesint30Meeting duration
attendeesstring-Comma-separated emails
preferred_timestring-e.g. "tomorrow 2pm", "next Monday morning"
days_aheadint5Days to search for slots
descriptionstring""Meeting agenda

Workflow

1. Load Persona

  • persona_load("meetings") — Google Calendar tools

2. Check Known Issues

  • check_known_issues("google_calendar", "")

3. Verify Calendar

  • google_calendar_status — verify API accessible

4. Get Availability

  • With attendees: google_calendar_check_mutual_availability(attendee_email=attendees, days_ahead, duration_minutes)
  • Without attendees: google_calendar_check_mutual_availability(attendee_email="primary", days_ahead, duration_minutes)

5. List Existing Events (optional)

  • google_calendar_list_events(days=days_ahead) — busy times

6. Create Meeting

  • google_calendar_quick_meeting(title, attendee_email=attendees or "", when=selected_time, duration_minutes)

7. Post-Action

  • memory_session_log("Scheduled meeting: {title}", "Time: {selected_time}, Duration: {duration_minutes}min")

Key Details

  • Time selection: Use preferred_time if provided; else first available slot from mutual availability
  • OAuth: If "unauthorized" or "token" in output → learn_tool_fix("google_calendar_schedule_meeting", "oauth token", "Token expired", "Run setup-gmail to refresh OAuth")
  • Output: Report success with title, time, duration, attendees; or list alternatives if no slot found

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