← Back to Skills Marketplace
mzfshark

WEB3 Integration

by Mauricio Z. · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
79
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install axodus-web3-integration
Description
Integrate apps with blockchain providers, wallets, and contract calls safely.
README (SKILL.md)

SKILL: web3-integration

Purpose

Integrate a frontend/backend with blockchain interaction (wallet connect, provider configuration, contract calls) using safe, testable patterns.

When to Use

  • A dApp needs to read/write contract state.
  • A backend service must index or react to on-chain events.
  • Wallet connection UX and chain gating is required.

Inputs

  • stack (required, enum: ethers|viem|web3js): preferred client library.
  • chain (required, string): chain name + chainId.
  • rpc (optional, string): RPC URL reference (env/config), not hardcoded.
  • contract_address (required, string).
  • abi_source (required, string): ABI path/artifact reference.
  • wallet_flow (optional, enum: injected|walletconnect|server_signer).

Steps

  1. Validate chain/contract coordinates (chainId, address format, ABI match).
  2. Set provider/signer flow:
    • frontend: user wallet signer
    • backend: server signer only when explicitly required and keys are secured externally
  3. Implement contract client wrapper:
    • typed interfaces when possible
    • explicit timeouts/retries for RPC
  4. Add chain gating:
    • refuse wrong chain
    • prompt network switch (frontend)
  5. Add logging/audit hooks for write operations.
  6. Add tests:
    • unit tests for wrapper
    • local chain simulation when available

Validation

  • No secrets stored in repo (keys only via secrets manager/env).
  • Wrong-chain behavior is safe (no accidental writes).
  • Errors are handled deterministically (retry policy is explicit).

Output

  • Wrapper module path(s)
  • Environment variable contract (what must be configured)
  • Validation commands (tests/build)

Safety Rules

  • Never request or paste private keys into chat/output.
  • Never default to mainnet.
  • Avoid “auto-sign” server flows unless explicitly required and approved.

Example

Input:

  • stack: viem
  • chain: base:8453
  • contract_address: 0x...
  • abi_source: artifacts/MyContract.json

Output:

  • src/web3/client.ts with chainId checks and a typed contract instance.
Usage Guidance
This skill appears coherent and low-risk, but before installing or using it: (1) Verify the provenance/author if you require vendor trust (SKILL.md says 'RedHat Dev' but registry owner differs). (2) Never paste private keys into chat—follow the skill's rule to use a secrets manager or environment variables. (3) When implementing, point RPC URLs to trusted providers and limit any server-side signing flows; require explicit approval and secure key storage if server signing is used. (4) Review any generated code (wrappers, logging) and run the suggested tests locally (including a local chain simulation) before deploying to production.
Capability Analysis
Type: OpenClaw Skill Name: axodus-web3-integration Version: 1.0.0 The skill bundle provides standard, security-conscious instructions for integrating Web3 libraries (ethers, viem, web3js) into applications. It includes explicit safety rules in SKILL.md and web3-integration.md that forbid requesting private keys, discourage defaulting to mainnet, and mandate chain-gating to prevent accidental transactions on the wrong network.
Capability Tags
cryptorequires-walletrequires-sensitive-credentials
Capability Assessment
Purpose & Capability
The name/description match the instructions: steps focus on provider/signer selection, chain validation, wrapper modules, logging/audit, and tests. Nothing in the skill requires unrelated binaries, cloud credentials, or system access. (Minor metadata mismatch: SKILL.md claims 'RedHat Dev' while registry owner ID differs; this is a provenance note but does not affect capability alignment.)
Instruction Scope
SKILL.md instructions stay within web3 integration scope: they validate chain/address/ABI, recommend environment-based RPC configuration, prevent storing secrets in repo, and explicitly forbid requesting/pasting private keys into chat or defaulting to mainnet.
Install Mechanism
This is an instruction-only skill with no install spec and no code files to execute; therefore there is no installation risk from downloads or package installs.
Credentials
The skill requests no environment variables or credentials in metadata (which is appropriate), and the instructions correctly advise using env/secrets managers for RPC URLs and keys. Users should ensure secrets are provided via secure secret management rather than chat or code. The lack of declared required env vars is reasonable but means safe secret handling depends on the implementer.
Persistence & Privilege
always:false and default model invocation are set (normal). The skill does not request permanent presence or system-wide configuration changes.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install axodus-web3-integration
  3. After installation, invoke the skill by name or use /axodus-web3-integration
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of web3-integration skill: - Enables frontend and backend integration with blockchain providers, wallets, and smart contract calls. - Supports major client libraries (`ethers`, `viem`, `web3js`) and common wallet flows. - Enforces safe patterns: chain validation, proper signer setup, explicit timeouts/retries, and robust error handling. - Outputs wrapper module paths, required environment variables, and validation/test commands. - Includes detailed safety rules to prevent key exposure and accidental mainnet transactions.
Metadata
Slug axodus-web3-integration
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is WEB3 Integration?

Integrate apps with blockchain providers, wallets, and contract calls safely. It is an AI Agent Skill for Claude Code / OpenClaw, with 79 downloads so far.

How do I install WEB3 Integration?

Run "/install axodus-web3-integration" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is WEB3 Integration free?

Yes, WEB3 Integration is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does WEB3 Integration support?

WEB3 Integration is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created WEB3 Integration?

It is built and maintained by Mauricio Z. (@mzfshark); the current version is v1.0.0.

💬 Comments