rlm

Process large text and code files exceeding LLM context windows via recursive chunking and sub-agent delegation.

3|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/legout/pi-config --skill rlm-legout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rlm
Source: https://github.com/legout/pi-config/tree/main/skills/rlm
Command: npx skills add https://github.com/legout/pi-config --skill rlm-legout

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of analyzing extremely large documents, logs, or codebases that exceed the standard LLM context window, preventing information loss and truncation errors.

Core Features & Use Cases

  • Recursive Processing: Breaks down massive files into manageable chunks and synthesizes results using sub-LLM agents.
  • Handle-Based Search: Allows efficient exploration of large datasets using token-saving stubs instead of loading full content.
  • Smart Chunking: Automatically detects content types (Markdown, JSON, Code) to split files at logical boundaries rather than arbitrary character counts.

Quick Start

Use the rlm skill to analyze the large log file located at path/to/server.log and answer the user query about connection errors.

Frequently Asked Questions about rlm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze large log files that exceed the standard LLM context window?

To analyze large log files exceeding the LLM context window, use recursive chunking to break massive files into manageable chunks and synthesize results using sub-LLM agents. This prevents information loss and truncation errors during large-scale text processing.

What is the best way to process massive codebases without losing context?

The best way to process massive codebases without losing context is recursive chunking with handle-based search. This method uses token-saving stubs for efficient exploration and parallel sub-LLM invocation to ensure accurate synthesis of large datasets.

How does smart chunking work for different file types like Markdown and JSON?

Smart chunking works by automatically detecting content types like Markdown, JSON, and Code to split files at logical boundaries. This content-aware splitting avoids arbitrary character counts and maintains structural integrity during analysis.

Can I search specific sections of massive documentation without loading the full content?

Yes, you can search specific sections of massive documentation without loading full content by using handle-based search. This technique allows efficient exploration of large datasets using token-saving stubs instead of loading the entire file into the context window.

What are the limitations of using sub-agents for large file analysis?

The limitations of using sub-agents for large file analysis include the complexity of maintaining persistent state across recursive chunks. While parallel sub-LLM invocation synthesizes large datasets accurately, managing context boundaries requires content-aware splitting to avoid logical errors.