Skip to content
TrustedSkillsbeta
Back to all skills

Solidity Debug

Checked
0xlayerghost·vlatest·testing·MIT

Identifies potential vulnerabilities and errors in Solidity code through static analysis and automated debugging suggestions.

Repository

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 0xlayerghost/solidity-agent-kit --skill solidity-debug -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

0xlayerghost

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 0xlayerghost/solidity-agent-kit at ad854ef3a7.

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

Commit
ad854ef3a7
Manifest
skills/solidity-debug/SKILL.md
Scanned
1 file, 120 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

The solidity-debug skill enables AI agents to analyze Solidity smart contracts for vulnerabilities, logic errors, and optimization opportunities. It leverages static analysis techniques to inspect bytecode and source code without requiring a live blockchain environment.

When to use it

  • Reviewing newly written smart contract code before deployment to catch reentrancy or overflow risks.
  • Auditing third-party libraries integrated into your project for known security flaws.
  • Generating detailed reports on gas inefficiencies within complex transaction flows.
  • Validating that specific security patterns, such as checks-effects-interactions, are correctly implemented.

Key capabilities

  • Performs deep static analysis of Solidity source files.
  • Identifies common vulnerability classes like reentrancy and integer overflows.
  • Provides actionable recommendations for code refactoring.
  • Supports multiple Solidity versions for compatibility checking.

Example prompts

  • "Analyze this ERC-20 token contract for potential security vulnerabilities and list the high-risk functions."
  • "Review the provided smart contract logic to identify any gas optimization opportunities in the transfer function."
  • "Check if this bridge contract correctly implements the checks-effects-interactions pattern to prevent reentrancy attacks."

Tips & gotchas

Ensure you provide the full source code or a complete file path, as partial snippets may lead to incomplete analysis. While effective for static issues, remember that this skill does not simulate live network interactions or runtime state changes.