菜单
Retrieve durable Pluribus context before substantive work. Use when editing multiple files, changing APIs or schema, debugging failures, handling security or compliance, or any task needing more than two sentences to explain to a teammate.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Vote on Pluribus curation chores when wakeup or recall surfaces housekeeping.
Vote on Pluribus curation chores when recall or wakeup surfaces housekeeping.
Memory loop — recall before work, housekeeping when chores exist, record after outcomes.
Memory loop — recall before work, record after outcomes.
Memory loop — recall before work, record after outcomes.
Check that Pluribus is reachable before relying on memory tools. Use when MCP errors, timeouts, or disconnects appear, or when validating a new install.
| name | recall-context |
| description | Retrieve durable Pluribus context before substantive work. Use when editing multiple files, changing APIs or schema, debugging failures, handling security or compliance, or any task needing more than two sentences to explain to a teammate. |
Before planning or editing:
recall_context (alias memory_context_resolve if your client lists that name).housekeeping or open chores, call resolve_chore with agent_id when you can judge — see skill resolve-chore.retrieval_query or task text that states what you are about to do.recall_bundle / mcp_context and fold constraints and prior failures into your plan.Do not skip recall because the task “seems small” once you have read a few files—if it matches the trigger list above, recall first.
Do not defer recall to “later” on substantive refactors or incidents when Pluribus MCP is available.
Server-side ranking and authority stay on the Pluribus control plane; you only request and apply context.