chore: don't use the dfinity tap to install icp-cli

skills/asset-canister/SKILL.md

@@ -16,7 +16,7 @@ The asset canister hosts static files (HTML, CSS, JS, images) directly on the In
 
 ## Prerequisites
 
-- icp-cli >= 0.1.0 (`brew install dfinity/tap/icp-cli`)
+- icp-cli >= 0.1.0 (`brew install icp-cli`)
 - Node.js >= 18 (for building frontend assets)
 - `@icp-sdk/canisters` npm package (for programmatic uploads)
 

skills/certified-variables/SKILL.md

@@ -16,7 +16,7 @@ Query responses on the Internet Computer come from a single replica and are NOT
 
 ## Prerequisites
 
-- `icp-cli` >= 0.1.0 (install: `brew install dfinity/tap/icp-cli`)
+- `icp-cli` >= 0.1.0 (install: `brew install icp-cli`)
 - Rust: `ic-certified-map` crate (for Merkle tree), `ic-cdk` (for `certified_data_set` / `data_certificate`)
 - Motoko: `CertifiedData` module (included in mo:core/mo:base), `ic-certification` package (`mops add ic-certification`) for Merkle tree with witness support
 - Frontend: `@icp-sdk/core` (agent, principal), `@dfinity/certificate-verification`

skills/ckbtc/SKILL.md

@@ -16,7 +16,7 @@ ckBTC is a 1:1 BTC-backed token native to the Internet Computer. No bridges, no
 
 ## Prerequisites
 
-- `icp-cli` >= 0.1.0 (install: `brew install dfinity/tap/icp-cli`)
+- `icp-cli` >= 0.1.0 (install: `brew install icp-cli`)
 - For Motoko: `mops` package manager, `core = "2.0.0"` in mops.toml
 - For Rust: `ic-cdk`, `icrc-ledger-types`, `candid`, `serde`
 - A funded ICP identity (for mainnet deployment cycles)

skills/evm-rpc/SKILL.md

@@ -16,7 +16,7 @@ The EVM RPC canister is an IC system canister that proxies JSON-RPC calls to Eth
 
 ## Prerequisites
 
-- `icp-cli` >= 0.1.0 (`brew install dfinity/tap/icp-cli`)
+- `icp-cli` >= 0.1.0 (`brew install icp-cli`)
 - For Motoko: `mops` package manager, `core = "2.0.0"` in mops.toml
 - For Rust: `ic-cdk`, `candid`, `serde`
 - Cycles in your canister (each RPC call costs cycles)

skills/https-outcalls/SKILL.md

@@ -16,7 +16,7 @@ HTTPS outcalls allow canisters to make HTTP requests to external web services di
 
 ## Prerequisites
 
-- icp-cli >= 0.1.0 (`brew install dfinity/tap/icp-cli`)
+- icp-cli >= 0.1.0 (`brew install icp-cli`)
 - For Motoko: `moc >= 0.14.10` (included with icp-cli), `mo:core` 2.0 and `ic >= 2.1.0` in mops.toml
 - For Rust: `ic-cdk >= 0.19`, `serde_json` for JSON parsing
 

skills/icrc-ledger/SKILL.md

@@ -14,7 +14,7 @@ metadata:
 ICRC-1 is the fungible token standard on Internet Computer, defining transfer, balance, and metadata interfaces. ICRC-2 extends it with approve/transferFrom (allowance) mechanics, enabling third-party spending like ERC-20 on Ethereum.
 
 ## Prerequisites
-- icp-cli >= 0.1.0 (install: `brew install dfinity/tap/icp-cli`)
+- icp-cli >= 0.1.0 (install: `brew install icp-cli`)
 - For Motoko: mops with `core = "2.0.0"` in mops.toml
 - For Rust: `ic-cdk = "0.19"`, `candid = "0.10"`, `icrc-ledger-types = "0.1"` in Cargo.toml
 

skills/multi-canister/SKILL.md

@@ -16,7 +16,7 @@ Splitting an IC application across multiple canisters for scaling, separation of
 
 ## Prerequisites
 
-- `icp-cli` >= 0.1.0 (`brew install dfinity/tap/icp-cli`)
+- `icp-cli` >= 0.1.0 (`brew install icp-cli`)
 - For Motoko: `mops` package manager, `core = "2.0.0"` in mops.toml
 - For Rust: `ic-cdk >= 0.19`, `candid`, `serde`, `ic-stable-structures`
 - Understanding of `async`/`await` and error handling

skills/sns-launch/SKILL.md

@@ -16,7 +16,7 @@ Service Nervous System (SNS) is the DAO framework for decentralizing individual
 
 ## Prerequisites
 
-- `icp-cli` >= 0.1.0 (`brew install dfinity/tap/icp-cli`)
+- `icp-cli` >= 0.1.0 (`brew install icp-cli`)
 - `dfx` with the sns extension (`dfx extension install sns`) for prepare-canisters, validate, and propose
 - An NNS neuron with sufficient stake to submit proposals (mainnet)
 - Dapp canisters already deployed and working on mainnet

skills/stable-memory/SKILL.md

@@ -14,7 +14,7 @@ metadata:
 Stable memory is persistent storage on Internet Computer that survives canister upgrades. Heap memory (regular variables) is wiped on every upgrade. Any data you care about MUST be in stable memory, or it will be lost the next time the canister is deployed.
 
 ## Prerequisites
-- icp-cli >= 0.1.0 (`brew install dfinity/tap/icp-cli`)
+- icp-cli >= 0.1.0 (`brew install icp-cli`)
 - For Motoko: mops with `core = "2.0.0"` in mops.toml
 - For Rust: `ic-stable-structures = "0.7"` in Cargo.toml
 

skills/vetkd/SKILL.md

@@ -20,7 +20,7 @@ vetKeys (verifiably encrypted threshold keys) bring on-chain privacy to the IC v
 
 ## Prerequisites
 
-- `icp-cli` >= 0.1.0 (`brew install dfinity/tap/icp-cli`)
+- `icp-cli` >= 0.1.0 (`brew install icp-cli`)
 - Rust: `ic-vetkeys = "0.6"` ([crates.io](https://crates.io/crates/ic-vetkeys))
 - Motoko: Use the raw management canister approach shown below
 - Frontend: `@dfinity/vetkeys` v0.4.0 (`npm install @dfinity/vetkeys`)

skills/wallet/SKILL.md

@@ -16,7 +16,7 @@ Cycles are the computation fuel for canisters on Internet Computer. Every canist
 **Note:** icp-cli uses the **cycles ledger** (`um5iw-rqaaa-aaaaq-qaaba-cai`) by default. The cycles ledger is a single canister that tracks cycle balances for all principals, similar to a token ledger. Commands like `icp cycles balance`, `icp cycles mint`, and `icp canister top-up` go through the cycles ledger. There is no legacy wallet concept in icp-cli. The programmatic patterns below (accepting cycles, creating canisters via management canister) remain the same regardless of which funding mechanism is used.
 
 ## Prerequisites
-- icp-cli >= 0.1.0 (install: `brew install dfinity/tap/icp-cli`)
+- icp-cli >= 0.1.0 (install: `brew install icp-cli`)
 - An identity with ICP balance for converting to cycles (mainnet)
 - For local development: cycles are unlimited by default