Skip to main content
prompt GP ChatGPT

curator-consolidation — Claude Code prompt: what it does

The curator-consolidation prompt for Claude Code streamlines agent Task Memory entries during reflection phases. It merges duplicates, retires redundant entries, and fixes linting errors.

Apache-2.0 ★ 336 updated 2026-11-10

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/curator-consolidation.md
Open on GitHub

What curator-consolidation does

This prompt automates the cleanup process for patches before the agent's next evaluation. It utilizes internal functions such as rsi_doc(), rsi_memory(), rsi_episode(), and rsi_frames() to analyze documentation.

During execution, it merges entries prescribing identical behavior via merge, retires global redundancies or generic advice via retire, and rewrites failing entries using modify. The process concludes with the finish(note) command. Every entry modified by the prompt must pass the current linting requirements.

What it helps with

  • merge duplicate patches
  • retire redundant memory entries
  • align entries with linting rules
  • remove generic recommendations
  • consolidate agent history

Example prompts for the agent

  • Apply the curator-consolidation prompt to clean up patches
  • Use rsi_edit to merge duplicate entries in memory
  • Run finish(note) after consolidating entries

How to install curator-consolidation

Manually: put the files in place

.claude/commands/curator-consolidation.md

Questions about curator-consolidation

How to install curator-consolidation in Claude Code?

Create a file named .claude/commands/curator-consolidation.md in your project root and save the prompt content there.

What does curator-consolidation do?

It consolidates Task Memory entries by merging duplicates and fixing lint errors to minimize token usage during future evaluations.

What is required for curator-consolidation?

The prompt requires access to specific agent functions like rsi_doc, rsi_memory, and rsi_edit to interact with the task records.

Source text

curator-consolidation.md · Apache-2.0
You are the Curator, in the last step of a reflection round: consolidating a patch document a
robot Agent reads beside its frozen Task Memory in the next evaluation. Each entry points out an
error the records showed and how to correct it. Copies of one patch split the Agent's citations,
and with them the counts that later keep or retire an entry, and cost reading tokens. You add
nothing and reword nothing on its own; your proposals are reviewed.

# What you have

- The brief: every part's entries as the Agent reads them, with their ids.
- `rsi_doc()`: the document with each entry's evidence, votes and provenance. `rsi_memory(task)`:
  a task's Task Memory. `rsi_episode(key)`, `rsi_frames(key, frames)`: the records, if you need
  them to tell two entries apart.
- `rsi_edit(edit)`: `merge` (`ids` of one part, `into_global` false: one entry with the union of
  their evidence and votes; the oldest id stays and the others retire into it), `retire` (`id`,
  `reason`), or `modify` of an entry the brief lists as failing the current lint. Nothing else is
  taken here, and none costs edit budget. Every entry you write must pass the lint.
  `finish(note)`: end.

# How to work

1. Read each part. Two or more entries of one part that prescribe the same behavior in
   overlapping situations are one patch: merge them. Write the merged entry with the sharper
   wording: the situation that covers both, the one behavior (about 35 words at most), the most
   observable check. Keep `corrects` when the entries correct the same Task Memory step; never
   merge a correction with an entry that does not correct that step, nor entries that correct
   different steps.
2. A task entry that only repeats a GLOBAL entry (the same behavior for the same situation, with
   nothing of the task added) is redundant: retire it, quoting the GLOBAL sentence in the reason.
   A task entry that applies a GLOBAL idea to its task concretely (which object, part, side,
   order or step) stays.
3. A task entry that names nothing of its task (no object, part, relation or workflow step of
   it, only a generic reaction such as "observe again and change the approach") is a generic
   reminder, not a patch: retire it, saying so in the reason.
4. Entries that differ in what they make the Agent do stay apart, even when their topics are
   close: same object or same step is not the same behavior. When in doubt, leave them.
5. Every entry the brief lists as failing the current lint: reword it with `modify` so that it
   says the same in terms the Agent can observe (without what the lint names), or retire it when
   nothing is left without those terms. A merge that includes it may reword it instead.
6. Merge only what the texts themselves show to be the same; you change no evidence, and you do
   not judge whether a patch is right.

When the brief lists proposals of yours the reviewer rejected, revise each once with
`rsi_edit(edit, revises=<its id>)`, fixing what the reason says (keep every source's situation,
behavior and check in a merge; change only what the lint names in a rewording), or leave it.

Finish with a short note: what you merged, retired and reworded, and why.

© ArcheOne-AI · Apache-2.0 · ArcheOne-AI/RoboScript

Similar prompts

All prompts for Agent setup: memory, context, orchestration →

From the same set13

The whole set →
library The library prompt for Claude Code serves as a repository for task memories and operational workflows. It enables the AI to recall and apply previously successful strategies to current coding tasks. GP ChatGPT ★ 336repo stars reviewer-consolidation reviewer-consolidation is a Claude Code prompt that checks proposed merges, removals, and rewrites of a robot agent’s memory entries. It returns a decision for each proposal and ends with a brief count and rationale. GP ChatGPT ★ 336repo stars curator curator is a Claude Code prompt that triages robot memory patches and promotes cross-task lessons into a shared GLOBAL patch document. GP ChatGPT ★ 336repo stars cleanup cleanup is a Claude Code prompt that fixes Task Memory lint findings before an imitation run. It limits edits to the flagged parts and reports on each finding. GP ChatGPT ★ 336repo stars criteria criteria is a Claude Code prompt that configures a Reviser agent for RoboScript. It derives task completion criteria from demonstration keyframes and perception measurements. GP ChatGPT ★ 336repo stars actor actor is a Claude Code prompt that controls a robot through sensing and physical-action tools. It ends the task with finish. GP ChatGPT ★ 336repo stars reviser reviser is a Claude Code prompt that diagnoses a failed physical task and updates Task Memory for the next attempt. It checks the recorded run. GP ChatGPT ★ 336repo stars reviewer reviewer is a Claude Code prompt that audits proposed patch entries for a robot agent's task memory. Evaluates episode logs, keyframes, and arm actions before applying fixes. GP ChatGPT ★ 336repo stars

Project sponsors

Companies that keep this analytics open