Offlyn Clipper Meeting Recap

Problem

When OpenClaw handles meeting-related questions, it can confuse live meeting content with saved notes. If a user asks catch me up or what did I miss, calling note search first returns old material instead of the current call recap. This skill connects Offlyn Clipper's local MCP interface to OpenClaw, so the assistant can route real-time meeting requests away from historical context.

How It Works

The core capabilities are a small set of tools:
- clipper_catch_me_up: for current meeting recap, such as 'catch me up' or 'what did I miss.'
- clipper_search_notes: only for saved notes, project background, or prior thinking, not live calls.
- clipper_list_chat_presets: offers 2–4 suggestion chips at the start of a Clipper-related chat, then follows the preset's recommended tool.
- clipper_ping: checks bridge health and whether a live meeting is active.
- clipper_get_note_context: fetches one note by UUID; use raw body only when the user has granted access.

The routing rule is explicit: for live-meeting phrasing, call clipper_catch_me_up first. If it returns no_active_meeting, tell the user to start or resume recording in Offlyn Clipper and retry. If the MCP tool list looks stale, run a health check and recover through a fresh OpenClaw session rather than guessing tools in the current thread.

Boundaries And Caveats

• The skill depends on the local Clipper process running on Mac; MCP works over a local socket.
• Tool visibility is controlled in Clipper settings, and selected tools can be disabled under Integrations → Shared with OpenClaw.
• This is not a cloud note-sync service or a meeting recorder; it fixes the routing problem of how OpenClaw should call local Clipper tools.