drmoisan
drmoisan/open-claw-bridge
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/drmoisan/open-claw-bridge --skill mailbridge-admin命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
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.
基于 SOC 职业分类
正在显示 SKILL.md
| 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} |