Dfinity Official Cloud Engine Canisters

Name: Dfinity Official Cloud Engine Canisters
Author: dfinity

Chains by @dfinity v1.0.0 B PASS 0 known · 1 unknown

Rules for canister code on a cloud engine (CloudEngine subnet, e.g. OpenCloud). Engine canisters hold 0 cycles: never attach cycles you computed: drop `(with cycles = …)` clauses (failure: IC0504). Cross-subnet calls must be bounded-wait and cycle-free (`(with timeout = N)`, `Call::bounded_wait`) or rejected: 'Unbounded-wait calls and calls with cycles are not allowed to CloudEngine subnets'. HTTPS outcalls use the ordinary wrapper and are free; never via the proxy: no transform applies ('Replicas had different responses') and its budget drains into InsufficientCycles: move the outcall, don't top up. Cycle-bearing cross-subnet calls go through the engine's proxy canister: XRC, and threshold ECDSA/Schnorr and vetKD (Bitcoin, Ethereum, VetKeys); hand-encode the arguments; the ic-vetkeys and ic-cdk helpers attach cycles. Derived keys belong to the proxy. Use when writing or debugging engine canister code, signing or deriving keys, or on these errors. Do NOT use for deploying a proxy (deploy-to-cloud-engine).

Install

$ cp -r cryptoskill/skills/chains/dfinity-official-cloud-engine-canisters .claude/skills/

$ clawhub install dfinity-official-cloud-engine-canisters

Quality Score

Score: 65/100 Grade: B Risk Gate: PASS

Trust profile trust grade not computed yet

0 red flags 10 cleared 1 not measured

Capabilities below are detected automatically by an open-source scanner that reads the skill's text and scripts (see how this is computed). Not measured means the scanner couldn't make a confident call — it is NOT a green check, and you should treat it as a possible red flag until a human or a stronger scanner has measured it.

10 Cleared by scanner we scanned the skill's text & scripts and found no evidence of these

✓
Can move funds this skill can sign and send transactions on your behalf
✓
Requires private key you must hand over a private key, mnemonic, or wallet config
✓
Requires hosted operator depends on a third-party hosted service to function
✓
Uses remote install script setup pipes a remote shell script (curl | sh class)
✓
Mutable remote runtime runs remote code that can change behavior without a local diff
✓
Can install code installs software at setup time (npx, pip, brew, etc.)
✓
Can execute shell runs arbitrary shell commands on your machine
✓
Can browse the web fetches arbitrary URLs at runtime
✓
Can write files writes to your local filesystem
✓
Can spawn sub-agents delegates to other skills or sub-agents

1 Not measured yet scanner couldn't make a confident call — treat as a possible red flag

?
Auto-invocable may be invoked by the agent without your explicit prompt

Execution mode

read_only Phase 1 single-mode classification — multi-mode breakdown deferred to Phase 2.

Ingredients (services this skill talks to)

We did not find any well-known hosted services in this skill's text or scripts. This does NOT mean the skill is local-only — it might use services we don't yet recognize, or talk to them through code paths our scanner can't reach. A complete dependency list (every package, library, and binary, with integrity hashes) is on the roadmap; today we only show recognized hosts.

Audits

No one has audited this skill yet. That is different from “audited and clean” — it just means no professional reviewer (a security firm, the CryptoSkill team, or a verified independent researcher) has signed off on it. There are no audit reports to read. How reviewer levels work →

SKILL.md → SOURCE.md → TRUST.auto.yaml → Browse directory →

Auto-generated by cryptoskill/extract-capabilities/0.3.1 · hosted-service list version 2026-09-06 · how this is computed

Source

View on GitHub →