Skills · SkillTesting & SecurityReviewed

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.

View on GitHub

Kind: Skill
Works with: Claude Code, Codex
Source: affaan-m/ECC @ d3b8a3e90890
Path: skills/nasiko-control-plane/SKILL.md
License: MIT
Jobs: Guardrails

InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.

# 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.
…