Near Cli Tools

What This Skill Does

The Near Cli Tools skill, authored by cuongdcdev, provides an essential interface for OpenClaw agents to manage and interact with the NEAR Protocol command-line tools. This skill automates the detection, installation, and execution of near-cli-rs, enabling agents to perform complex blockchain operations, deploy smart contracts, and manage accounts directly from the terminal. It is designed to bridge the gap between human intent and the underlying Rust-based NEAR CLI, ensuring that agents can reliably execute commands across various operating systems including Linux, macOS, and Windows.

Installation

Installation is streamlined for multiple environments. For Unix-based systems, you can use the official shell script: curl --proto '=https' --tlsv1.2 -LsSf https://github.com/near/near-cli-rs/releases/latest/download/near-cli-rs-installer.sh | sh. For developers, the skill supports npm installations (npm install -g near-cli-rs) or cargo builds for Rust-centric environments. After installation, ensure the binary is within your system PATH, or use whereis near to locate it for direct execution.

Use Cases

This skill is ideal for:

• Developers needing to automate smart contract compilation and deployment cycles.
• Users performing on-chain transactions, such as transferring tokens or managing staking pools.
• Agents maintaining account security, key management, and configuration synchronization across multiple NEAR networks (Mainnet, Testnet, or Devnet).
• Debugging and verifying node connection status during protocol interaction.

Example Prompts

1. "OpenClaw, please install the NEAR CLI on this machine and verify the current version installed."
2. "I need to deploy my smart contract to the NEAR Testnet. Can you use the near CLI to handle the deployment process?"
3. "Find the absolute path for my near binary and check the status of my current account balance on Mainnet."

Tips & Limitations

Crucially, agents must always resolve the absolute path of the near binary before invocation to prevent path resolution errors. If you are on a restricted environment, ensure the shell configuration (~/.bashrc or ~/.zshrc) is correctly updated after adding the binary location to your PATH. Always verify the installation with near --version post-setup to confirm the environment is correctly primed for blockchain interaction.