nasiko-control-plane
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.
- License 许可
- MIT
- 最近更新
- 2026-11-09
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- 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.
02 资源文件 1
- 参考文档agents/openai.yaml277 B
03 SKILL.md 正文
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 --jsononly 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-runfirst. - 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
PATHentries. Use ECC's qualified location or an explicit absoluteECC_NASIKO_CLI_EXECUTABLEfor development verification. - Do not treat a partial or ambiguous installation as success.
04 同仓库更多 Skills
dei-assessment
Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.
dei-action-plan
Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.
culture-fit-assessment
Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.
cowork-to-code-bridge
Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.
counter-offer-response
Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.
continuous-feedback-system
Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.