nasiko-control-plane

该 Skill 借助 ECC 命令管理 Nasiko CLI 生命周期：先做只读状态检查；安装仅限经用户明示同意的固定版本 v0.1.0，并先以 dry-run 预览版本、来源、摘要与目标路径；卸载仅在所有权校验通过时执行。强调不执行未通过校验的产物、不回退 latest、不将密钥写入命令行或日志，遥测与数据共享需另行同意。

affaan-m

热度 34.66

最近更新 2026-10-18 16:19:25

分类：自动化依赖：代码执行 / 第三方 API应用场景：工作流 / 自动化脚本

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add affaan-m/ecc/nasiko-control-plane

Metadata

name: nasiko-control-plane
description: Manage the experimental Nasiko CLI lifecycle through ECC — read-only status checks, consent-gated install of the pinned qualified version with dry-run preview, and ownership-checked uninstall, under explicit telemetry and secrets boundaries. Use when the user asks to install, inspect, or remove the Nasiko CLI or check whether it is present.

Nasiko CLI Lifecycle Bridge

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.

Safety contract

Begin with ecc nasiko status --json. Status is read-only.
Installation always requires explicit user consent and --yes.
Install only an ECC-qualified pinned version, currently v0.1.0.
Preview first with ecc nasiko install --version v0.1.0 --dry-run --json.
Install with ecc nasiko install --version v0.1.0 --yes --json only after the user reviews the version, registry origin, digest, and destination.
Remove only a still-qualified ECC-managed binary with ecc nasiko uninstall --version v0.1.0 --yes --json. Preview removal with --dry-run first.
The qualified source is https://github.com/Nasiko-Labs/nasiko, licensed under Apache-2.0; artifact and extracted-binary SHA-256 values are pinned.
Never replace the qualified command with a downloaded shell or PowerShell bootstrap script.
Never put secrets or credentials in command arguments, logs, skill output, install metadata, or ECC state.
Nasiko telemetry and any sharing with Nasiko or Ito must be opt-in and separately disclosed. Installation is not telemetry consent.

Lifecycle boundary

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.

Failure behavior

If the platform, architecture, version, manifest, digest, archive, binary, or destination fails validation, stop without executing the artifact.
Do not fall back to latest.
Do not search arbitrary PATH entries. Use ECC's qualified location or an explicit absolute ECC_NASIKO_CLI_EXECUTABLE for development verification.
Do not treat a partial or ambiguous installation as success.