solidity-lsp

What This Skill Does

The solidity-lsp skill serves as a robust development environment for Ethereum-compatible smart contracts within the OpenClaw ecosystem. By integrating industry-standard tools like solc (the Solidity compiler) and solhint (the Solidity linter), this skill provides an end-to-end development loop. It allows developers to write, lint, compile, and perform security analysis on .sol files directly through the agent. Whether you are building complex DeFi protocols, NFTs, or ClawChain-specific pallets, this skill automates the verification process, ensuring code quality and adherence to security best practices such as the Checks-Effects-Interactions pattern.

Installation

To enable this skill, run the following command in your terminal: clawhub install openclaw/skills/skills/bowen31337/solidity-lsp. Ensure you have Node.js and npm installed on your system. You must also install the global dependencies via npm install -g solc solhint. For advanced static analysis, the skill supports integration with slither, which can be installed via pip3 install slither-analyzer. Verification of the installation is simple: execute solcjs --version and solhint --version to confirm your environment is correctly configured.

Use Cases

This skill is ideal for smart contract engineers who need to maintain clean, audit-ready code. Primary use cases include: 1. Continuous linting of development contracts to enforce style guides and safety rules defined in .solhint.json. 2. Rapid compilation and binary/ABI generation for contract deployments. 3. Automated security scanning to detect common vulnerabilities such as reentrancy or integer overflows. 4. Gas optimization feedback during the prototyping phase. 5. Providing contextual intelligence for ClawChain pallet development by resolving syntax errors and reporting compiler version mismatches.

Example Prompts

1. "Check the current smart contract for security vulnerabilities and highlight any gas optimization opportunities using solhint."
2. "Compile the contract located in the ./contracts directory and generate the ABI files, making sure to enable optimization."
3. "Analyze the vulnerabilities in the provided smart contract code and suggest refactors to align with the Checks-Effects-Interactions pattern."

Tips & Limitations

To maximize the utility of the solidity-lsp skill, always maintain a clean .solhint.json configuration file at the root of your project to standardize security rules across your team. Be aware that while solhint handles static analysis, it does not replace a professional smart contract audit. Always use slither for deeper security insights. Remember that compiler versions must explicitly match your project's pragma statements to avoid deployment errors. If you are using frameworks like Hardhat or Foundry, ensure those environments are correctly linked, as this skill acts as a companion to, rather than a replacement for, full-featured development frameworks.