app-controls
Inspect and drive Poracode itself — the Terminal panel, other threads, projects, workspaces, git, pull requests, and schedules —…
Read an Outlook calendar, find meeting times, and create or move events through the Microsoft 365 MCP server.
$ npx -y skills add Porabuild/Poracode --skill outlook-calendar --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/outlook-calendarContext preview
The summary Claude sees to decide when to auto-load this skill.
Read an Outlook calendar, find meeting times, and create or move events through the Microsoft 365 MCP server.
name: outlook-calendar description: "Read an Outlook calendar, find meeting times, and create or move events through the Microsoft 365 MCP server."
Work with the user's Outlook calendar through the connected `outlook` MCP server.
Get this right or everything else is wrong. Establish the user's time zone before reading or writing anything, and state times in it. When a meeting involves other people, say the time in each relevant zone rather than assuming everyone shares the user's.
Watch for all-day events and multi-day events — they do not behave like timed blocks when you are looking for a gap.
Report the schedule as blocks of committed time and gaps between them, not as a list of API records. Include what the user asked for and skip the rest.
Declined and tentative events are not the same as accepted ones. Say which is which when it affects availability.
A gap on the calendar is not automatically a good time. Respect working hours, leave room around back-to-back meetings, and flag when the only options are early, late, or over lunch.
When you propose slots, give a few concrete options with dates and times, not a description of your search.
Creating, moving, or cancelling an event notifies other people. If the user explicitly asked for the action and gave an exact time, duration, title, and attendee list, perform it. Otherwise confirm only the missing or ambiguous details before writing.
Moving a meeting the user does not organize can be disruptive — say so before doing it rather than after.
Never decline or accept an invitation on the user's behalf unless they asked for that specific response.
State what you found or what you changed, with times in the user's zone. If you could not find a workable slot, say that plainly and show the constraint that blocked it.
After a write, read back the event and verify its organizer, attendees, start, end, recurrence, and time zone. A successful API response without the expected calendar state is not completion.
One window for all your AI coding agents. Run Claude, Codex, OpenCode, Gemini, Antigravity, Cursor, and Copilot side-by-side. Terminal and chat, any layout.
Inspect and drive Poracode itself — the Terminal panel, other threads, projects, workspaces, git, pull requests, and schedules —…
Create a deliberately staged commit from the current worktree with a clear subject and why-focused body. Use when asked to commit…
Commit and push the current worktree and create or update a pull request with an accurate title, description, verification…
Finalize the current worktree through deep review, manual QA, fixes, checks, commit, push, PR creation or update, and merge after…
Open, inspect, interact with, and verify websites or local web apps in Poracode's isolated browser. Use for visible page state,…
Prove a web change actually works by exercising the flow in Poracode's browser and collecting visual, console, and network…