coralswarm-connectlisted

# CoralSwarm Connect — set up session capture Goal: after running this skill, the user's sessions are wired to their CoralSwarm ocean so that (a) a coding session with a harness primer may do **one** `ask_ocean` for this project — not a hunt on every turn — and (b) meaningful work is saved back into the ocean **throughout the session**, at natural checkpoints — never waiting for the session to end. This runs entirely on the CoralSwarm MCP's existing OAuth connection. It installs no credentials and needs no backend changes — the capture is performed by the connected agent calling the `add_context` write tool. Supported harnesses receive reminders from `hooks/run.mjs`. Enable the plugin in **one** manager only. ## Choose the setup path - **Claude Code, Cursor, or Codex:** follow the setup steps below. Before the first save, read [Saving work](../coralswarm/SKILL.md#saving-work) for the note/session decision, stable IDs, call examples, retries, and confirmation criteria. - **Custom bot with an MCP connection:** read that same save contract and the [Agent sessions](#agent-sessions-session_kindagent) section below. Keep IDs in the bot's conversation/run state and invoke `add_context` at milestones. Verify the first real checkpoint using the contract's confirmation steps. Hooks are useful only if the bot runs in a supported harness that fires them. - **Tools already connected and asked only to save context:** use [Saving work](../coralswarm/SKILL.md#saving-work) d