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 theuser 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, licensedunder Apache-2.0; artifact and extracted-binary SHA-256 values are pinned.
bootstrap script.
install metadata, or ECC state.
separately disclosed. Installation is not telemetry consent.
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.
destination fails validation, stop without executing the artifact.
latest.PATH entries. Use ECC's qualified location or anexplicit absolute ECC_NASIKO_CLI_EXECUTABLE for development verification.