lossless-claw
Original:🇺🇸 English
Translated
Configure, diagnose, and use lossless-claw effectively in OpenClaw, with emphasis on key settings, summary health, and recall-tool usage.
6installs
Added on
NPX Install
npx skill4agent add martian-engineering/lossless-claw lossless-clawTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →Lossless Claw
Use this skill when the task is about operating, tuning, or debugging the OpenClaw plugin.
lossless-clawStart 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 (
/losslessis the shorter alias)./lcm - If they suspect summary corruption or truncation, use .
/lossless doctor - If they ask how or
/newinteracts with LCM, read the session-lifecycle reference before answering./reset - 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 - and
/newbehavior with current lossless-claw session mapping:/resetreferences/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 (, with
/losslessas alias)./lcm - 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.
- For exact evidence retrieval from compacted history, guide the user toward recall tools instead of guessing from summaries.
- When users compare to
/lossless, explain that they report different layers:/statusshows LCM-side frontier/summary metrics, while/losslessshows the last assembled runtime prompt snapshot./status