lossless-claw

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

Ir a la instalación

Repositorio: 100yenadmin/lossless-claw
Última actividad en el origen: 2 de julio de 2026 a las 17:43
Idioma detectado de SKILL.md: inglés
Estrellas: 0
Forks: 0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

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

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos

6 archivos

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

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.