Skip to content
TrustedSkillsbeta
Back to all skills

Solidity Security

Checked
wshobson·vlatest·security·MIT

Identifies common Solidity vulnerabilities like reentrancy, overflows, and front running in smart contracts.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add wshobson/agents --skill solidity-security -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

wshobson

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned wshobson/agents at 46891e7e60.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
2 files, 461 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The solidity-security skill helps identify and mitigate security vulnerabilities in Solidity smart contracts. It analyzes contract code to detect common issues such as reentrancy, overflow/underflow, improper access control, and unsafe external calls.

When to use it

  • Before deploying a new Solidity-based decentralized application (dApp) to ensure its security.
  • During audits or code reviews of existing smart contracts.
  • When integrating third-party contracts into your project and want to assess their safety.
  • To automate routine security checks as part of a CI/CD pipeline for blockchain projects.

Key capabilities

  • Detection of reentrancy vulnerabilities
  • Identification of overflow and underflow issues
  • Analysis of access control mechanisms
  • Recognition of unsafe external calls or delegatecall usage

Example prompts

  • "Analyze this Solidity contract for security vulnerabilities."
  • "Check if this smart contract is susceptible to reentrancy attacks."
  • "Review the code for improper access controls and suggest fixes."

Tips & gotchas

  • Ensure that the provided Solidity code is complete and includes all relevant dependencies.
  • This skill may not detect logic flaws or business-specific vulnerabilities, so it should be used alongside manual review or advanced tools.