Chainstream Defi
v1.1.4[FINANCIAL EXECUTION] Execute irreversible on-chain DeFi operations via CLI and MCP tools. Use when user wants to swap tokens, create tokens on launchpad, si...
⭐ 0· 230·1 current·1 all-time
byChainStream@harry5556
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (financial execution / swaps / launchpads / sign & broadcast) align with the content of SKILL.md and the reference docs. All endpoints, CLI commands, MCP URL, and SDK guidance are consistent with a DeFi execution tool. No unrelated credentials or unrelated binaries are requested.
Instruction Scope
Instructions stay within DeFi execution scope (route → confirm → sign → broadcast) and include mandatory safety steps (explicit user confirmation, price/slippage thresholds). They reference local config (~/.config/chainstream/config.json) and wallet operations (signin, wallet import, raw key import). The skill repeatedly instructs use of `npx @chainstream-io/cli` to run commands; that implies downloading and executing remote npm code at runtime (see install_mechanism note). The instructions also allow importing raw private keys via the CLI — legitimate for the purpose but high-sensitivity and risky if done in a shared/hosted agent or chat.
Install Mechanism
There is no explicit install spec in the package (instruction-only), which is lower risk for disk writes. However, the runtime commands rely on `npx @chainstream-io/cli` and `tempo request` which implicitly fetch and execute remote packages/tools (npm, tempo). That means running the skill will cause remote code to be downloaded and executed (implicit install/execution). This is coherent for a CLI-based DeFi tool but worth noting as an execution-time risk.
Credentials
The skill declares no required env vars, which matches the CLI/SDK/MCP design where auth is handled via wallet login or interactive purchase. It does, however, rely on wallets, API keys, and local config files (~/.config/chainstream/...). The capability to import raw private keys and the CLI's automatic storage of API keys/config is proportional to a DeFi execution skill but is highly sensitive — exposing private keys or using CLI login in an untrusted environment is dangerous. Also: SKILL.md lists no required binaries but presumes availability of Node/npm (npx) and tooling like curl/tempo, which is an operational mismatch to be aware of.
Persistence & Privilege
The skill is not marked always:true and is user-invocable. Autonomous invocation is enabled (default) — the skill repeatedly insists that the agent must NOT auto-execute destructive operations and require explicit confirmation. That policy is coherent, but because the skill can sign and broadcast real transactions, you should ensure the agent enforces those confirmation rules. The CLI also persists keys and API keys in ~/.config, which is expected behavior for a wallet CLI but gives the tool persistent credentials on the host.
Assessment
This skill is internally coherent for executing real on-chain DeFi operations, but it carries high operational risk because transactions are irreversible and the runtime runs remote code. Before installing/using it: 1) Do not paste or type private keys into a shared chat — importing raw keys into the CLI will expose them on the host. Prefer using your own wallet via the SDK or an isolated machine. 2) Understand that `npx @chainstream-io/cli` will fetch and run code from npm each time; review the CLI source (GitHub/package) before running. 3) Expect the CLI to persist keys and apiKey in ~/.config/chainstream — ensure that path is secure. 4) Insist on explicit human confirmation for every destructive step (the skill requires this; make sure your agent enforces it). 5) If you run this inside an automated agent, restrict autonomous invocation or add policy checks so the agent cannot broadcast transactions without an out-of-band human approval. If you want lower risk, use read-only data skills (chainstream-data / chainstream-graphql) or integrate via SDK with a wallet you control.Like a lobster shell, security has layers — review code before you run it.
bridgevk975yft82a8j4ccsk0r00gpn4x83bt02cryptovk975yft82a8j4ccsk0r00gpn4x83bt02defivk975yft82a8j4ccsk0r00gpn4x83bt02ethereumvk975yft82a8j4ccsk0r00gpn4x83bt02latestvk971m9azs75ztf7y1a3p8dx9fd840c9ysolanavk975yft82a8j4ccsk0r00gpn4x83bt02swapvk975yft82a8j4ccsk0r00gpn4x83bt02tradingvk975yft82a8j4ccsk0r00gpn4x83bt02x402vk975yft82a8j4ccsk0r00gpn4x83bt02
License
MIT-0
Free to use, modify, and redistribute. No attribution required.