agentleFS
tre-systemstre-systems/office-assistant/.claude/skills/check-availability/SKILL.md

check-availability

Skill1 starsChanged 9 months agoMITView on GitHub

Check free/busy status for one or more people. Use when the user asks if someone is free, busy, available, or what their availability looks like.

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. Distinctive:

    Check people's availability using their Office 365 free/busy schedule.

    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 no time range is given, default to the current business day (9am-5pm) in the user's timezone.

    line 44
  6. Very specific:

    Call get_free_busy with the parameters.

    line 46
  7. Very specific:

    If the user wants to book a slot based on the results, offer to create the meeting using create_event.

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Check people's availability using their Office 365 free/busy schedule.

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 email addresses and time range from the request. Convert relative dates (today/tomorrow/next week) into exact calendar dates in that timezone.
  3. If no time range is given, default to the current business day (9am-5pm) in the user's timezone.
  4. Call get_free_busy with the parameters.
  5. Present results clearly for each person:
    • Their scheduled items with times and status (free/busy/tentative/out of office)
    • A plain-English summary: "Alice is free from 10-11am and 2-4pm. Bob is in meetings until 3pm."
  6. If the user wants to book a slot based on the results, offer to create the meeting using create_event.

Note: This tool requires a work/school Microsoft 365 account. Personal Microsoft accounts (outlook.com, hotmail.com, live.com) cannot check other people's availability. If the user is on a personal account (timezone is null from get_my_profile), explain this limitation.

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.