solidity-security

Inspect Solidity contracts and apply reentrancy guards and CEI patterns.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/kaynetik/skills --skill solidity-security-kaynetik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solidity-security
Source: https://github.com/kaynetik/skills/tree/main/solidity-security
Command: npx skills add https://github.com/kaynetik/skills --skill solidity-security-kaynetik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Solidity developers often ship insecure contracts; this Skill provides secure coding patterns, vulnerability prevention guidance, and audit preparation to reduce risk.

Core Features & Use Cases

  • Prevent common vulnerabilities like reentrancy, overflow, and insecure access control in Solidity code.
  • Provide secure patterns, testing guidance, and readiness checks for professional audits.
  • Use case: When reviewing or coding a Solidity contract, apply these patterns to harden code and prepare audit artifacts.

Quick Start

Inspect your Solidity contract and apply reentrancy guards and CEI patterns to the critical state-changing functions.

Frequently Asked Questions about solidity-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent reentrancy attacks in my Solidity smart contracts?

Prevent reentrancy in Solidity smart contracts by applying the Checks-Effects-Interactions (CEI) pattern and integrating ReentrancyGuard modifiers to secure state-changing functions against malicious external calls.

What is the best way to implement secure access control in Solidity?

Implement secure access control in Solidity by applying robust pattern guidance that restricts function execution to authorized roles, preventing unauthorized access and privilege escalation vulnerabilities in your contract logic.

How do I prepare Solidity contracts for a professional security audit?

Prepare Solidity contracts for a professional security audit by applying secure coding patterns, generating audit-ready documentation, and verifying the absence of common access-control flaws and reentrancy vulnerabilities before review.

Why does the Checks-Effects-Interactions pattern matter for smart contract security?

The Checks-Effects-Interactions pattern matters for smart contract security because it ensures state variables update before external calls to untrusted contracts, mitigating reentrancy risks during complex execution flows.

Can I use these secure coding patterns during active code reviews?

Yes, you can apply these secure coding patterns during active code reviews to systematically inspect Solidity contracts, identify access-control flaws, and harden critical functions against vulnerabilities before deployment.

What common vulnerabilities should I check for when auditing Solidity code?

When auditing Solidity code, check for reentrancy, integer overflow, and insecure access control vulnerabilities by implementing robust error handling and verifying that state-changing functions follow secure patterns.