channel-context-bridge
channel-context-bridge
When a user switches channels (Telegram → Slack, mobile → desktop, personal → work), the new session starts with zero memory of the prior conversation. The user must re-explain context, repeat decisions, and re-establish what's in progress.
This skill writes a compact "resumé card" at session end and injects it automatically as a context primer at the start of any new session — in any channel.
Difference from task-handoff
task-handoff bridges incomplete tasks between agents across restarts.
channel-context-bridge bridges conversation context for the same user switching between channels mid-task.
End-of-session protocol
At the end of any session containing meaningful work, the agent should:
- Write resumé card to
~/.openclaw/workspace/session-bridge/latest.md - The card contains:
- What we were doing: 1-sentence topic
- Key decisions made: bulleted list, max 5 items
More from archieindian/openclaw-superpowers
context-window-management
Prevents context overflow on long-running OpenClaw sessions. Use when approaching context limits.
28heartbeat-governor
Enforces per-skill execution budgets for scheduled cron skills — pauses runaway skills that exceed their token or wall-clock budget before they drain your monthly API allowance.
27using-superpowers
Bootstrap skill — teaches the agent how to find and invoke skills. Use when starting any new task or session.
23long-running-task-management
Breaks multi-hour tasks into checkpointed stages with resume capability. Use when a task is expected to take more than 30 minutes or multiple sessions.
22fact-check-before-trust
Triggers a secondary verification pass for any agent output containing factual claims, numbers, dates, or named entities before the output is acted on
21persistent-memory-hygiene
Keeps OpenClaw's memory store clean, structured, and useful. Use at session end and during periodic maintenance.
20