lossless-claw

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

Ir para a instalação

Repositório: 100yenadmin/lossless-claw
Última atividade na origem: 2 de julho de 2026 às 17:43
Idioma detectado do SKILL.md: inglês
Estrelas: 0
Forks: 0

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

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

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

6 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

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.