SkillsAdd

affaan-m/ecc

nasiko-control-plane

Use the experimental Nasiko CLI lifecycle bridge for pinned installation, read-only status, and qualified uninstall with explicit consent and telemetry and secrets boundaries.

Trending #2846 First seen Aug 16, 2026

Installation

$ npx skills add affaan-m/ecc --skill nasiko-control-plane
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

recovery-controller-setup Similar name
aws/agent-toolkit-for-aws

Configures AWS Application Recovery Controller (ARC) for operational resilience: routing contro…

2.3K installs
controlling-costs Similar name
axiomhq/skills

Analyzes Axiom query patterns to find unused data, then builds dashboards and monitors for cost…

1.7K installs
planetscale-traffic-control-recommendations Similar name
planetscale/skills

Build a safe recommendation plan for PlanetScale Postgres Database Traffic Control budgets and …

12 installs
controlnet-pose Similar name
prime-skills/runcomfy-agent-skills

Pose-conditioned generation on RunComfy via the `runcomfy` CLI. Routes across Kling 2-6 Motion …

354.3K installs
desktop control Similar name
patrickporto/desktop-agent

Control mouse, keyboard, and screen for desktop automation tasks

4K installs
bencium-controlled-ux-designer Similar name
bencium/bencium-marketplace

Expert UI/UX design guidance for unique, accessible interfaces. Use for visual decisions, color…

3.9K installs

Also in this package

Other skills from affaan-m/ecc · top by installs.

npx skills add affaan-m/ecc
security-review 16K golang-patterns 13.7K backend-patterns 13.1K frontend-patterns 13K coding-standards 12.9K golang-testing 12K docker-patterns 11.3K springboot-patterns 11.2K python-patterns 11.1K frontend-slides 11.1K

Browse all from affaan-m/ecc

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 254.3K
License LICENSE
Default branch main
Open issues 54
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,470 B
  • docs SUMMARY.md 2,423 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 856 installs

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 --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 ECCNASIKOCLI_EXECUTABLE for development verification.

  • Do not treat a partial or ambiguous installation as success.