SkillsAdd

omer-metin/skills-for-antigravity

smart-contract-engineer

Blockchain smart contract specialist for Solidity, EVM, security patterns, and gas optimizationUse when "smart contract, solidity, ethereum, evm, contract, web3, gas optimization, upgradeable contract, reentrancy, solidity, ethereum, smart-contracts, evm, web3, blockchain, defi, nft, security, gas" mentioned.

First seen Jan 25, 2026

Installation

$ npx skills add omer-metin/skills-for-antigravity --skill smart-contract-engineer
View on skills.sh ↗ GitHub repository ↗

Summary

Blockchain smart contract specialist for Solidity, EVM, security patterns, and gas optimizationUse when "smart contract, solidity, ethereum, evm, contract, web3, gas optimization, upgradeable contract, reentrancy, solidity, ethereum, smart-contracts, evm, web3, blockchain, defi, nft, security, gas" mentioned.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

review-contract Similar name
anthropics/knowledge-work-plugins

Review a contract against your organization's negotiation playbook — flag deviations, generate …

3.2K installs
contract-review Similar name
anthropics/knowledge-work-plugins

Lightweight NDA, MSA, and vendor contract review for SMBs without legal on staff. Reads contrac…

2.2K installs
prisma-next-contract Similar name
prisma/prisma-next

Edit the Prisma Next data contract — add models, fields, relations, indexes, enums, value objec…

1.3K installs
planetscale-change-gates-and-approval-contract Similar name
planetscale/skills

Enforce explicit approval gates for any PlanetScale, database, repository, credential, network,…

13 installs
typed-service-contracts Similar name
google-labs-code/design.md

Architecture standard for building robust, type-safe TypeScript services using the "Spec and Ha…

13 installs
doca-structured-tools-contract Similar name
nvidia/skills

Use this skill whenever another DOCA skill says "prefer the structured tool per doca-structured…

119 installs

Also in this package

Other skills from omer-metin/skills-for-antigravity · top by installs.

npx skills add omer-metin/skills-for-antigravity
game-ui-design 3K quantitative-research 2.5K pixel-art-sprites 2.1K technical-analysis 1.9K 3d-modeling 1.0K crypto-trading-bots 880 algorithmic-trading 498 gamification-loops 473 threejs-3d-graphics 442 landing-page-design 435

Browse all from omer-metin/skills-for-antigravity

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 142
License LICENSE
Default branch main
Open issues 1
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents antigravity

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,277 B
  • docs SUMMARY.md 341 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 38 installs

SKILL.md

Smart Contract Engineer

Identity

You are a smart contract engineer who has deployed contracts holding billions in TVL. You understand that blockchain code is immutable - bugs can't be patched, only exploited. You've studied every major hack and know the patterns that lead to catastrophic losses.

Your core principles:

  1. Security is not optional - one bug = total loss of funds
  2. Gas optimization matters - users pay for every operation
  3. Immutability is a feature and a constraint - design for it
  4. Test everything, audit everything, then test again
  5. Upgradability adds risk - use only when necessary

Contrarian insight: Most developers think upgradeability makes contracts safer. It doesn't. Every upgrade mechanism is an attack vector. The safest contracts are immutable with well-designed escape hatches. If you need to upgrade, you didn't understand the requirements.

What you don't cover: Frontend integration, backend services, tokenomics. When to defer: DeFi mechanics (defi-architect), wallet UX (wallet-integration), security audit (security-analyst).

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

  • For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
  • For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
  • For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.