← Search

Nasiko CLI Lifecycle Bridge
Claude Code 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 4eb71d9
Install test only, on the date shown. This does not guarantee the code is safe.
🔎 Install prompt analysis · 2026-10-13 : installs packages
⚙ Needs: Node.js and npm.

Nasiko CLI Lifecycle Bridge

Manage the experimental Nasiko CLI lifecycle: read-only status, consent-gated install of the pinned version, and ownership-checked uninstall.

At a glance
What
Manage the experimental Nasiko CLI lifecycle: read-only status, consent-gated install of the pinned version, and ownership-checked uninstall.
Cost
Free
Needs
Node.js and npm. The skill drives the `ecc` command-line tool, and that tool is not a separate product: it ships with ECC itself, as the npm package `ecc-universal` (the `ecc` command, version 2.2.3). If `ecc` is not on my machine yet, that package is where it comes from: `npm install -g ecc-universal`. No Nasiko account and no API key are needed to install this skill.
Level
Intermediate — Node.js and npm.
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

Nasiko CLI Lifecycle Bridge is a free Muse skill and lifecycle bridge for the experimental Nasiko CLI, operated through ECC. Status checks are read-only. Installation always requires explicit user consent and installs only the ECC-qualified pinned version, currently v0.1.0, with a dry-run preview first.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: Node.js and npm. The skill drives the `ecc` command-line tool, and that tool is not a separate product: it ships with ECC itself, as the npm package `ecc-universal` (the `ecc` command, version 2.2.3). If `ecc` is not on my machine yet, that package is where it comes from: `npm install -g ecc-universal`. No Nasiko account and no API key are needed to install this skill. Install "Nasiko CLI Lifecycle Bridge" for me. It manages the experimental Nasiko CLI lifecycle through ECC: read-only status checks, a consent-gated install of the pinned qualified Nasiko version (v0.1.0), and an ownership-checked uninstall, under explicit telemetry and secrets boundaries. Repository: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/nasiko-control-plane/SKILL.md Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch both files of the skill from the repository into a temporary folder and look inside: SKILL.md, and agents/openai.yaml in the agents/ subfolder of the same skill folder. 2. Integrity check: Skill Harbor reviewed this listing on 2026-10-10 and recorded the fingerprints below. I want you to compute the SHA-256 of each downloaded file and compare: - SKILL.md: SHA-256 086650c5a5d797530086a1f7a5f6d853034a30c75c53e2e4aa80e8df7192b52b - agents/openai.yaml: SHA-256 765d863356ba7de108816a62247a3748c6878fee0ff018e8ab1ea07c6fa92b27 If a fingerprint does not match, I want you to stop before installing and tell me the files changed since Skill Harbor's review, so the new version is unverified. Show me your safety findings and give me three choices: (a) wait for Skill Harbor to re-review the listing (recommended), (b) analyze the new files in detail first and then decide, (c) install anyway knowing the risk. Then wait for my answer before doing anything else. 3. Safety check: I want to see your findings explicitly, in short separate items: - every network address the code contacts (expected: none during this installation; the two files are a Markdown guidance file and a small YAML file. When the skill is used later, it points at the qualified Nasiko source, github.com/Nasiko-Labs/nasiko) - every shell command it runs (expected: none during installation; when used, the skill runs read-only `ecc nasiko status` checks first, and any install it performs is consent-gated, pinned to v0.1.0, and previewed with a dry run) - every place credentials, API keys or personal data are read, stored or sent (expected: none; the skill text itself states that secrets never go into command arguments, logs, or output) - any obfuscated or encoded code (expected: none — plain Markdown and YAML text) If anything looks suspicious, stop and explain it to me before continuing. 4. Confirmation: before installing, give me a short summary of what the skill does plus your safety findings, and wait for my explicit "yes, install". 5. Install it as a skill: copy SKILL.md and agents/openai.yaml (keeping the agents/ subfolder) into the agent's skills directory, in a folder named "nasiko-control-plane". 6. Verify with no network calls: frontmatter valid, both files in place. 7. Report what was installed, where, and what I still need to do myself (for example: if the `ecc` command is missing on my machine, install it from its npm package, `npm install -g ecc-universal`; the first check the skill runs afterwards is the read-only `ecc nasiko status --json`. Installing the Nasiko CLI itself is a separate, consent-gated step for later, not part of this installation). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
  • It can download and install software packages.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 4eb71d9 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Install prompt analysis · 2026-10-13 : installs packages
What the scan found — excerpts from the install prompt
  • installs packages — Prerequisites: Node.js and npm. The skill drives the `ecc` command-line tool, and that tool is not a separate · Prérequis : Node.js et npm. Le skill pilote l'outil en ligne de commande `ecc`, et cet outil n'est pas un prod · 7. Rapporte ce qui a été installé, où, et ce qu'il me reste à faire moi-même (par exemple : si la commande `ec
🔎 Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
4eb71d9 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : installs packages

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.