agentleFS
tre-systemstre-systems/office-assistant/.claude/skills/schedule-meeting/SKILL.md

schedule-meeting

Skill1 starsChanged 9 months agoMITView on GitHub

Quickly schedule a new meeting. Use when the user wants to create a meeting, send a meeting invite, or book time on a calendar.

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

8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a meeting on the user's Office 365 calendar.

    line 10
  2. Very specific:

    If calling any mcp__office-assistant__* tool returns a "No such tool" or "tool not available" error, the MCP server is not registered with …

    line 22
  3. Distinctive:

    Do NOT attempt to call MCP tools again or use Bash workarounds — the server must be registered first, which requires restarting the …

    line 35
  4. Very specific:

    Call get_my_profile to get the user's timezone.

    line 40
  5. Distinctive:

    If any required info is missing (at minimum: subject and start time), ask.

    line 43
  6. Distinctive:

    Default to a 30-minute meeting if no duration or end time is given.

    line 48
  7. Very specific:

    If the user is scheduling on behalf of someone else (e.g.

    line 53
  8. Distinctive:

    Ask "Shall I go ahead and create this?"

    line 64

“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

Create a meeting on the user's Office 365 calendar.

How to call tools

The office-assistant MCP server is already registered and running. Call tools directly using the mcp__office-assistant__<tool_name> functions available in your tool list. Do NOT use Bash, Python scripts, or subprocess calls to invoke tools. All tool names below use their short form (e.g. get_my_profile); the actual callable tool is always mcp__office-assistant__<short_name>.

If MCP tools are not available

If calling any mcp__office-assistant__* tool returns a "No such tool" or "tool not available" error, the MCP server is not registered with Claude Code.

Tell the user:

The calendar assistant isn't connected yet. To set it up, run this command in your terminal:

cd <project directory> && ./setup.sh

Then start a new conversation and try again.

Replace <project directory> with the actual working directory of this project. Do NOT attempt to call MCP tools again or use Bash workarounds — the server must be registered first, which requires restarting the conversation.

Process

  1. Call get_my_profile to get the user's timezone.
  2. Parse the user's request for: subject, attendees (emails), start time, end time or duration, location, and whether it should be a Teams meeting.
  3. If any required info is missing (at minimum: subject and start time), ask.
    • For recurring meetings, ask about the pattern (daily, weekly, monthly), frequency, and end condition (end date, number of occurrences, or no end).
    • For room bookings (work/school only), use list_rooms to find rooms or ask which room to book.
  4. Default to a 30-minute meeting if no duration or end time is given.
  5. For work/school accounts, default to a Teams meeting (is_online_meeting=true) unless told otherwise. For personal accounts (timezone is null from get_my_profile), always set is_online_meeting=false — Teams meetings are not supported.
  6. If the user is scheduling on behalf of someone else (e.g. "Schedule a meeting for Sarah"), use the user_email parameter with that person's email. This requires delegate access (work/school accounts only).
  7. Show the user a summary:
    • Subject
    • Date and time (in their timezone)
    • Duration
    • Recurrence (if applicable)
    • Attendees (if any)
    • Room (if any)
    • Location or "Teams meeting"
  8. Ask "Shall I go ahead and create this?"
  9. On confirmation, call create_event with the parameters.
  10. Report success: show the created event details including any Teams link.

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.