Menu
Read Outlook inbox, meeting requests, and calendar from the OpenClaw HostAdapter HTTP API.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/drmoisan/open-claw-bridge --skill mailbridge-adminThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
Execute a previously planned epic by replaying the committed epic-kickoff artifact through the epic-orchestrator agent. Use after /epic-plan has prepared the epic (issues, folders, research, specs, atomic plans, preflight clearance) and the user is ready to execute end-to-end.
Feature-branch review workflow for base-branch resolution, PR-context refresh, active feature folder selection, review artifact generation, validator gates, acceptance-criteria check-off, and remediation triggers. Use when authoring or executing PR-style feature reviews.
Resolve PRBaseBranch for VS Code command: `drm-copilot: Collect PR Context` (command ID: `drmCopilotExtension.collectPrContext`) using merge-base ancestry. Use when orchestrators or review workflows need the correct comparison base branch and must select the branch with the most recent common ancestor commit with HEAD.
Based on SOC occupation classification
| name | mailbridge_admin |
| description | Read Outlook inbox, meeting requests, and calendar from the OpenClaw HostAdapter HTTP API. |
| metadata | {"openclaw":{"os":["windows"]}} |
Use this skill whenever the operator asks about inbox items, meeting requests, scheduling conflicts, calendar analysis, or drafting an administrative response.
GET /v1/status on the HostAdapter. If the bridge is not ready, stop and report the bridge state.GET /v1/messages?since=<utc>&limit=<n>GET /v1/meeting-requests?since=<utc>&limit=<n>GET /v1/calendar?start=<utc>&end=<utc>&limit=<n>GET /v1/messages/{bridgeId}GET /v1/events/{bridgeId}isRedacted=true or the bridge mode is safe, state that details are unavailable. Never fabricate sender, body, or attendee details.The following rules apply to every availability or scheduling question. They are mandatory and must be applied in addition to the Required Workflow above.
(a) Render every event time in the operator's local timezone from USER.md, alongside the original UTC value.
(b) Before answering any availability or scheduling question, perform a fresh GET /v1/calendar call covering the relevant time window.
(c) After GET /v1/status, consult meta.bridge.cacheStale; when true, issue a fresh GET /v1/calendar before computing any scheduling answer.
(d) Exclude events whose responseStatus == 4 (Declined, OlResponseStatus.olResponseDeclined) from busy holds and from calendar summaries.
(e) Restrict proposed free windows to the operator business-hours range from USER.md; do not propose windows outside that range.
(f) Apply the operator's meeting-tier policy from USER.md; a documented tier-1 request may propose bumping a lower-tier hold (tier-2 or tier-3) with clear rationale.
All requests use base URL http://host.docker.internal:4319/v1 and require:
Authorization: Bearer <token>
Read the token from the file at /run/openclaw/hostadapter.token.
| Endpoint | Pattern |
|---|---|
| Bridge status | GET /v1/status |
| List messages | GET /v1/messages?since=2026-04-11T00:00:00Z&limit=50 |
| Get message | GET /v1/messages/{bridgeId} |
| List meeting requests | GET /v1/meeting-requests?since=2026-04-11T00:00:00Z&limit=50 |
| List calendar events | GET /v1/calendar?start=2026-04-18T00:00:00Z&end=2026-05-02T00:00:00Z&limit=100 |
| Get calendar event | GET /v1/events/{bridgeId} |