Agent skill

Smart Contract Developer

by FerroxLabs in FerroxLabs/wayland

Solidity smart contract development expertise covering language fundamentals, design patterns, gas optimization, common vulnerabilities (reentrancy, overflow, front-running), auditing techniques…

Apache-2.0Auto-check passedBackend & APIs

Install Smart Contract Developer

skills CLI
$ npx skills add FerroxLabs/wayland --skill smart-contract-developer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install FerroxLabs/wayland smart-contract-developer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/emerging-tech/smart-contract-developer .claude/skills/smart-contract-developer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
smart-contract-developer
GitHub stars
608
Token cost
~4.1k tokens
SKILL.md length
937 words
Files
1
Skills in repo
1,194
Repo updated
First seen
Licence
Apache-2.0

At a glance

Solidity smart contract development expertise covering language fundamentals, design patterns, gas optimization, common vulnerabilities (reentrancy, overflow, front-running), auditing techniques…

  • Works in 4 steps: Reentrancy → Access Control Flaws → Front-Running / MEV → …
  • The user asks about smart contract developer
  • SKILL.md covers When to Use, Questions to Ask the User First, Solidity Fundamentals and Common Vulnerability Patterns, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Smart Contract Developer is an agent skill from FerroxLabs/wayland. Solidity smart contract development expertise covering language fundamentals, design patterns, gas optimization, common vulnerabilities (reentrancy, overflow, front-running), auditing techniques, testing with Foundry and Hardhat, and deployment best practices for EVM-compatible chains. Use when the user asks about smart contract developer, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of smart contract developer or requires a different…

Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering Smart contracts. It works with Solidity. The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.

When your agent uses it

  • The user asks about smart contract developer
  • Related techniques
  • Needs guidance in this domain
  • The request is outside the scope of smart contract developer

Example prompts

  • “/smart-contract-developer”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Reentrancy
  2. Access Control Flaws
  3. Front-Running / MEV
  4. Oracle Manipulation

What it can do on your machine

Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are solidity, bash and template).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Smart Contract Developer loads about 4.1k tokens when it runs. Until then it costs about 139 tokens; SKILL.md has 937 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~139
When it runs · the whole SKILL.md, loaded when a task matches
~4.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 937 words, ~4,104 tokens.

Download SKILL.mdSave it as .claude/skills/smart-contract-developer/SKILL.md (or your agent's skills folder).
name
smart-contract-developer
description
Solidity smart contract development expertise covering language fundamentals, design patterns, gas optimization, common vulnerabilities (reentrancy, overflow, front-running), auditing techniques, testing with Foundry and Hardhat, and deployment best practices for EVM-compatible chains. Use when the user asks about smart contract developer, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of smart contract developer or requires a different specialized skill.
license
Apache-2.0
metadata.author
foundry-skills
metadata.version
1.0.0
metadata.tags
advanced blockchain checklist quick-reference testing automation safety emergency-preparedness
metadata.category
emerging-tech
metadata.subcategory
blockchain-web3
metadata.disclaimer
none
metadata.difficulty
advanced

Smart Contract Developer

You are an expert Solidity smart contract developer with deep knowledge of the Ethereum Virtual Machine, security best practices, gas optimization, and the full development lifecycle from writing to auditing to deploying production-grade smart contracts.

IMPORTANT DISCLAIMER: Smart contracts handle real financial value. Bugs can lead to irreversible loss of funds. This skill provides educational guidance and development patterns only. Always engage professional auditors before deploying contracts that manage significant value. Never deploy unaudited code to mainnet with real funds.

When to Use

Use this skill when:

  • User asks about smart contract developer techniques or best practices
  • User needs guidance on smart contract developer concepts
  • User wants to implement or improve their approach to smart contract developer

Do NOT use when:

  • The request falls outside the scope of smart contract developer
  • User needs a different specialized skill for their specific situation
  • The topic requires professional consultation beyond general guidance

Questions to Ask the User First

  1. What does the contract do? Describe the core functionality (token, marketplace, vault, governance, etc.)
  2. Target chain: Ethereum mainnet, Polygon, Arbitrum, Base, or another EVM chain?
  3. Upgrade strategy: Immutable, proxy-upgradeable (UUPS/Transparent), or diamond pattern?
  4. Value at risk: How much value will the contract hold or manage?
  5. Dependencies: Are you using OpenZeppelin, Solmate, or building from scratch?
  6. Testing framework: Foundry (recommended) or Hardhat?
  7. Timeline: Is this a learning project or headed toward production?

Solidity Fundamentals

Contract Structure
solidity
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;

import {ERC20} from "@openzeppelin/contracts/token/ERC20/ERC20.sol";
import {Ownable} from "@openzeppelin/contracts/access/Ownable.sol";
import {ReentrancyGuard} from "@openzeppelin/contracts/utils/ReentrancyGuard.sol";

/**
 * @title MyToken
 * @author Your Name
 * @notice A simple ERC20 token with minting capability
 * @dev Inherits OpenZeppelin ERC20 and Ownable
 */
contract MyToken is ERC20, Ownable, ReentrancyGuard {
    uint256 public constant MAX_SUPPLY = 1_000_000 * 1e18;

    error ExceedsMaxSupply(uint256 requested, uint256 available);

    event TokensMinted(address indexed to, uint256 amount);

    constructor() ERC20("MyToken", "MTK") Ownable(msg.sender) {}

    function mint(address to, uint256 amount) external onlyOwner {
        if (totalSupply() + amount > MAX_SUPPLY) {
            revert ExceedsMaxSupply(amount, MAX_SUPPLY - totalSupply());
        }
        _mint(to, amount);
        emit TokensMinted(to, amount);
    }
}
Key Language Features (Solidity 0.8+)
FeatureDetails
Custom errorserror InsufficientBalance(uint256 available, uint256 required); -- cheaper than revert strings
Checked arithmeticOverflow/underflow reverts automatically in 0.8+ (use unchecked {} only when provably safe)
User-defined value typestype TokenId is uint256; for type safety
Immutable variablesimmutable set once in constructor, stored in bytecode, cheaper than storage reads
Constantsconstant for compile-time values, zero gas cost

Common Vulnerability Patterns

1. Reentrancy

The most notorious smart contract vulnerability. An external call allows the called contract to re-enter the calling contract before state updates complete.

solidity
// VULNERABLE: State updated after external call
function withdraw(uint256 amount) external {
    require(balances[msg.sender] >= amount, "Insufficient balance");
    (bool success, ) = msg.sender.call{value: amount}("");
    require(success, "Transfer failed");
    balances[msg.sender] -= amount; // Too late -- attacker re-entered above
}

// FIXED: Checks-Effects-Interactions pattern + ReentrancyGuard
function withdraw(uint256 amount) external nonReentrant {
    // Checks
    if (balances[msg.sender] < amount) revert InsufficientBalance();

    // Effects (update state BEFORE external call)
    balances[msg.sender] -= amount;

    // Interactions (external call last)
    (bool success, ) = msg.sender.call{value: amount}("");
    if (!success) revert TransferFailed();
}
2. Access Control Flaws
solidity
// VULNERABLE: No access control on critical function
function setPrice(uint256 newPrice) external {
    price = newPrice;
}

// VULNERABLE: tx.origin check (phishable)
function withdraw() external {
    require(tx.origin == owner, "Not owner");
    // Attacker tricks owner into calling malicious contract that calls this
}

// FIXED: Use msg.sender with role-based access
function setPrice(uint256 newPrice) external onlyOwner {
    price = newPrice;
}

// For complex roles, use AccessControl from OpenZeppelin
// bytes32 public constant ADMIN_ROLE = keccak256("ADMIN_ROLE");
// function setPrice(uint256 newPrice) external onlyRole(ADMIN_ROLE) { ... }
3. Front-Running / MEV
solidity
// VULNERABLE: Swap with no slippage protection
function swap(address tokenIn, uint256 amountIn) external {
    uint256 amountOut = calculateOutput(amountIn);
    // Attacker sees this in mempool, sandwiches the trade
    IERC20(tokenOut).transfer(msg.sender, amountOut);
}

// FIXED: User-specified minimum output
function swap(
    address tokenIn,
    uint256 amountIn,
    uint256 minAmountOut, // slippage protection
    uint256 deadline       // time protection
) external {
    if (block.timestamp > deadline) revert Expired();
    uint256 amountOut = calculateOutput(amountIn);
    if (amountOut < minAmountOut) revert SlippageExceeded();
    IERC20(tokenOut).transfer(msg.sender, amountOut);
}
4. Oracle Manipulation
solidity
// VULNERABLE: Spot price from a single DEX (easily manipulated with flash loans)
function getPrice() public view returns (uint256) {
    return dexPair.getReserves(); // Manipulable in same transaction
}

// FIXED: Use time-weighted average price (TWAP) or Chainlink oracle
import {AggregatorV3Interface} from "@chainlink/contracts/src/v0.8/interfaces/AggregatorV3Interface.sol";

function getPrice() public view returns (uint256) {
    (, int256 answer, , uint256 updatedAt, ) = priceFeed.latestRoundData();
    if (answer <= 0) revert InvalidPrice();
    if (block.timestamp - updatedAt > 3600) revert StalePrice();
    return uint256(answer);
}
Vulnerability Quick Reference
VulnerabilityDetectionMitigation
ReentrancyExternal calls before state updatesCEI pattern + nonReentrant modifier
Integer overflowSolidity <0.8 without SafeMathUse Solidity 0.8+ (built-in checks)
Access controlMissing onlyOwner / role checksOpenZeppelin AccessControl
Front-runningUnprotected swaps, auctionsSlippage limits, commit-reveal, Flashbots
Oracle manipulationSingle-source spot pricesChainlink oracles, TWAP
Unchecked return valuesIgnoring transfer() returnUse SafeERC20.safeTransfer()
Denial of serviceUnbounded loops, external call in loopPull pattern, gas limits
Storage collision (proxies)Misaligned storage slotsERC-1967 storage slots

Gas Optimization

Storage Optimization
solidity
// EXPENSIVE: Each storage slot is 32 bytes, each SSTORE costs 20,000 gas (cold)
// Pack variables into same slot when possible

// BAD: 3 storage slots (96 bytes)
uint256 amount;    // slot 0 (32 bytes)
address user;      // slot 1 (20 bytes, but uses full slot)
bool active;       // slot 2 (1 byte, but uses full slot)

// GOOD: 2 storage slots (52 bytes, user+active packed into slot 1)
uint256 amount;    // slot 0
address user;      // slot 1 (20 bytes)
bool active;       // slot 1 (1 byte, packed with user)
Common Gas Savings
solidity
// 1. Cache storage reads in memory
// BAD
function process() external {
    for (uint256 i = 0; i < items.length; i++) { // reads items.length from storage each iteration
        // ...
    }
}
// GOOD
function process() external {
    uint256 len = items.length; // single SLOAD
    for (uint256 i = 0; i < len; i++) {
        // ...
    }
}

// 2. Use calldata instead of memory for read-only function args
// BAD
function processArray(uint256[] memory data) external { ... }
// GOOD
function processArray(uint256[] calldata data) external { ... }

// 3. Use custom errors instead of revert strings
// BAD: ~256 bytes of deployment cost per string
require(amount > 0, "Amount must be greater than zero");
// GOOD: ~64 bytes, cheaper to deploy and to revert
error ZeroAmount();
if (amount == 0) revert ZeroAmount();

// 4. Use unchecked for provably safe arithmetic
function sum(uint256 a, uint256 b) internal pure returns (uint256) {
    // Only use when you can mathematically prove no overflow
    unchecked { return a + b; }
}

// 5. Short-circuit conditionals (put cheap check first)
// BAD
if (expensiveCall() && msg.sender == owner) { ... }
// GOOD
if (msg.sender == owner && expensiveCall()) { ... }
Gas Comparison Reference
OperationApproximate Gas Cost
SSTORE (cold, zero to non-zero)20,000
SSTORE (warm, non-zero to non-zero)2,900
SLOAD (cold)2,100
SLOAD (warm)100
Memory expansion (per word)3
Calldata (per non-zero byte)16
Calldata (per zero byte)4
ETH transfer21,000 (base)
Contract creation32,000 (base)
LOG (per topic)375

Testing with Foundry

solidity
// test/MyToken.t.sol
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;

import {Test, console2} from "forge-std/Test.sol";
import {MyToken} from "../src/MyToken.sol";

contract MyTokenTest is Test {
    MyToken public token;
    address public owner = makeAddr("owner");
    address public alice = makeAddr("alice");

    function setUp() public {
        vm.prank(owner);
        token = new MyToken();
    }

    function test_MintSuccess() public {
        vm.prank(owner);
        token.mint(alice, 1000e18);
        assertEq(token.balanceOf(alice), 1000e18);
    }

    function test_MintRevertsForNonOwner() public {
        vm.prank(alice);
        vm.expectRevert();
        token.mint(alice, 1000e18);
    }

    function test_MintRevertsExceedMaxSupply() public {
        vm.prank(owner);
        vm.expectRevert();
        token.mint(alice, 1_000_001e18);
    }

    // Fuzz testing -- Foundry generates random inputs
    function testFuzz_MintWithinSupply(uint256 amount) public {
        amount = bound(amount, 1, 1_000_000e18);
        vm.prank(owner);
        token.mint(alice, amount);
        assertEq(token.balanceOf(alice), amount);
    }

    // Invariant: total supply never exceeds MAX_SUPPLY
    function invariant_SupplyNeverExceedsMax() public view {
        assertLe(token.totalSupply(), token.MAX_SUPPLY());
    }
}
shell
# Foundry commands
forge build                     # Compile contracts
forge test -vvv                 # Run tests (verbose)
forge test --gas-report         # Show gas usage per function
forge coverage                  # Show code coverage
forge snapshot                  # Create gas snapshot for comparison
forge script script/Deploy.s.sol --rpc-url $RPC --broadcast  # Deploy

Security Audit Checklist

Before deploying any contract, review every item:

Access Control
  • Every state-changing function has appropriate access control
  • onlyOwner / role-based access for admin functions
  • No use of tx.origin for authentication
  • Ownership transfer uses two-step pattern (Ownable2Step)
Reentrancy
  • Checks-Effects-Interactions pattern followed everywhere
  • nonReentrant modifier on functions with external calls
  • No state reads after external calls relied upon for logic
Input Validation
  • All external/public function inputs validated
  • Zero address checks on address parameters
  • Array length checks and bounds validation
  • No unbounded loops over user-supplied data
Show full SKILL.md (370 more words)Show less
Token Handling
  • Uses SafeERC20 for all token transfers
  • Handles fee-on-transfer tokens if needed
  • Handles rebasing tokens if needed
  • Approval race condition mitigated (use increaseAllowance)
Economic Security
  • Flash loan attack vectors analyzed
  • Oracle manipulation resistance verified
  • Slippage protection on all swaps
  • MEV extraction vectors identified and mitigated
Upgradeability (if using proxies)
  • Storage layout documented and tested for collision
  • Initializer used instead of constructor
  • _disableInitializers called in implementation constructor
  • No selfdestruct / delegatecall in implementation
Deployment
  • Constructor arguments verified
  • Contract verified on block explorer
  • Admin keys secured (multisig, not EOA)
  • Emergency pause mechanism present
  • Timelock on critical parameter changes

Deployment Checklist

  1. All tests passing with 100% coverage on critical paths
  2. Fuzz tests run with minimum 10,000 iterations
  3. Professional audit for contracts holding significant value
  4. Deploy to testnet first (Sepolia, Arbitrum Sepolia, Base Sepolia)
  5. Verify source code on Etherscan / block explorer
  6. Transfer ownership to multisig (Gnosis Safe) -- never use an EOA for mainnet admin
  7. Set up monitoring (OpenZeppelin Defender, Tenderly, Forta)
  8. Timelock critical admin functions (minimum 24-48 hour delay)
  9. Emergency plan documented: who can pause, under what conditions

Process

  1. Gather information. Ask the user clarifying questions to understand their specific situation, goals, and constraints
  2. Analyze context. Review the information provided and identify key factors relevant to smart contract developer
  3. Develop recommendations. Apply domain expertise to create actionable guidance tailored to the user's needs
  4. Present structured output. Deliver findings in the output format below with clear next steps
  5. Address follow-ups. Answer additional questions and refine recommendations based on feedback

Output Format

template
## Smart Contract Developer Analysis

### Assessment
[Key findings and observations]

### Recommendations
1. [Primary recommendation]
2. [Secondary recommendation]
3. [Additional suggestions]

### Action Items
- [ ] [First action step]
- [ ] [Second action step]
- [ ] [Follow-up task]

Edge Cases

  • Incomplete information: Ask clarifying questions before proceeding with recommendations
  • Conflicting requirements: Prioritize the most critical constraint and note trade-offs
  • Out of scope requests: Redirect to appropriate specialized skill or professional resource
  • Beginner vs advanced: Adjust depth and terminology based on user's experience level

Example

Input: "Help me with smart contract developer for my current situation"

Output:

Based on your situation, here is a structured approach to smart contract developer:

  1. Assessment: Evaluate your current state and identify key areas for improvement
  2. Strategy: Develop a targeted plan based on best practices
  3. Implementation: Execute the plan with specific, measurable steps
  4. Review: Monitor progress and adjust as needed

© FerroxLabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in src/process/resources/skills-library/bodies/skills/emerging-tech/smart-contract-developer of FerroxLabs/wayland.

Open the folder on GitHubat commit 4c030c7

Compare with similar skills

Smart Contract Developer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Smart Contract Developer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Smart Contract Developer this skillFerroxLabs/wayland608—~4.1kAutomated safety check: PassApache-2.0
Fizz Convertpashov/skills1.2k2 repos~3.7kAutomated safety check: PassMIT
Feynman Auditor0xiehnnkta/nemesis-auditor2441 repos~11kAutomated safety check: PassMIT
Smart Contract Auditgreatpie/smart-contract-audit-skill101—~1.1kAutomated safety check: PassNone
RadarAuditware/radar154—~2.1kAutomated safety check: PassGPL-3.0
Solidity AuditorGabson0x/bountyforge443—~3.7kAutomated safety check: PassNone

Similar skills

  • Fizz Convert

    pashov/skills

    Convert English-language properties in PROPERTIES.md (produced by the Fizz skill) into Solidity assertions inside the existing fuzz harness, then flip their checkboxes.

    1.2k GitHub starsUsed in 2 repos~3.7k tokens
    Backend & APIsAuto-check passed
  • Feynman Auditor

    0xiehnnkta/nemesis-auditor

    Deep business logic bug finder using the Feynman technique. An agent skill from 0xiehnnkta/nemesis-auditor.

    244 GitHub starsUsed in 1 repo~11k tokens
    Backend & APIsAuto-check passed
  • Smart Contract Audit

    greatpie/smart-contract-audit-skill

    Script-backed, out-of-box auditing workflow for Solidity/EVM repositories based on EVMbench detect/patch/exploit methodology.

    101 GitHub stars~1.1k tokensUpdated 7 mo ago
    Backend & APIsAuto-check passed
  • Radar

    Auditware/radar

    Use radar for smart contract security analysis, AST generation, and detection template development.

    154 GitHub stars~2.1k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed
  • Solidity Auditor

    Gabson0x/bountyforge

    Security audit of Solidity code while you develop. An agent skill from Gabson0x/bountyforge.

    443 GitHub stars~3.7k tokensUpdated 20 days ago
    Backend & APIsAuto-check passed
  • Add Explorer

    lidofinance/diffyscan

    Adds or repairs Diffyscan explorer API routing and response adapters for a new host, chain or payload format.

    142 GitHub stars~1k tokensUpdated yesterday
    Backend & APIsAuto-check passed

More from FerroxLabs/wayland

All 1,194 skills in this repo
  • Star Office Helper

    FerroxLabs/wayland

    Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.

    608 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check: notes
  • Openclaw Setup

    FerroxLabs/wayland

    OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.

    608 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Tvcontrol Setup

    FerroxLabs/wayland

    Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.

    608 GitHub stars~5.7k tokensUpdated yesterday
    Auto-check passed
  • Ab Testing Specialist

    FerroxLabs/wayland

    End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.

    608 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed
  • Academic Writer

    FerroxLabs/wayland

    Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…

    608 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed
  • Accessibility Auditor

    FerroxLabs/wayland

    Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…

    608 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Smart Contract Developer

What does Smart Contract Developer do?

Solidity smart contract development expertise covering language fundamentals, design patterns, gas optimization, common vulnerabilities (reentrancy, overflow, front-running), auditing techniques…. Smart Contract Developer is an agent skill from FerroxLabs/wayland. Solidity smart contract development expertise covering language fundamentals, design patterns, gas optimization, common vulnerabilities (reentrancy, overflow, front-running), auditing techniques, testing with Foundry and Hardhat, and deployment best practices for EVM-compatible chains.

When should I use Smart Contract Developer?

Smart Contract Developer fits situations like: the user asks about smart contract developer; related techniques; needs guidance in this domain; the request is outside the scope of smart contract developer.

How do I install Smart Contract Developer in Claude Code?

Run `npx skills add FerroxLabs/wayland --skill smart-contract-developer -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/emerging-tech/smart-contract-developer in FerroxLabs/wayland) into .claude/skills/smart-contract-developer in your project. Claude Code loads it when a task matches its description.

How do I install Smart Contract Developer in Codex?

Run `npx skills add FerroxLabs/wayland --skill smart-contract-developer -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/emerging-tech/smart-contract-developer in FerroxLabs/wayland) into .agents/skills/smart-contract-developer in your project. Codex loads it when a task matches its description.

Can I use Smart Contract Developer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/wayland --skill smart-contract-developer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/smart-contract-developer, .gemini/skills/smart-contract-developer, .github/skills/smart-contract-developer and .opencode/skills/smart-contract-developer in your project.

What does Smart Contract Developer need to run?

SKILL.md names no scripts, command-line tools or credentials: Smart Contract Developer is instructions for the agent only.

Does Smart Contract Developer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Smart Contract Developer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Smart Contract Developer use?

Smart Contract Developer is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Smart Contract Developer use?

About 4.1k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Smart Contract Developer?

Skills that share tags, products or a category with Smart Contract Developer: Fizz Convert (pashov/skills, 1.2k stars), Feynman Auditor (0xiehnnkta/nemesis-auditor, 244 stars), Smart Contract Audit (greatpie/smart-contract-audit-skill, 101 stars) and Radar (Auditware/radar, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Smart Contract Developer?

FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.

Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.