lossless-claw

Configure, diagnose, and use lossless-claw effectively in OpenClaw, with emphasis on key settings, summary health, and recall-tool usage.

Jump to install

Repository: 100yenadmin/lossless-claw
Last source activity: July 2, 2026 at 17:43
Detected SKILL.md language: English
Stars: 0
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/100yenadmin/lossless-claw --skill lossless-claw

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

6 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

Lossless Claw

Use this skill when the task is about operating, tuning, or debugging the lossless-claw OpenClaw plugin.

Start here:

Confirm whether the user needs configuration help, diagnostics, recall-tool guidance, or session-lifecycle guidance.

If they need a quick health check, tell them to run /lossless (/lcm is the shorter alias).

If they are debugging lossless-claw behavior or failures, check the independent Lossless log before the shared OpenClaw gateway log.

If they suspect summary corruption or truncation, use /lossless doctor.

If they want high-confidence junk/session cleanup guidance, use /lossless doctor clean before recommending any deletes.

If they ask how /new, /reset, or /lossless rotate interacts with LCM, read the session-lifecycle reference before answering.

If they ask how to import old or past OpenClaw conversation data into Lossless, read the session-lifecycle reference before answering.

Load the relevant reference file instead of improvising details from memory.

Reference map:

Configuration (complete config surface on current main): references/config.md

Internal model and data flow: references/architecture.md

Diagnostics and summary-health workflow: references/diagnostics.md

Recall tools and when to use them: references/recall-tools.md

/new, /reset, /lossless rotate, and past-session import behavior with current lossless-claw session mapping: references/session-lifecycle.md

Working rules:

Prioritize explaining why a setting matters, not just what it does.

Prefer the native plugin command surface for MVP workflows (/lossless, with /lcm as alias).

Do not assume the Go TUI is installed.

Do not recommend advanced rewrite/backfill/transplant/dissolve flows unless the user explicitly asks for non-MVP internals. If the user specifically asks to import old or past OpenClaw conversation data into Lossless, recommend the packaged session migration CLI instead of TUI backfill/surgery flows.

For exact evidence retrieval from compacted history, guide the user toward recall tools instead of guessing from summaries.

When users compare /lossless to /status, explain that they report different layers: /lossless shows LCM-side frontier/summary metrics, while /status shows the last assembled runtime prompt snapshot.