deploy/docker/openclaw-assistant/skills/mailbridge_admin/SKILL.md
Read Outlook inbox, meeting requests, and calendar from the OpenClaw HostAdapter HTTP API.
npx skillsauth add drmoisan/open-claw-bridge mailbridge_adminInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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} |
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.