rlm

Solid

Context-as-environment decomposition (Layer B of the RLM integration). Treat a large artifact (file / dir / log) as a REPL/filesystem the root agent greps and slices instead of ingesting — partition it into addressable chunks via query-context.mjs --map, RECURSE sub-agent calls over the relevant chunks under a bounded depth/children/step budget, AGGREGATE (piping competing per-chunk answers through /weigh), then PERSIST the recursion trace. The anti-context-rot move: ADDRESS context, don't dump the whole artifact into the window. Reuses .oh/scripts/ralph.sh (the recursion loop) and .oh/worktrees/ (isolated branches) BY REFERENCE — never edits either. Manual-invoke (spawns agents, burns tokens). TRIGGER when: /rlm invoked, or asked to "answer a question over a huge file/log", "decompose a large artifact", "recurse over chunks", "address context instead of ingesting it", "beat context rot on a long input", "RLM <file> <query>".

AI & Automation 38 stars 3 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 86/100

Stars 20%
53
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# rlm — context-as-environment decomposition The **`/rlm`** skill is Layer B of the harness RLM integration (the plan: `.claude/plans/there-s-a-whole-snappy-crayon.md` § Layer B). It answers a query over an artifact too large to ingest by treating that artifact as an **environment the root agent addresses** — grep/slice/chunk-map — rather than a blob it reads into its context window. It then **recurses** sub-agent calls over the narrowed chunks under a bounded budget, and **aggregates** their structured returns, routing competing candidate answers through `/weigh`. **Single responsibility.** `/rlm` owns *decomposition*; `/weigh` owns *selection*. They compose: `/rlm` fans sub-calls out over chunks, `/weigh` scores/selects among the candidate answers a chunk yields. This skill never re-implements selection — it calls `/weigh`. **Reuse, don't reinvent (load-bearing).** The recursion substrate already exists: | Substrate | Owner | How `/rlm` uses it | |---|---|---| | Recursion **loop** | `.oh/scripts/ralph.sh` | each iteration re-reads disk = the REPL step — **reused by reference, never edited** | | Isolated recursion **branches** | `.oh/worktrees/` (the `/worktrees` skill) | depth-2 sub-trees fork here — **reused by reference, never edited** | | Recursion **budget** | `.oh/agents/advisor.md` | the `Max depth N / Max children per level M / Step budget S` triple — `references/recursion-budget.md` points at it and adds a per-run token ceiling | | Chunk-map **primitive** | `scr...

Details

Author
mifunedev
Repository
mifunedev/openharness
Created
5 months ago
Last Updated
today
Language
TypeScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

rlm-orchestrator

Implement RLM-style (Recursive Language Model) orchestration for complex tasks. This skill should be used when facing large context requirements, multi-part tasks that would benefit from parallel execution, or when context rot is a concern. Automatically decomposes tasks, spawns parallel subagents, aggregates results, and iterates until completion. Inspired by the RLM research paper (arXiv:2512.24601).

47 Updated 1 months ago
belumume
AI & Automation Listed

rlm

Recursive Language Model loop for large-context tasks. Searches Willow KB first via willow_knowledge_search, then chunks file context and dispatches rlm-subcall (Haiku) per chunk if the KB doesn't fully answer. Use when a query spans more context than fits in the session — corpus archaeology, MIGR1 atoms, large log files, Grove history digests.

5 Updated 3 weeks ago
rudi193-cmd
AI & Automation Solid

recursive-decomposition

Decompose dense codebase-wide, multi-document, PDF, and aggregation work even when the input fits the context window, following Recursive Language Models (Zhang, Kraska, Khattab, 2025). Use when the user asks to analyse all files, a whole repo, all docs, large PDFs, or to aggregate or multi-hop across scattered sources. Skip one file, one function, a single needle, or a one-page PDF conversion. Triggers: long context, context rot, large codebase, many files, all files, big document, multi-document, PDF, aggregate, summarize everything, codebase-wide, multi-hop, recursive, sub-agents, map-reduce.

47 Updated today
massimodeluisa