Agent Skills › Martian-Engineering/lossless-claw › lossless-claw

lossless-claw

GitHub

指导用户配置、诊断和使用 OpenClaw 的 lossless-claw 插件，涵盖健康检查、日志排查、摘要修复及会话生命周期管理。

skills/lossless-claw/SKILL.md Martian-Engineering/lossless-claw

Trigger Scenarios

需要配置 lossless-claw 插件诊断插件行为或故障查询摘要健康或清理会话

Install

npx skills add Martian-Engineering/lossless-claw --skill lossless-claw -g -y

More Options

Use without installing

npx skills use Martian-Engineering/lossless-claw@lossless-claw

指定 Agent (Claude Code)

npx skills add Martian-Engineering/lossless-claw --skill lossless-claw -a claude-code -g -y

安装 repo 全部 skill

npx skills add Martian-Engineering/lossless-claw --all -g -y

预览 repo 内 skill

npx skills add Martian-Engineering/lossless-claw --list

SKILL.md

Frontmatter

{
    "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:

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 or /reset interacts with LCM, 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 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.