affaan-m/ecc

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.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/affaan-m/ecc --skill nasiko-control-plane

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

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

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

Tâches connexes

du même dépôt

Autres Skills

Tous les Skills
affaan-m
Communauté

rust-testing

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology. Use when writing Rust tests — unit, integration, async, property-based, or coverage.

Installations / 24h
489
GitHub Stars
308,2 k
Mis à jour
20 nov.
affaan-m
Communauté

search-first

Research-before-coding workflow: search npm/PyPI, MCP servers, skills, and GitHub for existing tools before writing custom code, then adopt, extend, or build. Launches the researcher agent for non-trivial needs. Use when starting a feature, adding a dependency or integration, or about to write a utility that may already exist.

Installations / 1h
5
GitHub Stars
308,2 k
Mis à jour
20 nov.
affaan-m
Communauté

browser-qa

Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP / DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.

Installations / 1h
2
GitHub Stars
307,9 k
Mis à jour
20 nov.
affaan-m
Communauté

docker-patterns

Docker and Docker Compose patterns for local development, hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration. Use when creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions, or planning accurate native macOS and Windows validation.

Installations / 1h
2
GitHub Stars
307,9 k
Mis à jour
20 nov.