/lossless-claw
Configure, diagnose, and use lossless-claw effectively in OpenClaw, with emphasis on key settings, summary health, and recall-tool usage.
$ npx -y skills add martian-engineering/lossless-claw --skill lossless-claw --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/lossless-claw
Context preview
The summary Claude sees to decide when to auto-load this skill.
Configure, diagnose, and use lossless-claw effectively in OpenClaw, with emphasis on key settings, summary health, and recall-tool usage.
SKILL.md
lossless-claw.SKILL.mdname: lossless-claw
description: Configure, diagnose, and use lossless-claw effectively in OpenClaw, with emphasis on key settings, summary health, and recall-tool usage.
Lossless Claw
Use this skill when the task is about operating, tuning, or debugging the `lossless-claw` OpenClaw plugin.
Start here:
1. Confirm whether the user needs configuration help, diagnostics, recall-tool guidance, or session-lifecycle guidance. 2. If they need a quick health check, tell them to run `/lossless` (`/lcm` is the shorter alias). 3. If they are debugging lossless-claw behavior or failures, check the independent Lossless log before the shared OpenClaw gateway log. 4. If they suspect summary corruption or truncation, use `/lossless doctor`. 5. If they want high-confidence junk/session cleanup guidance, use `/lossless doctor clean` before recommending any deletes. 6. If they ask how `/new` or `/reset` interacts with LCM, read the session-lifecycle reference before answering. 7. 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` and `/reset` 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.
- 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.
Read more
name: lossless-claw description: Configure, diagnose, and use lossless-claw effectively in OpenClaw, with emphasis on key settings, summary health, and recall-tool usage.
Lossless Claw
Use this skill when the task is about operating, tuning, or debugging the `lossless-claw` OpenClaw plugin.
Start here:
1. Confirm whether the user needs configuration help, diagnostics, recall-tool guidance, or session-lifecycle guidance. 2. If they need a quick health check, tell them to run `/lossless` (`/lcm` is the shorter alias). 3. If they are debugging lossless-claw behavior or failures, check the independent Lossless log before the shared OpenClaw gateway log. 4. If they suspect summary corruption or truncation, use `/lossless doctor`. 5. If they want high-confidence junk/session cleanup guidance, use `/lossless doctor clean` before recommending any deletes. 6. If they ask how `/new` or `/reset` interacts with LCM, read the session-lifecycle reference before answering. 7. 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` and `/reset` 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.
- 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.
Lossless Context Management plugin for OpenClaw, based on the LCM paper from Voltropy.
Repo: martian-engineering/lossless-claw