Nasiko Control Plane

Use this skill when a user explicitly asks to install, inspect, or operate the Nasiko control plane with ECC.

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.

Files2

2 files · 1.3 KB

Select a file to preview

Overall Score

88/100

Grade

A

Excellent

Safety

88

Quality

90

Clarity

87

Completeness

85

Summary

This skill enables safe installation, inspection, and lifecycle management of the Nasiko agent control plane through ECC (a secure execution environment). It enforces explicit user consent, pins artifact versions with SHA-256 validation, and establishes clear boundaries around secrets, telemetry, and CLI functionality. The skill is read-first and requires multi-step verification before any destructive operations.

Detected Capabilities

shell executionartifact download and verificationbinary installation to ECC-managed pathstatus queries via ECC CLIenvironment variable usage for executable path

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

install nasiko control planenasiko status checknasiko cli setupverify nasiko installationnasiko uninstall safely

Risk Signals

WARNING

Download and execute artifact from external source

Safety contract: install steps

INFO

Environment variable expansion (ECC_NASIKO_CLI_EXECUTABLE)

Failure behavior section

INFO

External dependency on GitHub artifact source (github.com/Nasiko-Labs/nasiko)

Safety contract: qualified source

Referenced Domains

External domains referenced in skill content, detected by static analysis.

github.com

Use Cases

Install Nasiko control plane CLI with verified artifacts
Check Nasiko control plane installation status
Uninstall Nasiko control plane safely with user confirmation
Verify artifact integrity via SHA-256 pinned digests
Prevent accidental telemetry or credentials leakage during installation

Quality Notes

Excellent safety contract with explicit consent gates and multi-step verification (dry-run before install)
Clear scope boundaries: installation only, defers connection/auth/deployment to Nasiko CLI itself
Well-documented anti-patterns (no shell bootstrap scripts, no secrets in arguments)
Comprehensive failure modes with validation checkpoints (platform, arch, version, digest, archive, binary, destination)
Explicit telemetry consent separation—installation is not consent
Strong artifact pinning with SHA-256 and version lock (v0.1.0)
Prevents fallback to latest and arbitrary PATH searches—uses qualified ECC location only
Supporting YAML file provides clear user-facing interface and default prompt
Distinction between CLI installation and control-plane runtime state is well explained

Model: claude-haiku-4-5-20251001Analyzed: Aug 16, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

nasiko-control-plane