[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K2VREJWTGCZX4B9CQ0AZ2X":3,"skill-same:01M6K2VREJWTGCZX4B9CQ0AZ2X":74},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":57,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M6K2VREJWTGCZX4B9CQ0AZ2X","install-tokenless",null,"Install and configure Tokenless (LLM token optimization toolkit) on Linux or macOS. Use when the user asks to install Tokenless, set up token optimization, reduce LLM token usage, or enable Tokenless for an agent framework (cosh, OpenClaw, Hermes, Qoder, Claude Code, Codex, Qwen Code).","agentic-os-org\u002FANOLISA","agentic-os-org","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F326861446?v=4","01M6K2QGJPXKNJFSPNB3FYW1R3","Agentic OS","01M6K2QGQ6W3S1A9J9DR1G88NZ",665,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fos-skills\u002Fai\u002Finstall-tokenless\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"install tokenless","install","when","openclaw","reduce","for","qwen code","usage","token","qoder","up","use","configure","SET","Optimization","framework","code","toolkit","agent framework","linux","macos","2026-11-10 10:12:30",false,"---\nname: install-tokenless\nversion: 1.0.0\ndescription: Install and configure Tokenless (LLM token optimization toolkit) on Linux or macOS. Use when the user asks to install Tokenless, set up token optimization, reduce LLM token usage, or enable Tokenless for an agent framework (cosh, OpenClaw, Hermes, Qoder, Claude Code, Codex, Qwen Code).\nlayer: application\nlifecycle: usage\n---\n\n# Install Tokenless\n\nTokenless is the token optimization component of ANOLISA. It compresses tool schemas, API responses, and CLI output to reduce LLM token consumption — without changing prompts or agent behavior.\n\n## System Requirements\n\n- **OS**: Linux or macOS. This Skill's Bash workflow requires WSL2 on Windows; native Windows x64 npm installation is documented in the Tokenless user guide.\n- **Architecture**: x86_64 or arm64\n- **Network**: Internet access required\n- **Shell**: Bash\n\nPer-method prerequisites:\n\n| Method | Requires | Installs |\n|--------|----------|----------|\n| A — anolisa CLI | `curl` | full component suite including adapters |\n| B — npm | Node.js 16.7+ with `npm`, glibc Linux or macOS | `tokenless` (0.9.2 and earlier: also `rtk`), adapter resources |\n| C — curl | `curl`, `tar`, plus Node.js 16.7+ **or** a Rust toolchain (`cargo`; after 0.9.2 also `git` and `patch`), depending on the path taken | npm path: as Method B. Source-build path (Linux only): the `tokenless` CLI only |\n| D — Skill | whichever of A\u002FB\u002FC the agent runs | as that method |\n\nThe package postinstall enables the `claude-code` adapter by running that adapter's own `install.sh`, which registers the plugin with the Claude CLI when one is reachable; with no Claude CLI it skips registration and says so. That registration lives in Claude's own configuration, outside both the npm prefix and the adapter directory, so deregister it with the adapter's `uninstall.sh` (or `scripts\u002Funinstall.sh`) rather than by deleting the package.\n\nThe source-build path is validated on Linux only, and the installer refuses it on macOS: there it either takes the npm path or exits with an error, and never runs `cargo`. On musl Linux (Alpine) the source build is the only available path, because prebuilt binaries are glibc-linked.\n\n## Installation Workflow\n\nCopy this checklist and track progress:\n\n```\nTask Progress:\n- [ ] Step 1: Install Tokenless CLI\n- [ ] Step 2: Verify installation\n- [ ] Step 3: Enable for an agent framework (optional)\n- [ ] Step 4: Test compression\n```\n\n### Step 1: Install Tokenless CLI\n\nTry these methods **in order**. Move to the next only if the previous one fails.\n\n**Method A: anolisa CLI (Recommended)**\n\n```bash\ncurl -fsSL https:\u002F\u002Fget.agentic-os.sh | bash\nanolisa install tokenless\n```\n\nThis installs the full ANOLISA component suite including adapters.\n\nOn Alinux with the YUM repository configured, the managed RPM is the alternative\nto this method, and the documented install priority puts it ahead of every route\nbelow:\n\n```bash\nsudo yum install anolisa tokenless\nsudo anolisa --install-mode system adopt tokenless\n```\n\n`adopt` records the directly installed RPM in system state so the adapter commands\ncan use its component contract. Methods B–D create no anolisa component record, so\nprefer Method A or the RPM route whenever either is available.\n\n**Method B: npm Global Install**\n\nRequires Node.js 16.7+ — the release `fs.cpSync` arrived in, which the package postinstall needs to place the adapter resources. Installs prebuilt binaries for your platform:\n\n```bash\nnpm install -g anolisa-tokenless\n```\n\nThis automatically installs the `tokenless` binary plus the framework adapter resources. How RTK, the command rewriter, is installed depends on the release that npm resolves; check it with `tokenless --version`:\n\n- **0.9.2 and earlier:** a separate `rtk` binary is installed next to `tokenless`, which has no `rtk` subcommand.\n- **Releases after 0.9.2:** RTK is linked into `tokenless` and runs as `tokenless rtk`; no `rtk` binary is installed.\n\n(`toon` is no longer a standalone binary — TOON encoding is a `tokenless` subcommand.)\n\nThe adapter resources land in `~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless`, which is shared with the anolisa CLI. Ownership there has to be **proven**, not assumed: the postinstall only refreshes a tree carrying the marker (`.tokenless-owner`) that this package or the standalone curl installer wrote. Anything else is kept unchanged and reported — a managed anolisa component install, a tree left by a release from before the marker existed, or a directory somebody copied by hand — because nothing about its content says who put it there, and every framework registration pointing into it would dangle otherwise. The copy this package ships stays available inside the package under `adapters\u002Ftokenless`; pass `ANOLISA_TOKENLESS_FORCE_ADAPTERS=1` to take the directory over anyway.\n\nThe npm package declares `os: win32, linux, darwin`; prebuilt Linux packages require glibc.\nIntel macOS (x86_64) uses the published `@anolisa\u002Ftokenless-darwin-x64` package.\nMethod A does not cover Intel macOS; use Method B or Method C's npm path there. Do not pass\n`TOKENLESS_FORCE_BUILD=1` on macOS — the installer refuses the source build on that platform and exits with an\nerror instead of running `cargo`. Native Windows x64 can use npm directly, but the remaining Bash\ncommands in this Skill require WSL2.\n\n**Method C: Standalone curl Install**\n\nOne-liner that tries npm first and builds from source instead. The method is chosen **before** npm runs (npm unavailable, musl Linux, or `TOKENLESS_FORCE_BUILD=1`). Once `npm install` has been invoked the installer does not switch method automatically — npm's exit status cannot prove its postinstall left no framework registration behind — so a failure at that stage is reported as an incomplete installation, keeping and naming whatever could not be rolled back. Re-run it, or choose the source build explicitly with `TOKENLESS_FORCE_BUILD=1`:\n\n```bash\ncurl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Falibaba\u002Fanolisa\u002Fmain\u002Fsrc\u002Ftokenless\u002Fscripts\u002Finstall.sh | bash\n```\n\nOptions via environment variables. Pass them to `bash`, not to `curl`, otherwise the installer never sees them:\n\n```bash\n# Pin a specific version\ncurl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Falibaba\u002Fanolisa\u002Fmain\u002Fsrc\u002Ftokenless\u002Fscripts\u002Finstall.sh | TOKENLESS_VERSION=0.7.4 bash\n\n# Custom install directory\ncurl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Falibaba\u002Fanolisa\u002Fmain\u002Fsrc\u002Ftokenless\u002Fscripts\u002Finstall.sh | TOKENLESS_INSTALL_DIR=\u002Fusr\u002Flocal\u002Fbin bash\n\n# Force the source build even when npm is available (needs cargo, and after 0.9.2 git and patch; Linux only)\ncurl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Falibaba\u002Fanolisa\u002Fmain\u002Fsrc\u002Ftokenless\u002Fscripts\u002Finstall.sh | TOKENLESS_FORCE_BUILD=1 bash\n```\n\nA pinned version is a hard pin: the source build downloads only the matching `tokenless\u002Fv\u003CVERSION>` tag, and fails if that tag does not exist. It never falls back to the `main` branch.\n\nThe source-build path installs the `tokenless` CLI only, with no adapter resources. Treat it as a CLI-only install (see Step 3). It runs on Linux only. Without `TOKENLESS_VERSION` it builds the version npm reports as latest.\n\nWhether RTK is part of that build depends on the tag:\n\n- **Releases after 0.9.2** link RTK into `tokenless`. Before building, the installer fetches the pinned RTK source with `git` and `patch` and stops if either is missing.\n- **0.9.2 and earlier**, such as the 0.7.4 example above, build without RTK and need neither tool.\n\nThe installer records every path it created in `~\u002F.local\u002Fshare\u002Ftokenless\u002Finstall-receipt`, which the uninstall step below relies on.\n\n### Step 2: Verify Installation\n\n```bash\ntokenless --version\n```\n\nIf `command not found`, ensure the install directory is in PATH:\n\n```bash\nexport PATH=\"$HOME\u002F.local\u002Fbin:$PATH\"\n```\n\n### Step 3: Enable for an Agent Framework (Optional)\n\nPick the enable path that matches how Step 1 installed Tokenless. Installation only places files on disk; it never registers Tokenless with an agent.\n\n**Installed via Method A (anolisa CLI)** — the component is recorded, so use the adapter commands:\n\n```bash\nanolisa adapter scan\nanolisa adapter enable tokenless \u003Cagent>\nanolisa adapter status tokenless\n```\n\n**Installed via Method B, or via Method C's npm path** — the package postinstall copied the adapters to `~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002F`, but there is **no anolisa component record**, so `anolisa adapter enable` is not available. Run the framework's bundled script instead:\n\n```bash\nls ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002F          # confirm the directory exists\nbash ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002Fclaude-code\u002Fscripts\u002Finstall.sh\n```\n\n**Installed via Method C's source-build path** — CLI-only. No adapter resources were installed, so no adapter can be enabled. Use the `tokenless` subcommands directly, or reinstall through Method A or B for agent integration.\n\n> **Note:** The script paths below are examples for npm-installed adapters. Not all frameworks ship a standalone install script, and directory names may differ. Always check `ls ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002F` first. For anolisa CLI installs, `anolisa adapter enable tokenless \u003Cframework>` is the recommended path.\n\n| Agent | anolisa CLI install | npm-based install |\n|-------|---------------------|-------------------|\n| cosh \u002F Copilot Shell | `anolisa adapter enable tokenless cosh` | no bundled script — cosh integrates through the ANOLISA cosh extension, so use the anolisa CLI path |\n| OpenClaw | `anolisa adapter enable tokenless openclaw` | `bash ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002Fopenclaw\u002Fscripts\u002Finstall.sh` |\n| Hermes | `anolisa adapter enable tokenless hermes` | `bash ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002Fhermes\u002Fscripts\u002Finstall.sh` |\n| Qoder | `anolisa adapter enable tokenless qoder` | `bash ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002Fqoder\u002Fscripts\u002Finstall.sh` |\n| Claude Code | `anolisa adapter enable tokenless claude-code` | `bash ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002Fclaude-code\u002Fscripts\u002Finstall.sh` |\n| Codex | `anolisa adapter enable tokenless codex` | `bash ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002Fcodex\u002Fscripts\u002Finstall.sh` |\n| Qwen Code | `anolisa adapter enable tokenless qwencode` | `bash ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002Fqwencode\u002Fscripts\u002Finstall.sh` |\n\nEach bundled adapter also ships a matching `scripts\u002Funinstall.sh` next to its `install.sh`; use it to disable that framework again. Run it **before** removing the adapter resources — a registration points into that directory, so deleting the directory first leaves the framework hooked, plugged or symlinked to a path that no longer exists. The [Uninstall](#uninstall) section gives the full order per install method.\n\nRestart the agent CLI, IDE, or gateway after enabling.\n\n### Step 4: Test Compression\n\n```bash\nprintf '%s\\n' \\\n  '{\"status\":\"ok\",\"data\":{\"name\":\"demo\",\"items\":[1,2,3]},\"debug\":{\"trace\":\"verbose\"},\"metadata\":null}' \\\n  | tokenless compress-response\n```\n\nIf the output is shorter than the input (debug\u002Fmetadata fields removed), Tokenless is working.\n\nCheck savings after using an agent:\n\n```bash\ntokenless stats list --limit 5\ntokenless stats summary\n```\n\n## Troubleshooting\n\n| Symptom | Fix |\n|---------|-----|\n| `command not found: tokenless` | Add install dir to PATH: `export PATH=\"$HOME\u002F.local\u002Fbin:$PATH\"` |\n| npm install fails with EACCES | Fix npm prefix: `mkdir -p ~\u002F.npm-global && npm config set prefix '~\u002F.npm-global'` |\n| `GLIBC_xxx not found` | Linux binaries require glibc 2.17+. Update: `sudo dnf update glibc` |\n| No stats after enabling | Content may not have passed through Tokenless or had no compressible fields |\n| musl Linux (Alpine) | Prebuilt binaries not available; build from source |\n\n## Uninstall\n\nUninstall must match how Tokenless was installed, and must only remove files that\ninstallation created. Do not run a blanket `rm` across `~\u002F.local\u002Fbin` or the\nadapter tree — those paths may belong to another method.\n\n**anolisa CLI installation (Method A):**\n```bash\nanolisa uninstall tokenless\n```\n\n**Standalone curl installation (Method C):** the installer recorded its method,\nnpm prefix, install directory, and every file it created in\n`~\u002F.local\u002Fshare\u002Ftokenless\u002Finstall-receipt`. Remove exactly those:\n\n```bash\ncurl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Falibaba\u002Fanolisa\u002Fmain\u002Fsrc\u002Ftokenless\u002Fscripts\u002Funinstall.sh | bash\n\n# Preview first, or also delete the runtime data directory:\n#   ... | bash -s -- --dry-run\n#   ... | bash -s -- --purge\n```\n\nThe receipt-driven uninstaller removes the recorded binaries from the recorded\ninstall directory (including a custom `TOKENLESS_INSTALL_DIR`), uninstalls the\nglobal npm package from the recorded prefix when the npm path was used, removes\nthe adapter directory only when that npm run created it, strips only the PATH\nline the installer appended, and leaves `~\u002F.tokenless` (stats and stash data)\nin place unless `--purge` is passed. A source-build install recorded no adapters,\nso none are removed.\n\n`~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless` is shared with the anolisa CLI and\nwith a direct `npm install -g`. When that directory already belonged to another\ninstallation, the npm postinstall leaves it untouched, the curl installer compares\nit against the snapshot it took beforehand and only restores it if something\nreally did replace it, does not record the directory, and says so — the receipt\nthen owns only the launcher links, and this uninstaller leaves the shared\nresources and their framework registrations alone. A snapshot that cannot be taken\nat all stops the run before `npm install -g` replaces anything.\n\nEach recorded file also carries its sha256, and the adapter directory carries the\ndigest of its stamped `manifest.json`. A path whose content no longer matches was\ntaken over by another installer (anolisa, a manual `npm install -g`) and is kept.\nBefore deleting the adapter directory the uninstaller runs each bundled\nframework's own `scripts\u002Funinstall.sh`, so an enabled framework registration is\nremoved rather than left pointing at a deleted directory. If one of them fails,\nthe uninstaller **stops short**: the adapter resources and the receipt are both\nkept and it exits non-zero, so the registration still resolves and the script the\nwarning names still exists. Fix that framework and re-run to finish.\n\nContent alone is not proof of ownership — a newer anolisa or npm install of the\nsame version leaves byte-identical binaries and manifests behind. So the receipt\nalso records this install's id, the link target each launcher resolves to, and an\nownership marker (`.tokenless-owner`) inside the adapter tree and the npm module\ndirectory. A path whose recorded identity or marker no longer matches belongs to\nthat newer install and is kept, including its framework registrations and its npm\npackage.\n\nRe-running the installer with a different method retires the previous receipt, so\nswitching npm → source does not orphan a launcher link, the npm global package\nor the adapter tree — but only once the replacement is verified. The previous\ninstall is moved aside first and put back if the new one fails, so a missing tag,\na build error or an unwritable directory leaves the working install and its\nreceipt exactly as they were. That guarantee is fail-closed: if the copy aside\ncannot be made at all — no staging directory, or a recorded file that cannot be\nread — the installer stops before writing anything instead of replacing an install\nit could not put back. An npm → npm upgrade keeps a copy of the previous\npackage payload for the same reason: the launcher links resolve into it, so a\nbroken new binary is rolled back instead of being left behind a working-looking\nlink. The new receipt is written to a temporary, moved into place and flushed\nbefore anything is retired; when it cannot be written and the previous receipt\ncannot be removed either, the run fails and restores the previous install,\nbecause a stale receipt would let a later uninstall delete the new one. Where the previous npm prefix and the install\ndirectory overlap (`--prefix ~\u002F.local` with `~\u002F.local\u002Fbin`), that package is\nretired by hand instead of through `npm uninstall`, which would otherwise take the\nfreshly installed CLI with it. A failed npm attempt is rolled back the same way,\nso the source-build fallback never inherits an unowned package, launcher link or\nadapter tree.\n\n**Direct npm installation (Method B), not through the curl script:** no receipt\nexists, so undo the three things the install did, in this order. Deregister the\nframeworks enabled in Step 3 **first**, while their resources are still on disk —\notherwise every hook entry, plugin directory and symlink keeps pointing at a\ndirectory that no longer exists:\n\n```bash\n# 1. Once per framework enabled in Step 3 (claude-code, codex, hermes, openclaw,\n#    opencode, qoder, qwencode, qwenpaw).\nbash ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002F\u003Cframework>\u002Fscripts\u002Funinstall.sh\n\n# 2. Remove the global package.\nnpm uninstall -g anolisa-tokenless\n\n# 3. Remove the adapter resources the package postinstall created.\nrm -rf ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\n```\n\nThe uninstaller stops short rather than half-finishing, and exits non-zero when it\ndoes: a framework registration it could not remove keeps the adapter resources and\nthe receipt, and a global npm package it could not remove (no npm on PATH) keeps\nthe package, that prefix's launcher links and the receipt. Fix the cause and\nre-run — the receipt is what makes the retry possible.\n\nThis is the order the receipt-driven uninstaller uses internally, and the order\nthe Tokenless troubleshooting page prescribes for an npm installation. Step 3\nalso removes the resources a Method C npm install writes, so skip it when\nanother Tokenless installation on this machine still needs them — and skip it\nwhenever the postinstall reported that it kept a managed adapter tree, because\nthat directory was never this npm install's to delete.\n\nIf the receipt is missing (for example after a manual cleanup), the uninstaller\nexits with an error rather than guessing; remove `\u003Cinstall-dir>\u002Ftokenless` (and\n`\u003Cinstall-dir>\u002Frtk`, left by releases that shipped it separately) yourself, using\nthe directory you actually installed into.\n","# Install Tokenless\n\nTokenless is the token optimization component of ANOLISA. It compresses tool schemas, API responses, and CLI output to reduce LLM token consumption — without changing prompts or agent behavior.\n\n## System Requirements\n\n- **OS**: Linux or macOS. This Skill's Bash workflow requires WSL2 on Windows; native Windows x64 npm installation is documented in the Tokenless user guide.\n- **Architecture**: x86_64 or arm64\n- **Network**: Internet access required\n- **Shell**: Bash\n\nPer-method prerequisites:\n\n| Method | Requires | Installs |\n|--------|----------|----------|\n| A — anolisa CLI | `curl` | full component suite including adapters |\n| B — npm | Node.js 16.7+ with `npm`, glibc Linux or macOS | `tokenless` (0.9.2 and earlier: also `rtk`), adapter resources |\n| C — curl | `curl`, `tar`, plus Node.js 16.7+ **or** a Rust toolchain (`cargo`; after 0.9.2 also `git` and `patch`), depending on the path taken | npm path: as Method B. Source-build path (Linux only): the `tokenless` CLI only |\n| D — Skill | whichever of A\u002FB\u002FC the agent runs | as that method |\n\nThe package postinstall enables the `claude-code` adapter by running that adapter's own `install.sh`, which registers the plugin with the Claude CLI when one is reachable; with no Claude CLI it skips registration and says so. That registration lives in Claude's own configuration, outside both the npm prefix and the adapter directory, so deregister it with the adapter's `uninstall.sh` (or `scripts\u002Funinstall.sh`) rather than by deleting the package.\n\nThe source-build path is validated on Linux only, and the installer refuses it on macOS: there it either takes the npm path or exits with an error, and never runs `cargo`. On musl Linux (Alpine) the source build is the only available path, because prebuilt binaries are glibc-linked.\n\n## Installation Workflow\n\nCopy this checklist and track progress:\n\n```\nTask Progress:\n- [ ] Step 1: Install Tokenless CLI\n- [ ] Step 2: Verify installation\n- [ ] Step 3: Enable for an agent framework (optional)\n- [ ] Step 4: Test compression\n```\n\n### Step 1: Install Tokenless CLI\n\nTry these methods **in order**. Move to the next only if the previous one fails.\n\n**Method A: anolisa CLI (Recommended)**\n\n```bash\ncurl -fsSL https:\u002F\u002Fget.agentic-os.sh | bash\nanolisa install tokenless\n```\n\nThis installs the full ANOLISA component suite including adapters.\n\nOn Alinux with the YUM repository configured, the managed RPM is the alternative\nto this method, and the documented install priority puts it ahead of every route\nbelow:\n\n```bash\nsudo yum install anolisa tokenless\nsudo anolisa --install-mode system adopt tokenless\n```\n\n`adopt` records the directly installed RPM in system state so the adapter commands\ncan use its component contract. Methods B–D create no anolisa component record, so\nprefer Method A or the RPM route whenever either is available.\n\n**Method B: npm Global Install**\n\nRequires Node.js 16.7+ — the release `fs.cpSync` arrived in, which the package postinstall needs to place the adapter resources. Installs prebuilt binaries for your platform:\n\n```bash\nnpm install -g anolisa-tokenless\n```\n\nThis automatically installs the `tokenless` binary plus the framework adapter resources. How RTK, the command rewriter, is installed depends on the release that npm resolves; check it with `tokenless --version`:\n\n- **0.9.2 and earlier:** a separate `rtk` binary is installed next to `tokenless`, which has no `rtk` subcommand.\n- **Releases after 0.9.2:** RTK is linked into `tokenless` and runs as `tokenless rtk`; no `rtk` binary is installed.\n\n(`toon` is no longer a standalone binary — TOON encoding is a `tokenless` subcommand.)\n\nThe adapter resources land in `~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless`, which is shared with the anolisa CLI. Ownership there has to be **proven**, not assumed: the postinstall only refreshes a tree carrying the marker (`.tokenless-owner`) that this package or the standalone curl installer wrote. Anything else is kept unchanged and reported — a managed anolisa component install, a tree left by a release from before the marker existed, or a directory somebody copied by hand — because nothing about its content says who put it there, and every framework registration pointing into it would dangle otherwise. The copy this package ships stays available inside the package under `adapters\u002Ftokenless`; pass `ANOLISA_TOKENLESS_FORCE_ADAPTERS=1` to take the directory over anyway.\n\nThe npm package declares `os: win32, linux, darwin`; prebuilt Linux packages require glibc.\nIntel macOS (x86_64) uses the published `@anolisa\u002Ftokenless-darwin-x64` package.\nMethod A does not cover Intel macOS; use Method B or Method C's npm path there. Do not pass\n`TOKENLESS_FORCE_BUILD=1` on macOS — the installer refuses the source build on that platform and exits with an\nerror instead of running `cargo`. Native Windows x64 can use npm directly, but the remaining Bash\ncommands in this Skill require WSL2.\n\n**Method C: Standalone curl Install**\n\nOne-liner that tries npm first and builds from source instead. The method is chosen **before** npm runs (npm unavailable, musl Linux, or `TOKENLESS_FORCE_BUILD=1`). Once `npm install` has been invoked the installer does not switch method automatically — npm's exit status cannot prove its postinstall left no framework registration behind — so a failure at that stage is reported as an incomplete installation, keeping and naming whatever could not be rolled back. Re-run it, or choose the source build explicitly with `TOKENLESS_FORCE_BUILD=1`:\n\n```bash\ncurl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Falibaba\u002Fanolisa\u002Fmain\u002Fsrc\u002Ftokenless\u002Fscripts\u002Finstall.sh | bash\n```\n\nOptions via environment variables. Pass them to `bash`, not to `curl`, otherwise the installer never sees them:\n\n```bash\n# Pin a specific version\ncurl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Falibaba\u002Fanolisa\u002Fmain\u002Fsrc\u002Ftokenless\u002Fscripts\u002Finstall.sh | TOKENLESS_VERSION=0.7.4 bash\n\n# Custom install directory\ncurl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Falibaba\u002Fanolisa\u002Fmain\u002Fsrc\u002Ftokenless\u002Fscripts\u002Finstall.sh | TOKENLESS_INSTALL_DIR=\u002Fusr\u002Flocal\u002Fbin bash\n\n# Force the source build even when npm is available (needs cargo, and after 0.9.2 git and patch; Linux only)\ncurl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Falibaba\u002Fanolisa\u002Fmain\u002Fsrc\u002Ftokenless\u002Fscripts\u002Finstall.sh | TOKENLESS_FORCE_BUILD=1 bash\n```\n\nA pinned version is a hard pin: the source build downloads only the matching `tokenless\u002Fv\u003CVERSION>` tag, and fails if that tag does not exist. It never falls back to the `main` branch.\n\nThe source-build path installs the `tokenless` CLI only, with no adapter resources. Treat it as a CLI-only install (see Step 3). It runs on Linux only. Without `TOKENLESS_VERSION` it builds the version npm reports as latest.\n\nWhether RTK is part of that build depends on the tag:\n\n- **Releases after 0.9.2** link RTK into `tokenless`. Before building, the installer fetches the pinned RTK source with `git` and `patch` and stops if either is missing.\n- **0.9.2 and earlier**, such as the 0.7.4 example above, build without RTK and need neither tool.\n\nThe installer records every path it created in `~\u002F.local\u002Fshare\u002Ftokenless\u002Finstall-receipt`, which the uninstall step below relies on.\n\n### Step 2: Verify Installation\n\n```bash\ntokenless --version\n```\n\nIf `command not found`, ensure the install directory is in PATH:\n\n```bash\nexport PATH=\"$HOME\u002F.local\u002Fbin:$PATH\"\n```\n\n### Step 3: Enable for an Agent Framework (Optional)\n\nPick the enable path that matches how Step 1 installed Tokenless. Installation only places files on disk; it never registers Tokenless with an agent.\n\n**Installed via Method A (anolisa CLI)** — the component is recorded, so use the adapter commands:\n\n```bash\nanolisa adapter scan\nanolisa adapter enable tokenless \u003Cagent>\nanolisa adapter status tokenless\n```\n\n**Installed via Method B, or via Method C's npm path** — the package postinstall copied the adapters to `~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002F`, but there is **no anolisa component record**, so `anolisa adapter enable` is not available. Run the framework's bundled script instead:\n\n```bash\nls ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002F          # confirm the directory exists\nbash ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002Fclaude-code\u002Fscripts\u002Finstall.sh\n```\n\n**Installed via Method C's source-build path** — CLI-only. No adapter resources were installed, so no adapter can be enabled. Use the `tokenless` subcommands directly, or reinstall through Method A or B for agent integration.\n\n> **Note:** The script paths below are examples for npm-installed adapters. Not all frameworks ship a standalone install script, and directory names may differ. Always check `ls ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002F` first. For anolisa CLI installs, `anolisa adapter enable tokenless \u003Cframework>` is the recommended path.\n\n| Agent | anolisa CLI install | npm-based install |\n|-------|---------------------|-------------------|\n| cosh \u002F Copilot Shell | `anolisa adapter enable tokenless cosh` | no bundled script — cosh integrates through the ANOLISA cosh extension, so use the anolisa CLI path |\n| OpenClaw | `anolisa adapter enable tokenless openclaw` | `bash ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002Fopenclaw\u002Fscripts\u002Finstall.sh` |\n| Hermes | `anolisa adapter enable tokenless hermes` | `bash ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002Fhermes\u002Fscripts\u002Finstall.sh` |\n| Qoder | `anolisa adapter enable tokenless qoder` | `bash ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002Fqoder\u002Fscripts\u002Finstall.sh` |\n| Claude Code | `anolisa adapter enable tokenless claude-code` | `bash ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002Fclaude-code\u002Fscripts\u002Finstall.sh` |\n| Codex | `anolisa adapter enable tokenless codex` | `bash ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002Fcodex\u002Fscripts\u002Finstall.sh` |\n| Qwen Code | `anolisa adapter enable tokenless qwencode` | `bash ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002Fqwencode\u002Fscripts\u002Finstall.sh` |\n\nEach bundled adapter also ships a matching `scripts\u002Funinstall.sh` next to its `install.sh`; use it to disable that framework again. Run it **before** removing the adapter resources — a registration points into that directory, so deleting the directory first leaves the framework hooked, plugged or symlinked to a path that no longer exists. The [Uninstall](#uninstall) section gives the full order per install method.\n\nRestart the agent CLI, IDE, or gateway after enabling.\n\n### Step 4: Test Compression\n\n```bash\nprintf '%s\\n' \\\n  '{\"status\":\"ok\",\"data\":{\"name\":\"demo\",\"items\":[1,2,3]},\"debug\":{\"trace\":\"verbose\"},\"metadata\":null}' \\\n  | tokenless compress-response\n```\n\nIf the output is shorter than the input (debug\u002Fmetadata fields removed), Tokenless is working.\n\nCheck savings after using an agent:\n\n```bash\ntokenless stats list --limit 5\ntokenless stats summary\n```\n\n## Troubleshooting\n\n| Symptom | Fix |\n|---------|-----|\n| `command not found: tokenless` | Add install dir to PATH: `export PATH=\"$HOME\u002F.local\u002Fbin:$PATH\"` |\n| npm install fails with EACCES | Fix npm prefix: `mkdir -p ~\u002F.npm-global && npm config set prefix '~\u002F.npm-global'` |\n| `GLIBC_xxx not found` | Linux binaries require glibc 2.17+. Update: `sudo dnf update glibc` |\n| No stats after enabling | Content may not have passed through Tokenless or had no compressible fields |\n| musl Linux (Alpine) | Prebuilt binaries not available; build from source |\n\n## Uninstall\n\nUninstall must match how Tokenless was installed, and must only remove files that\ninstallation created. Do not run a blanket `rm` across `~\u002F.local\u002Fbin` or the\nadapter tree — those paths may belong to another method.\n\n**anolisa CLI installation (Method A):**\n```bash\nanolisa uninstall tokenless\n```\n\n**Standalone curl installation (Method C):** the installer recorded its method,\nnpm prefix, install directory, and every file it created in\n`~\u002F.local\u002Fshare\u002Ftokenless\u002Finstall-receipt`. Remove exactly those:\n\n```bash\ncurl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Falibaba\u002Fanolisa\u002Fmain\u002Fsrc\u002Ftokenless\u002Fscripts\u002Funinstall.sh | bash\n\n# Preview first, or also delete the runtime data directory:\n#   ... | bash -s -- --dry-run\n#   ... | bash -s -- --purge\n```\n\nThe receipt-driven uninstaller removes the recorded binaries from the recorded\ninstall directory (including a custom `TOKENLESS_INSTALL_DIR`), uninstalls the\nglobal npm package from the recorded prefix when the npm path was used, removes\nthe adapter directory only when that npm run created it, strips only the PATH\nline the installer appended, and leaves `~\u002F.tokenless` (stats and stash data)\nin place unless `--purge` is passed. A source-build install recorded no adapters,\nso none are removed.\n\n`~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless` is shared with the anolisa CLI and\nwith a direct `npm install -g`. When that directory already belonged to another\ninstallation, the npm postinstall leaves it untouched, the curl installer compares\nit against the snapshot it took beforehand and only restores it if something\nreally did replace it, does not record the directory, and says so — the receipt\nthen owns only the launcher links, and this uninstaller leaves the shared\nresources and their framework registrations alone. A snapshot that cannot be taken\nat all stops the run before `npm install -g` replaces anything.\n\nEach recorded file also carries its sha256, and the adapter directory carries the\ndigest of its stamped `manifest.json`. A path whose content no longer matches was\ntaken over by another installer (anolisa, a manual `npm install -g`) and is kept.\nBefore deleting the adapter directory the uninstaller runs each bundled\nframework's own `scripts\u002Funinstall.sh`, so an enabled framework registration is\nremoved rather than left pointing at a deleted directory. If one of them fails,\nthe uninstaller **stops short**: the adapter resources and the receipt are both\nkept and it exits non-zero, so the registration still resolves and the script the\nwarning names still exists. Fix that framework and re-run to finish.\n\nContent alone is not proof of ownership — a newer anolisa or npm install of the\nsame version leaves byte-identical binaries and manifests behind. So the receipt\nalso records this install's id, the link target each launcher resolves to, and an\nownership marker (`.tokenless-owner`) inside the adapter tree and the npm module\ndirectory. A path whose recorded identity or marker no longer matches belongs to\nthat newer install and is kept, including its framework registrations and its npm\npackage.\n\nRe-running the installer with a different method retires the previous receipt, so\nswitching npm → source does not orphan a launcher link, the npm global package\nor the adapter tree — but only once the replacement is verified. The previous\ninstall is moved aside first and put back if the new one fails, so a missing tag,\na build error or an unwritable directory leaves the working install and its\nreceipt exactly as they were. That guarantee is fail-closed: if the copy aside\ncannot be made at all — no staging directory, or a recorded file that cannot be\nread — the installer stops before writing anything instead of replacing an install\nit could not put back. An npm → npm upgrade keeps a copy of the previous\npackage payload for the same reason: the launcher links resolve into it, so a\nbroken new binary is rolled back instead of being left behind a working-looking\nlink. The new receipt is written to a temporary, moved into place and flushed\nbefore anything is retired; when it cannot be written and the previous receipt\ncannot be removed either, the run fails and restores the previous install,\nbecause a stale receipt would let a later uninstall delete the new one. Where the previous npm prefix and the install\ndirectory overlap (`--prefix ~\u002F.local` with `~\u002F.local\u002Fbin`), that package is\nretired by hand instead of through `npm uninstall`, which would otherwise take the\nfreshly installed CLI with it. A failed npm attempt is rolled back the same way,\nso the source-build fallback never inherits an unowned package, launcher link or\nadapter tree.\n\n**Direct npm installation (Method B), not through the curl script:** no receipt\nexists, so undo the three things the install did, in this order. Deregister the\nframeworks enabled in Step 3 **first**, while their resources are still on disk —\notherwise every hook entry, plugin directory and symlink keeps pointing at a\ndirectory that no longer exists:\n\n```bash\n# 1. Once per framework enabled in Step 3 (claude-code, codex, hermes, openclaw,\n#    opencode, qoder, qwencode, qwenpaw).\nbash ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\u002F\u003Cframework>\u002Fscripts\u002Funinstall.sh\n\n# 2. Remove the global package.\nnpm uninstall -g anolisa-tokenless\n\n# 3. Remove the adapter resources the package postinstall created.\nrm -rf ~\u002F.local\u002Fshare\u002Fanolisa\u002Fadapters\u002Ftokenless\n```\n\nThe uninstaller stops short rather than half-finishing, and exits non-zero when it\ndoes: a framework registration it could not remove keeps the adapter resources and\nthe receipt, and a global npm package it could not remove (no npm on PATH) keeps\nthe package, that prefix's launcher links and the receipt. Fix the cause and\nre-run — the receipt is what makes the retry possible.\n\nThis is the order the receipt-driven uninstaller uses internally, and the order\nthe Tokenless troubleshooting page prescribes for an npm installation. Step 3\nalso removes the resources a Method C npm install writes, so skip it when\nanother Tokenless installation on this machine still needs them — and skip it\nwhenever the postinstall reported that it kept a managed adapter tree, because\nthat directory was never this npm install's to delete.\n\nIf the receipt is missing (for example after a manual cleanup), the uninstaller\nexits with an error rather than guessing; remove `\u003Cinstall-dir>\u002Ftokenless` (and\n`\u003Cinstall-dir>\u002Frtk`, left by releases that shipped it separately) yourself, using\nthe directory you actually installed into.\n",{"name":5,"layer":50,"version":51,"lifecycle":31,"description":7},"application","1.0.0","main","d2c8a75e03a304c97d2b049d59f85c2ef0b08519","src\u002Fos-skills\u002Fai\u002Finstall-tokenless",195,"https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA","https:\u002F\u002Fagentic-os.sh\u002F","https:\u002F\u002Fgithub.com\u002Fagentic-os-org","2026-11-14 23:49:17",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add agentic-os-org\u002FANOLISA --skill install-tokenless",{"tool":66,"command":67},"bunx","bunx skills add agentic-os-org\u002FANOLISA --skill install-tokenless",{"tool":69,"command":70},"pnpm","pnpm dlx skills add agentic-os-org\u002FANOLISA --skill install-tokenless","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fos-skills\u002Fai\u002Finstall-tokenless\u002FSKILL.md",true,[],[75,89,111,128,146,159],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":45},"01M6K30MJVPNFF4VA778AZC512","ws-ckpt","Linux 工作区快照(ws-ckpt)。用户想保存或备份工作区当前状态(\"保存一下\"、\"留个底\"、\"先备份\"), 想撤销或恢复文件改动(\"回滚\"、\"撤销\"、\"改回去\"、\"恢复到之前\"、\"刚才那版\"), 想查看、对比或删除历史版本,或要开启\u002F关闭每回合自动快照、定时快照、快照保留策略时使用。 用户没提\"快照\"、只表达保存或恢复工作区文件的意图时同样适用;用户点名 git 操作(commit、branch、reset 到某提交)时不适用。","https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fws-ckpt\u002Fsrc\u002Fskills\u002Fws-ckpt\u002FSKILL.md",[],[82,43,83,84,85,86,87,88],"ws ckpt","commit","git","branch","reset","定时","文件",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":96,"publishedAt":45},"01M6K30G7BBZB1VCPE3NE08KZP","skillfs-mount","Help users configure, mount, and unmount a skillfs FUSE virtual filesystem on their local machine (e.g. for openclaw). Covers analyzing existing skill usage to suggest view configuration, generating skillfs-views.toml, mounting, and graceful unmount. Use this skill when the user asks to: set up skillfs, configure skill views, mount or unmount skillfs, check if skillfs is running, or get help organizing their skills directory (especially for openclaw users).","https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fskillfs\u002Fdocs\u002Fskills\u002Fskillfs-mount\u002FSKILL.md",[95],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[97,98,99,100,101,102,34,35,103,104,105,36,106,37,107,27,108,31,29,26,109,110],"skillfs mount","mount","virtual","get","local","existing skill","view","filesystem","toml","skill usage","analyzing","machine","running","directory",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":121,"publishedAt":45},"01M6K30CJW0X3V5PG4GP26TB63","test-skill","A test skill used in integration tests.","https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fskillfs\u002Fcrates\u002Fskillfs-fuse\u002Ftests\u002Ffixtures\u002Ftest-skill\u002FSKILL.md",[117,120],{"categoryNo":118,"categoryName":119,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[122,123,124,125,126,127],"test","Test Skill","true","integration tests","integration","tests",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":45},"01M6K304VCM7N6AR4PMYNDP3A7","storage-resize","Linux 磁盘扩容技能（RPM 包管理系统），实现云盘扩容后自动完成分区调整和文件系统扩容。支持系统盘\u002F数据盘在线扩容，适配 XFS\u002FEXT4\u002FBtrfs 文件系统。适用于 RPM 包管理的 Linux 系统（如 Alibaba Cloud Linux）。","https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fos-skills\u002Fsystem-admin\u002Fstorage-resize\u002FSKILL.md",[],[135,136,137,43,138,139,140,141,142,88,143,144,145],"storage resize","storage","system","cloud","operations","btrfs","ecs","aliyun","rpm","alibaba","数据",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":45},"01M6K2ZJEGANYH9TGGG25H7WVF","ktuner","内核参数自动调优。分析系统配置，输出调优建议并可一键应用，支持自动回滚。使用场景：系统性能优化、安全加固、内核参数诊断。","https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fos-skills\u002Fsystem-admin\u002Fktuner\u002FSKILL.md",[],[148,153,154,155,156,157,158],"core","run","Production","shell","安全","command",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":45},"01M6K2ZD5K40XCX8R1EA85MS7P","backup-restore","处理所有备份与恢复任务，覆盖四个层面：工作区（项目\u002F数据库\u002F代码）、用户数据（家目录\u002Fdotfiles\u002F密钥）、操作系统（全量系统\u002F磁盘镜像\u002FLVM 快照）、阿里云快照（云盘快照\u002F自动策略\u002F跨地域复制\u002F整机镜像）。适用于 RPM 包管理的 Linux 系统（如 Alibaba Cloud Linux）纯命令行环境，使用 yum 包管理器。当用户提到备份、恢复、快照、归档、回滚、克隆、迁移、容灾等任何涉及数据保存或恢复的请求时触发此技能，即使请求看起来很简单也应使用。","https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fos-skills\u002Fsystem-admin\u002Fbackup-restore\u002FSKILL.md",[],[166,167,168,138,169,170,171,143,144,172,145,173,174,43,142],"backup restore","backup","restore","beta","release","lvm","runtime","maintenance","dotfiles"]