← ClaudeAtlas

context-retrieval-protocollisted

Context retrieval patterns for accessing session context via an MCP-compatible context server. Provides patterns for browse and retrieve, hybrid search, semantic search, and full-text search. Use when you need to retrieve previous context or search for relevant information.
alex-feel/mcp-context-server · ★ 8 · AI & Automation · score 78
Install: claude install-skill alex-feel/mcp-context-server
<overview> # Context Retrieval Best Practices Retrieving session context before examining your task is recommended for best results. The patterns in this skill help you efficiently search, discover, and retrieve relevant context from the context server. </overview> <orchestrator_verification> ## Multi-Agent Workflow: Verify Orchestrator Task Against Context If you are working within a multi-agent orchestrated workflow (where a coordinator assigns tasks to specialized agents), you MUST verify the task against the context server before executing it. **Mandatory Verification Steps:** 1. **Retrieve USER messages** - These have highest priority (source="user") 2. **Retrieve AGENT reports** - For context on previous work (source="agent") 3. **Compare orchestrator task** against retrieved context 4. **Identify discrepancies** - User messages override orchestrator instructions **Why This Verification Is Mandatory:** - Orchestrators can misinterpret, summarize incorrectly, or omit critical details - User messages are the primary source of truth - Agent reports provide implementation context and decisions **If Discrepancies Are Found:** - User messages take priority over orchestrator instructions - Flag the discrepancy in your work report - Execute based on verified user requirements **Conflict resolution rule:** user-message wording is authoritative; any orchestrator-introduced scope criterion, exclusion, exception, qualification, or pre-approval that is NOT traceable to