context-preservation-protocollisted

<overview> # Context Preservation Best Practices Storing work documentation and context before stopping is recommended to ensure continuity between sessions. The patterns in this skill help you structure, store, and preserve your work results in the context server. </overview> <thread_id> # How to Obtain Thread ID The thread ID is used as `thread_id` for context server queries. Obtain it using the following search chain: 1. **Already available** -- If the thread ID is provided via context or prompt, use it directly 2. **Thread ID file** -- Check `.context_server/.thread_id` in the project working directory 3. **Project directory name** -- If no thread ID file exists, derive the thread identifier from the project directory basename using the git remote URL fallback chain described below. Using the project name ensures all agents working on the same project write to the same thread, which is essential for multi-agent coordination </thread_id> <tools> # Available Context Server Tools **Note:** Not all tools listed below may be available in your environment. Tool availability depends on server configuration and how the server is connected to your MCP client. Use the tools that are available to you. If a recommended tool is unavailable, use an alternative from this table. The tools below cover storage and update. For retrieval and search operations, the context server exposes a parallel set of tools (for example `search_context`, `get_context_by_ids`, `hybrid_search_co