Use the experimental Nasiko CLI lifecycle bridge for pinned installation, read-only status, and qualified uninstall with explicit consent and telemetry and secr
复制下面这句话,粘贴给 Claude Code、Codex、Cursor 等 AI 编程工具,它会读取安装说明并在你确认后完成安装。
请阅读 https://ai.atlankj.com/install/asset/gh-nasiko-control-plane-9ba8b37aed14 ,按照其中的说明把「nasiko-control-plane」安装到你(当前 AI 工具)中。执行前先告诉我将运行的命令和写入的位置,等我确认。
查看 AI 将读取的安装说明正在读取 GitHub 原文…
内容来自 GitHub 原始文件,由原作者维护。在 GitHub 查看
Use this skill when a user explicitly asks ECC to install, inspect, or remove the qualified Nasiko CLI. This skill does not operate a Nasiko control plane.
ecc nasiko status --json. Status is read-only.--yes.v0.1.0.ecc nasiko install --version v0.1.0 --dry-run --json.ecc nasiko install --version v0.1.0 --yes --json only after the
user reviews the version, registry origin, digest, and destination.ecc nasiko uninstall --version v0.1.0 --yes --json. Preview removal with
--dry-run first.https://github.com/Nasiko-Labs/nasiko, licensed
under Apache-2.0; artifact and extracted-binary SHA-256 values are pinned.The initial ECC bridge supports qualified installation, read-only status, and ownership-checked uninstall. Use the canonical Nasiko CLI directly for connection, authentication, launch, deployment, or shutdown until those verbs have their own verified ECC contracts. Do not guess CLI verbs.
Installing the CLI does not prove that a control-plane server is running, an agent is governed, routing or ACLs work, observability is complete, telemetry was enabled, or Ito compute is connected. Report each state separately.
latest.PATH entries. Use ECC's qualified location or an
explicit absolute ECC_NASIKO_CLI_EXECUTABLE for development verification.