calendar-setup
Skill1 starsChanged 9 months agoMITView on GitHub
Set up or troubleshoot Office 365 calendar authentication. Use when the user needs to log in, authenticate, reconnect, or fix auth issues.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- davekilleen/Dextheir own version, first seen Aug 31, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- davekilleen/Dex★ 509same 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 repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- calendarSkill
- check-availabilitySkill
- find-timeSkill
- schedule-meetingSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 3 are distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
If calling any mcp__office-assistant__* tool returns a "No such tool" or "tool not available" error, the MCP server is not registered with …
- Distinctive: line 36
Do NOT attempt to call MCP tools again or use Bash workarounds — the server must be registered first, which requires restarting the …
- Very specific: line 59
When the .env file already exists but the token has expired, the setup script skips the interactive .env prompts and goes straight to the …
- Very specific: line 63
Run uv run python -m office_assistant.setup in the background with a long timeout (300000 ms / 5 minutes) using run_in_background: true.
- Distinctive: line 76
Search for "App registrations" → click it → "New registration"
- Very specific: line 99
"CLIENT_ID and TENANT_ID must be set": Run uv run python -m office_assistant.setup to create the .env file.
- Distinctive: line 107
"ErrorAccessDenied": Check API permissions in the Azure Portal.
- Very specific: line 111
Want to start fresh?: Run uv run python -m office_assistant.setup — it will detect the expired token and walk you through signing in again.
≈ “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.
Files
Help the user connect their Microsoft account to the calendar assistant.
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.shThis will install dependencies, register the assistant with Claude Code, and walk you through connecting your Microsoft account. Once it's done, 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.
Check current state
First, try calling get_my_profile. If it succeeds, authentication is already
working. Tell the user they're connected and show their name and email.
If authentication fails
Quick setup
Tell the user to run this single command in a terminal:
uv run python -m office_assistant.setupIt will walk them through everything interactively: creating the .env file
and signing in. They just need an Azure App Registration first (see below).
Re-authentication (token expired, .env already exists)
When the .env file already exists but the token has expired, the setup script
skips the interactive .env prompts and goes straight to the device code flow.
In this case you can run it programmatically:
Run uv run python -m office_assistant.setup in the background with a long
timeout (300000 ms / 5 minutes) using run_in_background: true. After it
starts, read its output to get the device code and URL, then show those to
the user. The script blocks until the user completes browser sign-in and caches
the token. Once the background task completes, authentication is restored.
Azure App Registration (one-time prerequisite)
The user needs to create an app in Azure before they can authenticate. Ask first: are you using a work/school account or a personal Microsoft account (outlook.com, hotmail.com, live.com)?
- Go to https://portal.azure.com
- Search for "App registrations" → click it → "New registration"
- Set:
- Name:
Office Assistant - Supported account types:
- Work/school: "Accounts in this organizational directory only"
- Personal: "Personal Microsoft accounts only"
- Redirect URI: leave blank
- Name:
- Click "Register"
- Copy the Application (client) ID from the overview page
- Go to Authentication → set Allow public client flows to Yes → Save
- Go to API permissions → "Add a permission" → Microsoft Graph → Delegated:
- Work/school:
Calendars.ReadWrite,Calendars.ReadWrite.Shared,Place.Read.All,User.Read - Personal:
Calendars.ReadWriteandUser.Readonly - Click "Add permissions"
- Work/school:
Tip: Work/school accounts may need an Azure AD admin to grant consent. If you can't get admin approval, use a personal account instead — it doesn't require any admin.
Then run uv run python -m office_assistant.setup and follow the prompts.
Troubleshooting
- "CLIENT_ID and TENANT_ID must be set": Run
uv run python -m office_assistant.setupto create the.envfile. - "Application is configured for use by Microsoft Account users only" /
"AADSTS9002346": Set
TENANT_ID=consumersin.envfor personal accounts. - Device code expires immediately: The requested scopes may be wrong.
Personal accounts don't support
Calendars.ReadWrite.Shared— make sure you're on the latest code. - "ErrorAccessDenied": Check API permissions in the Azure Portal.
- "Approval required" / admin consent screen: The user's organisation requires admin approval. They can ask their IT admin to grant consent, or use a personal Microsoft account instead.
- Want to start fresh?: Run
uv run python -m office_assistant.setup— it will detect the expired token and walk you through signing in again.
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
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.

