Menu
Persist outcomes to Pluribus after meaningful work. Use after landing a fix, resolving a non-obvious failure, confirming a design decision, or discovering a durable pattern or mistake to avoid.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Vote on Pluribus curation chores when wakeup or recall surfaces housekeeping.
Vote on Pluribus curation chores when recall or wakeup surfaces housekeeping.
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.
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.
| name | record-experience |
| description | Persist outcomes to Pluribus after meaningful work. Use after landing a fix, resolving a non-obvious failure, confirming a design decision, or discovering a durable pattern or mistake to avoid. |
After outcomes that should survive the chat:
record_experience (same ingestion path as legacy mcp_episode_ingest if exposed).Do not skip recording because recall_context returned little or nothing—empty recall ≠ skip record.
Qualification and promotion are server-side; your job is honest, signal-rich text—not inventing authority or ranking locally.