Outlook Calendar
SkillProductivityWith the outlook claude skill, lets your agent view, create, update, and delete events in an Outlook calendar.
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the Outlook Calendar skill
About this skill
View, create, update, and delete events in the user's Outlook Calendar.
What this skill tells your AI
The instructions your AI receives, as published by win4r/museai-skills in opt/hatch/skills/outlook-calendar/SKILL.md and read by ahel’s review.
Purpose
Manage Outlook Calendar events with the outlook-calendar companion CLI.
Tooling
Use exec to run the installed CLI directly from PATH.
outlook-calendar --status
outlook-calendar disconnect
outlook-calendar list --page-size 10 [--time-min <RFC3339>] [--time-max <RFC3339>] [--query <text>] [--page-token <token>]
outlook-calendar get "<event_id>"
outlook-calendar create --summary "<title>" --start "<RFC3339-or-date>" --end "<RFC3339-or-date>" --timezone "<iana_tz>" [--attendee <email>] [--location <text>] [--description <text>] [--all-day]
outlook-calendar update "<event_id>" [--summary <title>] [--start <RFC3339>] [--end <RFC3339>] [--timezone <iana_tz>] [--location <text>] [--description <text>]
outlook-calendar delete "<event_id>"
For list, use --page-size for result count. --top, --limit, and
--max-results are compatibility aliases only; do not use them in new
commands. list uses --time-min / --time-max for time bounds. --start
and --end are canonical only for create / update; list accepts them
only as compatibility aliases.
JSON output contract:
disconnect: parseok,action,status, anddisconnect_url.list: parseok,count,next_page_token(when present, pass back as--page-token),retrieved_at, andevents[]with fields such asid,summary,description,start,end,event_starts_at,event_ends_at,location,is_all_day, andattendees.get: parseok,retrieved_at, andevent.create/update: parseok,action,event_id, andweb_link.delete: parseok,action, andevent_id.
Auth
This skill uses the CLI-managed Outlook connector. Do not hand-write auth files.
First-use or reconnect flow:
- Run
outlook-calendar --status. - If the response includes
connect_url, replace<connect_url>with the returned URL and share exactly this Markdown link:[Connect Outlook Calendar](<connect_url>); do not paste the raw URL separately. Wait for the user to finish linking. - Re-run the same status command before continuing.
- If the response includes
disconnect_url, the account is already connected.
For disconnect requests, run outlook-calendar disconnect. When disconnect_url is present, replace <disconnect_url> with the returned URL and share exactly this Markdown link: [Disconnect Outlook Calendar](<disconnect_url>); do not paste the raw URL separately. If it is absent, say the account is already disconnected.
Operating Rules
- Use
listfirst when you need an event ID or when the user asks about a date range. - All timed values must be RFC3339 / ISO 8601. Use date-only values only with
--all-day. - Always supply a valid IANA timezone on
create, and onupdatewhenever start or end times change. - Confirm with the user before creating an event that sends invitations.
- Private event updates may proceed from a clear user request. The helper reads the current event before updating it; organizer-owned meetings with attendees require confirmation because Outlook sends meeting-update email.
- The current helper does not support attendee changes on
update. If the user asks to add or remove invitees on an existing event, explain that limitation instead of emitting an unsupported--attendeeflag. deletemay proceed from a clear, unambiguous user request without an additional confirmation.- Event IDs are opaque Graph values. Reuse the exact
idreturned bylistorget. - Never use the shared connector helper CLI for Outlook Calendar; status and linking must go through
outlook-calendar --status. - Never surface raw Graph identifiers (event ids, calendar ids) or other internal response fields (change keys, page/skip tokens, raw JSON) in text shown to the user — including in summaries, lists, or per-item annotations. Reuse the ids only internally to chain follow-up commands (rule 8). The sole exceptions are when the user explicitly asks for a raw id or you must show one to troubleshoot a failure.
- For timed events, prefer
event_starts_at.user_localandevent_ends_at.user_local; the raw Graph fields remain for compatibility. All-day values are calendar dates, not instants, and must not be timezone-shifted.
Signals
- GitHub stars
- 312
- Forks
- 103
- Last commit
- Sep 2026
Advanced
- Item type
- skill
- Key
outlook-calendar- Source
- github.com/win4r/museai-skills
github.com/win4r/museai-skills
Related picks
Skill · mukul975
The pick for Outlooksocial
Skill · coreyhaines31
More in Productivitygws-calendar
Skill · googleworkspace
More in Productivitylark-workflow-standup-report
Skill · larksuite
More in Productivitywriting-plans
Skill · obra
More in Productivityenergy-procurement
Skill · affaan-m
More in Productivity