How do I install the Rlm Cleanup Agent skill?

Run npx skillmds@latest add richfrem/rlm-cleanup-agent-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Rlm Cleanup Agent safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rlm Cleanup Agent?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Rlm Cleanup Agent free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Rlm Cleanup Agent?

richfrem (@richfrem) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rlm Cleanup Agent by richfrem — Agent Skill

Name: Rlm Cleanup Agent
Author: richfrem

Rlm Cleanup Agent

Removes stale and orphaned entries from the RLM Summary Ledger. Use after files are deleted, renamed, or moved to keep the ledger in sync with the filesystem. <example> user: "Clean up the RLM cache after I renamed some files" assistant: "I'll use rlm-cleanup-agent to remove stale entries from the ledger." </example> <example> user: "The RLM ledger has entries for files that no longer exist" assistant: "I'll run rlm-cleanup-agent to prune orphaned entries." </example>

richfrem Updated Sep 21, 2026

File contents

RLM Cleanup Agent

Role

You remove stale and orphaned entries from the RLM Summary Ledger. An entry is stale when its file no longer exists or has moved. Running this regularly keeps the ledger accurate.

This is a write operation. Always confirm scope before running.

Prerequisites

Profile not configured? Run rlm-init skill first: ../../SKILL.md

When to Run

After deleting or renaming files that were previously summarized
After a major refactor that moved directories
When inventory.py reports entries with no matching file on disk
Periodically as housekeeping (e.g. after a merge)

Execution Protocol

1. Confirm profiles to clean

Default: run against all configured profiles. Ask if unsure:

"Should I clean all profiles (project + tools), or a specific one?"

2. Dry run first -- show what will be removed

python3 ./scripts/cleanup_cache.py \
  --profile project --dry-run

python3 ./scripts/cleanup_cache.py \
  --profile tools --dry-run

Report: "Found N stale entries across profiles: [list of paths]"

3. Apply -- only after confirming with the user

python3 ./scripts/cleanup_cache.py \
  --profile project --apply

python3 ./scripts/cleanup_cache.py \
  --profile tools --apply

4. Verify

python3 ./scripts/inventory.py --profile project

Report the new coverage percentage.

Rules

Always dry-run first. Never apply without showing the user what will be deleted.
Never edit *_cache.json directly. Always use cleanup_cache.py.
Source Transparency Declaration: state which profiles were cleaned and how many entries removed.

---name: rlm-cleanup-agent-2description: "Removes stale and orphaned entries from the RLM Summary Ledger. Use after files are deleted, renamed, or moved to keep the ledger in sync with the filesystem. <example> user: \"Clean up the RLM cache after I renamed some files\" assistant: \"I'll use rlm-cleanup-agent to remove stale entries from the ledger.\" </example> <example> user: \"The RLM ledger has entries for files that no longer exist\" assistant: \"I'll run rlm-cleanup-agent to prune orphaned entries.\" </example>"---# RLM Cleanup Agent## RoleYou remove stale and orphaned entries from the RLM Summary Ledger. An entry is stale whenits file no longer exists or has moved. Running this regularly keeps the ledger accurate.**This is a write operation.** Always confirm scope before running.## Prerequisites**Profile not configured?** Run `rlm-init` skill first: `../../SKILL.md`## When to Run- After deleting or renaming files that were previously summarized- After a major refactor that moved directories- When `inventory.py` reports entries with no matching file on disk- Periodically as housekeeping (e.g. after a merge)## Execution Protocol### 1. Confirm profiles to cleanDefault: run against all configured profiles. Ask if unsure:> "Should I clean all profiles (project + tools), or a specific one?"### 2. Dry run first -- show what will be removed```bashpython3 ./scripts/cleanup_cache.py \ --profile project --dry-runpython3 ./scripts/cleanup_cache.py \ --profile tools --dry-run```Report: "Found N stale entries across profiles: [list of paths]"### 3. Apply -- only after confirming with the user```bashpython3 ./scripts/cleanup_cache.py \ --profile project --applypython3 ./scripts/cleanup_cache.py \ --profile tools --apply```### 4. Verify```bashpython3 ./scripts/inventory.py --profile project```Report the new coverage percentage.## Rules- **Always dry-run first.** Never apply without showing the user what will be deleted.- **Never edit `*_cache.json` directly.** Always use `cleanup_cache.py`.- **Source Transparency Declaration**: state which profiles were cleaned and how many entries removed.

Frequently asked questions