Agent skill

Smart Contract Formal Verification

by sickn33 in sickn33/agentic-awesome-skills

Foundry and Soroban formal invariant verification register: state transition rules, boundary invariant properties, and symbolic execution checks.

MITAuto-check passedBackend & APIs

Install Smart Contract Formal Verification

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill smart-contract-formal-verification -a claude-code

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

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills smart-contract-formal-verification --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/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/smart-contract-formal-verification .claude/skills/smart-contract-formal-verification && 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-formal-verification
GitHub stars
47k
Used in
1 other repo
Token cost
~1.4k tokens
SKILL.md length
508 words
Files
1
Skills in repo
1,497
Repo updated
First seen
Licence
MIT

At a glance

Foundry and Soroban formal invariant verification register: state transition rules, boundary invariant properties, and symbolic execution checks.

  • Works in 3 steps: Define the parameters, thresholds, and… → Select appropriate boundary enforcement… → Export standardized artifacts (CSV…
  • Tasks that involve Smart contracts
  • SKILL.md covers Overview, When to Use This Skill, How It Works and Field Reference, plus 9 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Smart Contract Formal Verification is an agent skill from sickn33/agentic-awesome-skills. Foundry and Soroban formal invariant verification register: state transition rules, boundary invariant properties, and symbolic execution checks.

Its SKILL.md is about 1.4k 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 and Smart contract auditing. It works with Stellar and SQL. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Tasks that involve Smart contracts
  • Tasks that involve Smart contract auditing

Example prompts

  • “/smart-contract-formal-verification”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Define the parameters, thresholds, and identity bindings required for the target operational register.
  2. Select appropriate boundary enforcement values from validated enum select sets.
  3. Export standardized artifacts (CSV table, SQL DDL, JSON Schema) to integrate into validation CI pipelines.

What it can do on your machine

Read from SKILL.md and the folder at commit b84d35a. 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.

    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 Formal Verification loads about 1.4k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 508 words of instructions outside code blocks.

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

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 sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 508 words, ~1,389 tokens.

Download SKILL.mdSave it as .claude/skills/smart-contract-formal-verification/SKILL.md (or your agent's skills folder).
name
smart-contract-formal-verification
description
Foundry and Soroban formal invariant verification register: state transition rules, boundary invariant properties, and symbolic execution checks.
category
engineering
risk
safe
source
self
source_type
self
date_added
2026-10-01
author
Ranjeet2063
tags
formal-verification, invariants, foundry, soroban, security, math
source_repo
Ranjeet2063/agentic-awesome-skills

Smart Contract Formal Verification

What it is: Applies rigorous mathematical invariant proofs, symbolic execution engines, and property-based fuzz tests to verify smart contract safety.

Overview

Provides a standardized, auditable framework and data model for Smart Contract Formal Verification operations across distributed engineering and decentralized application systems.

When to Use This Skill

  • When formalizing architectural contracts, security invariants, or operational limits for Smart Contract Formal Verification.
  • When cross-functional review is required between protocol developers, smart contract auditors, and AI engineering agents.
  • When generating reproducible CSV, SQL DDL, JSON Schema, and Notion property registers for tracking compliance.

How It Works

  1. Define the parameters, thresholds, and identity bindings required for the target operational register.
  2. Select appropriate boundary enforcement values from validated enum select sets.
  3. Export standardized artifacts (CSV table, SQL DDL, JSON Schema) to integrate into validation CI pipelines.

Field Reference

#Field NameTypeSQL TypeJSON Schema TypeNotion Property TypeExample Value
1Formal Spec IDidSERIAL PRIMARY KEYintegerTextSPEC-001
2Target Contract ModuletextVARCHAR(64)stringTextvault_liquidity_engine
3State Transition PropertytextVARCHAR(128)stringTextTotal Assets Equals Sum of Shares
4Verification MethodselectVARCHAR(64)stringSelectFoundry Invariant Fuzzing
5Fuzz Runs CountnumberINTEGERnumberNumber100000
6Symbolic Execution EngineselectVARCHAR(32)stringSelectCertora Prover
7Counterexample DiscoveredselectVARCHAR(16)stringSelectNo
8Mathematical Theorem ProvedselectVARCHAR(16)stringSelectYes
9Invariant Violation TolerancecurrencyNUMERIC(14,2)numberNumber0.00
10Formal Verification StatusselectVARCHAR(32)stringSelectFormally Verified
11Proof Generation DatedateDATEstring, format: dateDate2026-10-01

Select Options

Verification Method

Foundry Invariant Fuzzing | Halmos Symbolic Execution | Certora Rule Prover | SMT Solver

Symbolic Execution Engine

Certora Prover | Halmos | Z3 SMT | None (Fuzzing Only)

Counterexample Discovered

Yes | No

Mathematical Theorem Proved

Yes | No

Formal Verification Status

Formally Verified | Violations Found | Proof In Progress

Relations

  • Audit Reference -> links to the formal review documentation or test repository.
  • Target Architecture -> links to the deployed contract or autonomous agent runtime component.
Show full SKILL.md (205 more words)Show less

Examples

Prompt

How do I configure and track Smart Contract Formal Verification for our production environment?

Recommended Next Step

Generate the unified field schema, SQL DDL migration, and JSON validation schema to register into your system catalog.

Workflow: Define criteria -> Run automated verification -> Record baseline -> Monitor invariants.

Best Practices

  • Enforce strict typing on numerical bounds and currency amounts; avoid unstructured free-text fields for critical states.
  • Re-run validation test suites on every state-altering commit or parameter change.
  • Keep example data synthetic and isolated from production cryptographic keys or private endpoints.

Limitations

  • Provides architectural specifications, data models, and verification schemas; does not execute direct transaction signing without authorized external tooling.
  • Requires network connectivity and valid RPC credentials when querying on-chain states.

Security & Safety Notes

  • All parameters declare risk: safe. No unauthorized state modification or privileged credential access is performed.
  • Use synthetic dummy keys and mock addresses in test suites and local verification scripts.

Common Pitfalls

  • Problem: Mismatched decimal precision between contract runtime and database register. Solution: Always verify decimals using the explicit field mapping in this reference.
  • Problem: Missing authorization checks prior to state update. Solution: Cross-validate against the Security Audit register before deployment.
  • @soroban-contract-audit - provides the security checklist and vulnerability categorization.
  • @web3-rate-limiting-circuit-breaker - provides operational guardrails and threshold breakers.
  • @cross-chain-relayer-audit - covers message hashes, nonces and quorum proofs.

Reusable Prompt

I want to establish a verified Smart Contract Formal Verification register for our production protocol.
Guide me through the required field parameters and output the corresponding SQL DDL and JSON Schema.

© sickn33, MIT. 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 skills/smart-contract-formal-verification of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit b84d35a

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Smart Contract Formal Verification 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 Formal Verification compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Smart Contract Formal Verification this skillsickn33/agentic-awesome-skills47k1 repos~1.4kAutomated safety check: PassMIT
Stellar iOS Mac SDKSoneso/stellar-ios-mac-sdk132—~4.3kAutomated safety check: PassApache-2.0
Stellar DevVelaPayments/vela-payments131—~1.8kAutomated safety check: PassMIT
Fizz Convertpashov/skills1.2k2 repos~3.7kAutomated safety check: PassMIT
Smart Contract Auditgreatpie/smart-contract-audit-skill101—~1.1kAutomated safety check: PassNone
Solidity AuditorGabson0x/bountyforge442—~3.7kAutomated safety check: PassNone

Similar skills

  • Stellar iOS Mac SDK

    Soneso/stellar-ios-mac-sdk

    Guides Stellar blockchain development in Swift using stellar-ios-mac-sdk.

    132 GitHub stars~4.3k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Stellar Dev

    VelaPayments/vela-payments

    End-to-end Stellar development playbook. An agent skill from VelaPayments/vela-payments.

    131 GitHub stars~1.8k tokensUpdated 4 days ago
    Backend & APIsAuto-check passed
  • 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
  • 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
  • Solidity Auditor

    Gabson0x/bountyforge

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

    442 GitHub stars~3.7k tokensUpdated 24 days ago
    Backend & APIsAuto-check passed
  • Audit

    austintgriffith/ethskills

    Deep EVM smart contract security audit system. An agent skill from austintgriffith/ethskills.

    295 GitHub stars~829 tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,497 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Works with

Categories

Questions about Smart Contract Formal Verification

What does Smart Contract Formal Verification do?

Foundry and Soroban formal invariant verification register: state transition rules, boundary invariant properties, and symbolic execution checks. Smart Contract Formal Verification is an agent skill from sickn33/agentic-awesome-skills. Foundry and Soroban formal invariant verification register: state transition rules, boundary invariant properties, and symbolic execution checks.

When should I use Smart Contract Formal Verification?

Smart Contract Formal Verification fits situations like: tasks that involve Smart contracts; tasks that involve Smart contract auditing.

How do I install Smart Contract Formal Verification in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill smart-contract-formal-verification -a claude-code`. Or copy the skill folder (skills/smart-contract-formal-verification in sickn33/agentic-awesome-skills) into .claude/skills/smart-contract-formal-verification in your project. Claude Code loads it when a task matches its description.

How do I install Smart Contract Formal Verification in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill smart-contract-formal-verification -a codex`. Or copy the skill folder (skills/smart-contract-formal-verification in sickn33/agentic-awesome-skills) into .agents/skills/smart-contract-formal-verification in your project. Codex loads it when a task matches its description.

Can I use Smart Contract Formal Verification 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 sickn33/agentic-awesome-skills --skill smart-contract-formal-verification -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-formal-verification, .gemini/skills/smart-contract-formal-verification, .github/skills/smart-contract-formal-verification and .opencode/skills/smart-contract-formal-verification in your project.

What does Smart Contract Formal Verification need to run?

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

Does Smart Contract Formal Verification 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 Formal Verification 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 Formal Verification use?

Smart Contract Formal Verification is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Smart Contract Formal Verification use?

About 1.4k tokens (SKILL.md is roughly 5.6k 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 Formal Verification?

Skills that share tags, products or a category with Smart Contract Formal Verification: Stellar iOS Mac SDK (Soneso/stellar-ios-mac-sdk, 132 stars), Stellar Dev (VelaPayments/vela-payments, 131 stars), Fizz Convert (pashov/skills, 1.2k stars) and Smart Contract Audit (greatpie/smart-contract-audit-skill, 101 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Smart Contract Formal Verification?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.