Skip to content
cccskills
FreePublished on GitHub

web3-smart-contract-engineering

Use when writing, reviewing, or deploying Solidity smart contracts — token contracts, signature-gated claim systems, merkle-gated staking vaults, allocation modules, role-based proxies, or factory patterns. Triggers on edits to `*.sol` files, `hardhat.config.*`, `foundry.toml`, deploy scripts, or mentions of "smart contract", "Solidity", "Web3", "EVM", "Hardhat", "Foundry", "ERC20/721/1155", "merkle", "staking", or "on-chain". For security audits and adversarial review see security-engineering.

The English summary is being prepared. Showing the original description.

See how to install

Files included (13)

  • SKILL.md4.6 KB
  • references/allocation-module.md1.3 KB
  • references/deployment.md1.1 KB
  • references/erc4626-staking-vault.md1.3 KB
  • references/frameworks-and-tooling.md3.0 KB
  • references/governance-and-factories.md1.9 KB
  • references/merkle-proofs.md1.0 KB
  • references/networks-and-config.md1.9 KB
  • references/security-rules.md2.0 KB
  • references/signature-verification.md1.8 KB
  • references/testing-patterns.md3.1 KB
  • references/token-contracts.md2.2 KB
  • references/velocity-control.md945 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Web3 / Smart Contract Engineering

You are operating as a smart contract engineer. Treat every line as adversarial surface: assume the caller is hostile, the mempool is public, and a deployed bug is permanent.

Reference stack: Hardhat + Foundry hybrid environment using Solidity 0.8.2–0.8.30, OpenZeppelin Contracts ^5.3.0 (with upgradeable variants), Ethers.js v6, and Thirdweb deploy tooling. Designed to be multi-chain across EVM L1s, L2s, and ZK rollups. Contract patterns covered include ERC20/721/1155 tokens, signature-gated payouts, merkle-gated staking, allocation/launch modules, and role-based multi-sig proxies. For adversarial review and audit checklists see security-engineering.

Universal Rules

  1. Never store private keys in code or config — use environment variables.
  2. Always verify contracts on block explorers after deployment.
  3. Record every deployment in a tracked manifest (e.g. deploys.ts) with address, args, and verify command.
  4. Test on testnet first — appropriate testnet (Sepolia, Amoy, etc.) before mainnet.
  5. Run Slither (npm run lint) before any mainnet deployment.
  6. Optimizer enabled at 200 runs for all production deployments.
  7. Include deadline parameters in all signature-gated functions.
  8. Emit events for all state-changing operations — indexers depend on them.
  9. Use OpenZeppelin for ECDSA, MerkleProof, AccessControl, ReentrancyGuard, Pausable, SafeERC20 — never roll your own.
  10. Always include block.chainid and address(this) in signed-data hashes; track usedHashes to prevent replay.

References

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when adversarially reviewing a document that makes formal or technical claims — math derivations, physics papers, statistical analyses, benchmark reports, whitepapers. Inventories every equation and quantitative claim, verifies each AS NAMED in the text (never a paraphrase or a neighboring statement), and classifies VERIFIED / REFUTED / UNVERIFIABLE / VACUOUS. Triggers on "check this paper", "verify these claims", "is this derivation right", "review this proof", "audit this benchmark", "does the math hold up". For source-code review see code-review-and-quality; for skill/agent library audits see skill-library-review; for content quality scoring see content-ops.

The English summary is being prepared. Showing the original description.

LazyIsEfficient/agentic-os17Updated Jul 17, 2026

Run Karpathy-style autoresearch optimization on any content. Generates 50+ variants, scores with a 5-expert simulated panel, evolves winners through multiple rounds, outputs optimized version + full experiment log. Use when optimizing landing pages, email sequences, ad copy, headlines, form pages, CTA text, or any conversion-focused content. Triggers on "optimize this page", "run autoresearch", "score these variants", "A/B test this copy".

The English summary is being prepared. Showing the original description.

LazyIsEfficient/agentic-os17Updated Jul 17, 2026

Tests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data via Chrome DevTools MCP.

The English summary is being prepared. Showing the original description.

LazyIsEfficient/agentic-os17Updated Jul 17, 2026

Conducts multi-axis code review across correctness, readability, architecture, security, and performance. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Triggers on "review my PR", "review this diff", "code review", "review this changeset", "is this ready to merge", "pre-merge review".

The English summary is being prepared. Showing the original description.

LazyIsEfficient/agentic-os17Updated Jul 17, 2026

Estimate the full development cost of an existing codebase from lines of code, architectural complexity, and team-composition overhead. Use for 'how much would this cost to build', 'what did this codebase cost', development-cost or build-cost estimates, calendar-time estimates, and Claude/AI ROI on a delivered codebase. Estimates by measured LOC and complexity, not by ticket volume.

The English summary is being prepared. Showing the original description.

LazyIsEfficient/agentic-os17Updated Jul 17, 2026

Auto-assembles a domain-specific expert panel (7–10 experts), scores any content or strategy artifact against a typed rubric, and iterates until the aggregate hits 90+ (max 3 rounds). Use as a quality gate on copy, email sequences, landing-page drafts, strategy docs, charts, titles, or recruiting evaluations — or when another skill needs a final review gate on its output. Triggers on "expert panel this", "score this", "rate these variants", "quality check this", "panel review", "expert score", "evaluate this copy/strategy/page". For variant generation and multi-round conversion optimization see autoresearch; for live-URL CRO auditing see conversion-ops; for the scripted content-production pipeline see content-pipeline.

The English summary is being prepared. Showing the original description.

LazyIsEfficient/agentic-os17Updated Jul 17, 2026

See all skills by LazyIsEfficient

Report a problem with this skill