Ethskills
austintgriffith/ethskills
Ethereum development knowledge for AI agents — from idea to deployed dApp.
Solidity smart contract development guidelines for Lineth blockchain.
Install Developing Smart Contracts
$ npx skills add LFDT-Lineth/lineth-monorepo --skill developing-smart-contracts -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LFDT-Lineth/lineth-monorepo developing-smart-contracts --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/LFDT-Lineth/lineth-monorepo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/developing-smart-contracts .claude/skills/developing-smart-contracts && rm -rf skills-srcUse ~/.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/
Install the "developing-smart-contracts" agent skill from https://github.com/LFDT-Lineth/lineth-monorepo/tree/main/.agents/skills/developing-smart-contracts into .claude/skills/developing-smart-contracts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developing-smart-contracts", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/LFDT-Lineth/lineth-monorepo/tree/main/.agents/skills/developing-smart-contractsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add LFDT-Lineth/lineth-monorepo --skill developing-smart-contracts -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LFDT-Lineth/lineth-monorepo developing-smart-contracts --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LFDT-Lineth/lineth-monorepo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/developing-smart-contracts .agents/skills/developing-smart-contracts && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "developing-smart-contracts" agent skill from https://github.com/LFDT-Lineth/lineth-monorepo/tree/main/.agents/skills/developing-smart-contracts into .agents/skills/developing-smart-contracts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developing-smart-contracts", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LFDT-Lineth/lineth-monorepo --skill developing-smart-contracts -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LFDT-Lineth/lineth-monorepo developing-smart-contracts --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LFDT-Lineth/lineth-monorepo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/developing-smart-contracts .cursor/skills/developing-smart-contracts && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "developing-smart-contracts" agent skill from https://github.com/LFDT-Lineth/lineth-monorepo/tree/main/.agents/skills/developing-smart-contracts into .cursor/skills/developing-smart-contracts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developing-smart-contracts", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/LFDT-Lineth/lineth-monorepo.git --path .agents/skills/developing-smart-contracts--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add LFDT-Lineth/lineth-monorepo --skill developing-smart-contracts -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LFDT-Lineth/lineth-monorepo developing-smart-contracts --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LFDT-Lineth/lineth-monorepo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/developing-smart-contracts .gemini/skills/developing-smart-contracts && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "developing-smart-contracts" agent skill from https://github.com/LFDT-Lineth/lineth-monorepo/tree/main/.agents/skills/developing-smart-contracts into .gemini/skills/developing-smart-contracts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developing-smart-contracts", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install LFDT-Lineth/lineth-monorepo developing-smart-contractsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add LFDT-Lineth/lineth-monorepo --skill developing-smart-contracts -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LFDT-Lineth/lineth-monorepo.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/developing-smart-contracts .github/skills/developing-smart-contracts && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "developing-smart-contracts" agent skill from https://github.com/LFDT-Lineth/lineth-monorepo/tree/main/.agents/skills/developing-smart-contracts into .github/skills/developing-smart-contracts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developing-smart-contracts", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LFDT-Lineth/lineth-monorepo --skill developing-smart-contracts -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LFDT-Lineth/lineth-monorepo developing-smart-contracts --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LFDT-Lineth/lineth-monorepo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/developing-smart-contracts .opencode/skills/developing-smart-contracts && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "developing-smart-contracts" agent skill from https://github.com/LFDT-Lineth/lineth-monorepo/tree/main/.agents/skills/developing-smart-contracts into .opencode/skills/developing-smart-contracts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developing-smart-contracts", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
developing-smart-contracts- GitHub stars
- 126
- Token cost
- ~1.4k tokens
- SKILL.md length
- 423 words
- Files
- 10
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Solidity smart contract development guidelines for Lineth blockchain.
- Works in 7 steps: Gas Optimization (CRITICAL) → NatSpec Docstrings (HIGH) → File Layout (HIGH) → …
- Refactoring Solidity contracts
- SKILL.md covers When to Apply, Licenses, Solidity Pragma and Rule Categories by Priority, plus 4 more sections
- Calls pnpm
What it does
Developing Smart Contracts is an agent skill from LFDT-Lineth/lineth-monorepo. Solidity smart contract development guidelines for Lineth blockchain. Use when writing, reviewing, or refactoring Solidity contracts, or when the user asks about Solidity best practices, contract structure, or NatSpec docstrings. Covers NatSpec documentation, naming conventions, file layout, and code style.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files (for example `metadata.json`, `rules/commands.md` and `rules/file-layout.md`).
It sits in Backend & APIs, covering Smart contracts and Technical documentation. It works with Solidity and Ethereum. The repository describes itself as: The principal Lineth repository. Lineth is an enterprise-grade EVM layer 2 framework for developing public, permissioned or private networks. Its modular and versatile design… The licence is AGPL-3.0.
When your agent uses it
- Refactoring Solidity contracts
- The user asks about Solidity best practices
- Contract structure
- NatSpec docstrings
Example prompts
- “/developing-smart-contracts”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 75baf30. 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
Shell commands in SKILL.md call:
pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
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
Developing Smart Contracts loads about 1.4k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 423 words of instructions outside code blocks.
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 LFDT-Lineth/lineth-monorepo at commit 75baf30, republished under its AGPL-3.0 licence (© LFDT-Lineth). 423 words, ~1,439 tokens.
Download SKILL.mdSave it as
.claude/skills/developing-smart-contracts/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.- name
- developing-smart-contracts
- description
- Solidity smart contract development guidelines for Lineth blockchain. Use when writing, reviewing, or refactoring Solidity contracts, or when the user asks about Solidity best practices, contract structure, or NatSpec docstrings. Covers NatSpec documentation, naming conventions, file layout, and code style.
- license
- AGPL-3.0
- metadata.author
- linea
- metadata.version
- 1.0.0
Lineth Smart Contract Development
Best practices for developing Solidity smart contracts on Lineth blockchain. Contains rules covering documentation, naming, structure, and code style.
Reference: Lineth Contract Style Guide
When to Apply
Reference these guidelines when:
- Writing new Solidity contracts for Lineth
- Reviewing smart contract code
- Refactoring existing contracts
- Adding NatSpec docstring documentation
- Setting up contract file structure
Licenses
// SPDX-License-Identifier: Apache-2.0 OR MIT
Solidity Pragma
- Contracts:
0.8.33(exact) - Interfaces, abstract contracts, libraries:
^0.8.33(caret)
Rule Categories by Priority
| Priority | Category | Impact | Rule File |
|---|---|---|---|
| 1 | Gas optimization | CRITICAL | rules/gas-optimization.md |
| 2 | NatSpec Docstrings | HIGH | rules/natspec.md |
| 3 | File Layout | HIGH | rules/file-layout.md |
| 4 | Naming | HIGH | rules/naming-conventions.md |
| 5 | Imports | MEDIUM | rules/imports.md |
| 6 | Visibility | MEDIUM | rules/visibility.md |
| 7 | General Rules | MEDIUM | rules/general-rules.md |
Read individual rule files for detailed explanations and code examples (correct and incorrect).
Quick Reference
1. Gas Optimization (CRITICAL)
Gas efficiency is critical for Lineth contracts. Apply these rules unless there is a documented safety, audit, or readability reason to deviate.
// Correct: external + calldata, cache storage reads
function submit(bytes32[] calldata _proofs) external {
uint256 current = fee;
require(current != 0, FeeNotSet());
_verify(_proofs, current);
}
// Incorrect: public + memory, repeated storage reads
function submit(bytes32[] memory _proofs) public {
require(fee != 0, FeeNotSet());
_verify(_proofs, fee);
}See rules/gas-optimization.md for details.
2. NatSpec Docstrings (HIGH)
ALWAYS use NatSpec docstrings for all public/external items.
// Correct: complete NatSpec with @notice, @param (in signature order), @return
/**
* @notice Sends a message to L2.
* @param _to The recipient address on L2.
* @param _fee The fee amount in wei.
* @return messageHash The hash of the sent message.
*/
function sendMessage(address _to, uint256 _fee) external payable returns (bytes32 messageHash);Every contract/interface NatSpec block must include @author Consensys Software Inc. and @custom:security-contact security-report@linea.build.
Consult rules/natspec.md for NatSpec docstring rules and examples
3. File Layout (HIGH)
Interface structure:
- Structs → 2. Enums → 3. Events → 4. Errors → 5. External Functions
Contract structure:
- Using statements → 2. Constants → 3. State variables → 4. Structs → 5. Enums → 6. Events → 7. Errors → 8. Modifiers → 9. Functions
See rules/file-layout.md for templates.
4. Naming Conventions (HIGH)
See rules/naming-conventions.md for symbol naming conventions.
5. Imports (MEDIUM)
Always use named imports. Always insert a blank line after imports.
// Correct: named imports with blank line before NatSpec/contract declaration
import { IMessageService } from "../interfaces/IMessageService.sol";
import { Ownable } from "@openzeppelin/contracts/access/Ownable.sol";
/**
* @title Brief description.
* @author Consensys Software Inc.
* @custom:security-contact security-report@linea.build
*/
contract MessageService is IMessageService, Ownable {See rules/imports.md for details.
Show full SKILL.md (178 more words)Show less
6. Visibility (MEDIUM)
See rules/visibility.md for rules on applying visibility modifiers (internal, external, public, etc).
7. General Rules (MEDIUM)
See rules/general-rules.md for inheritance and general style rules
Development Workflow
Follow this sequence when writing or modifying Solidity contracts:
- Write/modify contract applying rules from the priority table above.
- Compile and fix errors:
bash pnpm -F contracts run build - Run linter and fix warnings:
bash pnpm -F contracts run lint:fix - Run tests to verify behavior:
bash pnpm -F contracts run test - Verify NatSpec coverage: confirm all public/external functions, events, and errors have complete docstrings with
@notice,@param(in signature order), and@return. - Review gas patterns: check for unnecessary
memorycopies, repeated storage reads, and missing batch limits. - Commit after passing the checklist below.
Commit Checklist
Before making a commit, please verify:
- Rules on licenses and Solidity pragma have been applied
- All public items have NatSpec docstrings (
@notice,@param,@return) - All rules in
rules/*.mdhave been applied - Linting passes (
pnpm -F contracts run lint:fix)
Commands
For commands for testing and linting, refer to rules/commands.md
© LFDT-Lineth, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 9 other files in .agents/skills/developing-smart-contracts of LFDT-Lineth/lineth-monorepo.
- SKILL.md
- metadata.json
- rules/commands.md
- rules/file-layout.md
- rules/gas-optimization.md
- rules/general-rules.md
- rules/imports.md
- rules/naming-conventions.md
- rules/natspec.md
- rules/visibility.md
Open the folder on GitHubat commit 75baf30
Compare with similar skills
Developing Smart Contracts 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Developing Smart Contracts this skillLFDT-Lineth/lineth-monorepo | 126 | — | ~1.4k | Automated safety check: Pass | AGPL-3.0 | |
| Ethskillsaustintgriffith/ethskills | 294 | — | ~1.4k | Automated safety check: Pass | None | |
| Smart Contract Developmentvechain/x-app-template | 450 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Smart Contract Guidelines Advisortrailofbits/skills | 7.4k | — | ~2.2k | Automated safety check: Pass | CC-BY-SA-4.0 | |
| Foundry Reference Modelaviggiano/security | 144 | — | ~516 | Automated safety check: Pass | MIT | |
| Smart Contract InteractionNethereum/Nethereum | 2.3k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Smart Contract Development
vechain/x-app-template
Solidity smart contract development on VeChainThor — Hardhat setup, ERC-20/721 patterns, upgradeable contracts, gas optimization, testing with Thor Solo, security auditing, and ABI codegen.
- Official
Smart Contract Guidelines Advisor
trailofbits/skills
Reviews a smart contract project against Trail of Bits development guidelines, covering documentation, architecture, upgradeability, implementation quality, dependencies and tests.
Foundry Reference Model
aviggiano/security
Build a simple independent Solidity reference implementation for Foundry tests.
Smart Contract Interaction
Nethereum/Nethereum
Interact with Ethereum smart contracts using Nethereum typed DTOs.
Solidity Development
hiromaily/go-crypto-wallet
Solidity smart contract development workflow. An agent skill from hiromaily/go-crypto-wallet.
More from LFDT-Lineth/lineth-monorepo
Squash Bugbot
LFDT-Lineth/lineth-monorepo
Triage unresolved bot review comments on a GitHub PR. An agent skill from LFDT-Lineth/lineth-monorepo.
Lineth Quickstart
LFDT-Lineth/lineth-monorepo
Operating manual for the Lineth Stack quickstart — the Docker-Compose dev/demo stack at docs/getting-started/lineth-stack in the lineth-monorepo that boots a local Linea/Lineth L2 with Sepolia or…
Related
Categories
Questions about Developing Smart Contracts
What does Developing Smart Contracts do?
Solidity smart contract development guidelines for Lineth blockchain. Developing Smart Contracts is an agent skill from LFDT-Lineth/lineth-monorepo. Solidity smart contract development guidelines for Lineth blockchain.
When should I use Developing Smart Contracts?
Developing Smart Contracts fits situations like: refactoring Solidity contracts; the user asks about Solidity best practices; contract structure; natSpec docstrings.
How do I install Developing Smart Contracts in Claude Code?
Run `npx skills add LFDT-Lineth/lineth-monorepo --skill developing-smart-contracts -a claude-code`. Or copy the skill folder (.agents/skills/developing-smart-contracts in LFDT-Lineth/lineth-monorepo) into .claude/skills/developing-smart-contracts in your project. Claude Code loads it when a task matches its description.
How do I install Developing Smart Contracts in Codex?
Run `npx skills add LFDT-Lineth/lineth-monorepo --skill developing-smart-contracts -a codex`. Or copy the skill folder (.agents/skills/developing-smart-contracts in LFDT-Lineth/lineth-monorepo) into .agents/skills/developing-smart-contracts in your project. Codex loads it when a task matches its description.
Can I use Developing Smart Contracts 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 LFDT-Lineth/lineth-monorepo --skill developing-smart-contracts -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/developing-smart-contracts, .gemini/skills/developing-smart-contracts, .github/skills/developing-smart-contracts and .opencode/skills/developing-smart-contracts in your project.
What does Developing Smart Contracts need to run?
Going by SKILL.md and its folder, Developing Smart Contracts needs the command-line tools its instructions call (pnpm).
Does Developing Smart Contracts 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 Developing Smart Contracts 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 Developing Smart Contracts use?
Developing Smart Contracts is published under the AGPL-3.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Developing Smart Contracts use?
About 1.4k tokens (SKILL.md is roughly 5.8k 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 Developing Smart Contracts?
Skills that share tags, products or a category with Developing Smart Contracts: Ethskills (austintgriffith/ethskills, 294 stars), Smart Contract Development (vechain/x-app-template, 450 stars), Smart Contract Guidelines Advisor (trailofbits/skills, 7.4k stars) and Foundry Reference Model (aviggiano/security, 144 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Developing Smart Contracts?
LFDT-Lineth (a GitHub organization) maintains it in LFDT-Lineth/lineth-monorepo, which has 126 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 6, 2026.
Source: LFDT-Lineth/lineth-monorepo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.