Check whether Nasiko CLI is installed, preview installation of a fixed, verified version, and remove an ECC-managed installation. The workflow uses ECC commands, requires consent for installation, and checks ownership before removal.
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.
Review the instructions the agent will receive before you install.
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.
ecc nasiko status --json. Status is read-only.--yes.v0.1.0.ecc nasiko install --version v0.1.0 --dry-run --json.ecc nasiko install --version v0.1.0 --yes --json only after the
user reviews the version, registry origin, digest, and destination.ecc nasiko uninstall --version v0.1.0 --yes --json. Preview removal with
--dry-run first.https://github.com/Nasiko-Labs/nasiko, licensed
under Apache-2.0; artifact and extracted-binary SHA-256 values are pinned.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.
latest.PATH entries. Use ECC's qualified location or an
explicit absolute ECC_NASIKO_CLI_EXECUTABLE for development verification.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Design and audit interfaces for Web, iOS, and Android using WCAG 2.2 accessibility guidance. Check screen-reader labels, keyboard navigation, contrast, and control sizes to identify barriers and guide implementation for people using assistive technology.
Investigate unreliable AI agents across 12 layers, including instructions, memory, tool execution, and display. Use code and logs to trace failures, rank findings by severity, and produce an ordered repair plan that prioritizes code changes.
Compare coding agents on tasks from your own codebase. Define success checks, run agents in separate Git working directories, and report pass rates, available API costs, completion time, and consistency across repeated trials.
Design and refine an AI agent’s available actions, tool inputs, and result formats. Define recovery steps for errors, manage the information kept in context, and evaluate changes through completion rates, retries, and cost per successful task.
Diagnose failed AI agent runs by capturing errors, checking likely causes, and choosing small, reversible recovery actions. The workflow produces a structured report of the failure, recovery steps, and evidence, helping explain repeated retries or stalled progress.
Diagnose AI agent runs that fail repeatedly, loop through tools, or lose track of the task. Capture errors and environment details, test a focused recovery action, and produce a report explaining the evidence and outcome.