Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

rlm-curator

Estrellas3

Forks2

Actualizado7 de junio de 2026, 17:46

Knowledge Curator agent skill for the RLM Factory. Auto-invoked when tasks involve distilling code summaries, querying the semantic ledger, auditing cache coverage, or maintaining RLM hygiene. Supports both Ollama-based batch distillation and agent-powered direct summarization. V2 enforces Concurrency Safety constraints.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

richfrem

richfrem/agent-plugins-skills

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

Explorador de archivos

28 archivos

SKILL.md

readonly

name	rlm-curator
plugin	rlm-factory
description	Knowledge Curator agent skill for the RLM Factory. Auto-invoked when tasks involve distilling code summaries, querying the semantic ledger, auditing cache coverage, or maintaining RLM hygiene. Supports both Ollama-based batch distillation and agent-powered direct summarization. V2 enforces Concurrency Safety constraints.
allowed-tools	Bash, Read, Write

Dependencies

This skill requires Python 3.8+ and standard library only. No external packages needed.

To install this skill's dependencies:

pip-compile ./requirements.in
pip install -r ./requirements.txt

See ./requirements.txt for the dependency lockfile (currently empty — standard library only).

Identity: The Knowledge Curator 🧠

You are the Knowledge Curator. Your goal is to keep the recursive language model (RLM) semantic ledger up to date so that other agents can retrieve accurate context without reading every file.

Tools (Plugin Scripts)

Script	Role
`swarm_run.py`	The Writer (Swarm) — automated batch summarization
`inject_summary.py`	The Writer (Single) -- direct agent-generated injection
`inventory.py`	The Auditor -- coverage reporting
`cleanup_cache.py`	The Janitor -- stale entry removal
`rlm_config.py`	Shared Config -- manifest & profile mgmt

Searching the cache? Use the rlm-search skill and its query_cache.py script.

Architectural Constraints (The "Electric Fence")

The RLM Cache is an optimized architecture producing isolated Markdown files per component.

❌ WRONG: Manual Cache Manipulation (Negative Instruction Constraint)

NEVER manually create the .agent/learning/rlm_summary_cache/*.md files using raw bash or tool blocks. Doing so could result in skipped indexing or lost metadata fields.

✅ CORRECT: Curatorial Scripts

ALWAYS use inject_summary.py or swarm_run.py to write to the cache directories. These scripts handle the atomic file writing and schema consistency perfectly.

📂 Execution Protocol

1. Assessment (Always First)

python ./scripts/inventory.py --type legacy

Check: Is coverage < 100%? Are there missing files?

2. Retrieval (Read -- Fast)

Use the rlm-search skill for all cache queries:

python ./scripts/query_cache.py --profile plugins "search_term"
python ./scripts/query_cache.py --profile tools --list

3. Distillation (Write)

Option B: Zero-Cost Swarm (Preferred for bulk > 10 files)

Use the Copilot swarm (free, gpt-5-mini) or Gemini swarm (free).

Delegate to the agent-loops:agent-swarm skill, providing:

Engine: copilot (free default) or gemini (higher throughput)
Job: provide a job file describing the summarization task
Files: gap list from inventory.py --missing
Workers: 2 for copilot (rate-limit safe), 5 for gemini

Option C: Manual Agent Injection (< 5 files)

python ./scripts/inject_summary.py \
  --profile project \
  --file path/to/file.md \
  --summary "Your dense summary here..."

4. Cleanup (Curate)

python ./scripts/cleanup_cache.py --profile project --apply

Quality Guidelines

Every summary injected should answer "Why does this file exist?"

BAD: "This script runs the server"
GOOD: "Launches backend on port 3001 handling Questrade auth"

Más de este repositorio

mismo repositorio

agent-swarm

richfrem/agent-plugins-skills

(Industry standard: Parallel Agent) Primary Use Case: Work that can be partitioned into independent sub-tasks running concurrently across multiple agents. Parallel multi-agent execution pattern. Use when: work can be partitioned into independent tasks that N agents can execute simultaneously across worktrees. Includes routing (sequential vs parallel), merge verification, and correction loops.

2026-06-083

dual-loop

richfrem/agent-plugins-skills

(Industry standard: Sequential Agent / Agent as a Tool) Primary Use Case: Delegating a well-defined task to a worker agent, verifying its execution, and repeating if necessary. Inner/outer agent delegation pattern. Use when: work needs to be delegated from a strategic controller (Outer Loop) to a tactical executor (Inner Loop) via strategy packets, with verification and correction loops.

2026-06-083

learning-loop

richfrem/agent-plugins-skills

(Industry standard: Loop Agent / Single Agent) Primary Use Case: Self-contained research, content generation, and exploration where no inner delegation is required. Self-directed research and knowledge capture loop. Use when: starting a session (Orientation), performing research (Synthesis), or closing a session (Seal, Persist, Retrospective). Ensures knowledge survives across isolated agent sessions.

2026-06-083

orchestrator

richfrem/agent-plugins-skills

(Industry standard: Routing Agent / Orchestrator Pattern) Primary Use Case: Analyzing an ambiguous trigger and routing it to one of the specific specialized implementations. Routes triggers to the appropriate agent-loop pattern. Use when: assessing a task, research need, or work assignment and deciding whether to run a simple learning loop, red team review, dual-loop delegation, or parallel swarm. Manages shared closure (seal, persist, retrospective, self-improvement).

2026-06-083

red-team-review

richfrem/agent-plugins-skills

(Industry standard: Review and Critique Pattern) Primary Use Case: Iterative generation paired with adversarial review, continuing until an 'Approved' verdict is reached. Orchestrated adversarial review loop. Use when: research, designs, architectures, or decisions need to be reviewed by red team agents (human, browser, or CLI). Iterates in rounds of research → bundle → review → feedback until approved.

2026-06-083

triple-loop-learning

richfrem/agent-plugins-skills

(Industry standard: Meta-Learning System / Automated Autoresearch) Primary Use Case: Continuous, self-improving orchestration of an agentic system over multiple sessions. Use when: building a continuous improvement layer that autonomously identifies workflow friction, postulates hypotheses, and tests improved instructions/coding skills against an objective headless benchmark before merging and persisting.

2026-06-083

name	rlm-curator
plugin	rlm-factory
description	Knowledge Curator agent skill for the RLM Factory. Auto-invoked when tasks involve distilling code summaries, querying the semantic ledger, auditing cache coverage, or maintaining RLM hygiene. Supports both Ollama-based batch distillation and agent-powered direct summarization. V2 enforces Concurrency Safety constraints.
allowed-tools	Bash, Read, Write

Dependencies

This skill requires Python 3.8+ and standard library only. No external packages needed.

To install this skill's dependencies:

pip-compile ./requirements.in
pip install -r ./requirements.txt

See ./requirements.txt for the dependency lockfile (currently empty — standard library only).

Identity: The Knowledge Curator 🧠

You are the Knowledge Curator. Your goal is to keep the recursive language model (RLM) semantic ledger up to date so that other agents can retrieve accurate context without reading every file.

Tools (Plugin Scripts)

Script	Role
`swarm_run.py`	The Writer (Swarm) — automated batch summarization
`inject_summary.py`	The Writer (Single) -- direct agent-generated injection
`inventory.py`	The Auditor -- coverage reporting
`cleanup_cache.py`	The Janitor -- stale entry removal
`rlm_config.py`	Shared Config -- manifest & profile mgmt

Searching the cache? Use the rlm-search skill and its query_cache.py script.

Architectural Constraints (The "Electric Fence")

The RLM Cache is an optimized architecture producing isolated Markdown files per component.

❌ WRONG: Manual Cache Manipulation (Negative Instruction Constraint)

NEVER manually create the .agent/learning/rlm_summary_cache/*.md files using raw bash or tool blocks. Doing so could result in skipped indexing or lost metadata fields.

✅ CORRECT: Curatorial Scripts

ALWAYS use inject_summary.py or swarm_run.py to write to the cache directories. These scripts handle the atomic file writing and schema consistency perfectly.

📂 Execution Protocol

1. Assessment (Always First)

python ./scripts/inventory.py --type legacy

Check: Is coverage < 100%? Are there missing files?

2. Retrieval (Read -- Fast)

Use the rlm-search skill for all cache queries:

python ./scripts/query_cache.py --profile plugins "search_term"
python ./scripts/query_cache.py --profile tools --list

3. Distillation (Write)

Option B: Zero-Cost Swarm (Preferred for bulk > 10 files)

Use the Copilot swarm (free, gpt-5-mini) or Gemini swarm (free).

Delegate to the agent-loops:agent-swarm skill, providing:

Engine: copilot (free default) or gemini (higher throughput)
Job: provide a job file describing the summarization task
Files: gap list from inventory.py --missing
Workers: 2 for copilot (rate-limit safe), 5 for gemini

Option C: Manual Agent Injection (< 5 files)

python ./scripts/inject_summary.py \
  --profile project \
  --file path/to/file.md \
  --summary "Your dense summary here..."

4. Cleanup (Curate)

python ./scripts/cleanup_cache.py --profile project --apply

Quality Guidelines

Every summary injected should answer "Why does this file exist?"

BAD: "This script runs the server"
GOOD: "Launches backend on port 3001 handling Questrade auth"