Can it install the latest version of the Nasiko CLI?

No. It installs one pinned qualified version and forbids fallback to latest or bootstrap scripts.

Does it install anything without asking?

No. Install is consent-gated and shows a dry-run preview first.

How does it handle secrets and telemetry?

Telemetry is opt-in, and secrets are kept out of logs and arguments.

Can it remove a Nasiko CLI it did not install?

No. Uninstall is ownership-checked, so it only removes what it owns.

What does a status check change?

Nothing. Status checks are read-only.

Nasiko CLI Lifecycle Bridge

SkillDev tools

The nasiko-control-plane skill lets an AI agent manage the Nasiko CLI lifecycle through ECC. It performs read-only status checks, installs one pinned qualified version after consent and a dry-run preview, and removes the CLI only when ownership checks pass. It validates platform, digests, and destinations, and keeps telemetry opt-in with secrets out of logs and arguments.

Use Nasiko CLI Lifecycle Bridge in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add Nasiko CLI Lifecycle Bridge and connect your AI. About a minute.

Claude ChatGPT Ahel Desktop

Also: Claude Code · Cursor · Codex

Then ask your AI: use the Nasiko CLI Lifecycle Bridge skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.

No other account needed.

Have an AI agent that can load skills and reach the Nasiko CLI environment.

Nasiko CLI Lifecycle BridgeStart free

What your AI can do with it

Check the current Nasiko CLI status without making changes
Preview an install with a dry run before anything is applied
Install the pinned qualified Nasiko CLI version after consent
Uninstall the Nasiko CLI only when ownership checks pass
Validate platform, digests, and destinations during lifecycle actions
Keep telemetry opt-in and secrets out of logs and arguments

Getting started

Have an AI agent that can load skills and reach the Nasiko CLI environment.
Add the nasiko-control-plane skill to that agent.
Ask the agent to run a read-only status check of the Nasiko CLI.
Request an install and review the dry-run preview before giving consent.
Confirm consent so the pinned qualified version is installed.

What this skill tells your AI

The instructions your AI receives, as published by affaan-m/ecc in skills/nasiko-control-plane/SKILL.md and read by ahel’s review.

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.

Signals

GitHub stars: 270k
Forks: 40k
Last commit: Sep 2026

Questions

Can it install the latest version of the Nasiko CLI?: No. It installs one pinned qualified version and forbids fallback to latest or bootstrap scripts.
Does it install anything without asking?: No. Install is consent-gated and shows a dry-run preview first.
How does it handle secrets and telemetry?: Telemetry is opt-in, and secrets are kept out of logs and arguments.
Can it remove a Nasiko CLI it did not install?: No. Uninstall is ownership-checked, so it only removes what it owns.
What does a status check change?: Nothing. Status checks are read-only.

Advanced

Item type: skill
Key: nasiko-control-plane
Source: github.com/affaan-m/ecc

github.com/affaan-m/ecc

More in Dev tools

teach
Skill · mattpocock
More in Dev tools implement
Skill · mattpocock
More in Dev tools ponytail
Skill · dietrichgebert
More in Dev tools caveman
Skill · juliusbrussee
More in Dev tools shadcn
Skill · shadcn
More in Dev tools council
Skill · affaan-m
More in Dev tools