mcpField
L
lossless-claw

lossless-claw

github.com/martian-engineeringAgent workflows4.9k813 installsUpdated 1d ago
Repository

About lossless-claw

A reference skill for operating, tuning, and debugging the lossless-claw OpenClaw plugin. It guides users to relevant commands and documentation for diagnostics, recall, configuration, and session lifecycle questions.

Key features

  1. 01Guidance for plugin configuration
  2. 02Health checks with /lossless and /lcm
  3. 03Summary diagnostics with /lossless doctor
  4. 04Recall-tool usage guidance
  5. 05Session lifecycle reference guidance

Use cases

  1. 01Check LCM summary health
  2. 02Investigate plugin failures using logs
  3. 03Review safe cleanup recommendations
  4. 04Understand /new and /reset behavior

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/martian-engineering/lossless-claw --skill lossless-claw

After installing, type/lossless-clawin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
architecture.md
config.md
diagnostics.md
recall-tools.md
session-lifecycle.md

Details

From the project README

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.

Comments

Markdown supported