context-handoff

What This Skill Does

The context-handoff skill provides a robust mechanism for persisting chat state and project-level information to your local filesystem. Instead of relying on volatile chat history, this skill allows you to explicitly save "snapshots" of your current reasoning, decisions, file references, and upcoming tasks. By decoupling state management from the AI's internal session memory, you gain the ability to switch accounts, clear session windows, or move across different development projects without losing your progress. The skill supports two distinct modes: Session Contexts for specific chat threads and Project Summaries for long-term project tracking. It ensures your workflow remains continuous, organized, and recoverable.

Installation

To install this skill, run the following command in your terminal: clawhub install openclaw/skills/skills/bayllech/context-handoff

Use Cases

1. Cross-Session Continuity: Save your current technical investigation before closing a chat window or switching to a new OpenClaw agent instance. You can easily reload the context later to pick up exactly where you left off.
2. Project Lifecycle Tracking: Maintain a high-level summary of a project's goals, current status, and next steps in a persistent Markdown file that remains available across multiple different conversations.
3. Account Switching: Prepare for a logout or account transition by dumping critical technical state to disk, ensuring that your research or coding progress is archived safely.
4. Structured Documentation: Generate clean, actionable summaries of complex technical discussions, focusing on completed tasks, pending decisions, and critical file paths, rather than raw dialogue logs.

Example Prompts

• "保存当前上下文到 slot 名为 'feature-authentication' 的文件中，我需要切换到另一个账号处理别的任务。"
• "恢复 'data-pipeline-v2' 项目摘要，并告知我目前进展和下一步该做什么。"
• "列出最近更新的会话上下文槽位，我想看看之前做的 'debug-session' 是什么时候保存的。"

Tips & Limitations

• Structure Matters: The skill enforces a structured Markdown format. When saving, avoid including sensitive credentials like API keys or authentication tokens.
• Naming Conventions: Use descriptive slot and project names. If you forget what you have saved, use the list commands to view files sorted by their actual modification time (mtime).
• Storage Paths: Files are saved in /root/.openclaw/workspace/handoffs/sessions/ and /root/.openclaw/workspace/projects/. Ensure your environment has read/write permissions for these paths.
• No Auto-Save: This is an explicit tool; it does not automatically track your every move. You must trigger it via command when you want a checkpoint.
• Override Policy: Default behavior is to overwrite the file with the latest snapshot, keeping your workspace clean rather than cluttered with thousands of iterative logs.