web3-security-tooling
Guide for security tooling (analyzers, fuzzers, decompilers, compilers) and consistent placement in README.md.
Skills matching the name, description or GitHub author.
Guide for security tooling (analyzers, fuzzers, decompilers, compilers) and consistent placement in README.md.
Guide for understanding and contributing to the awesome-web3-security curated resource list. Use this skill when adding resources, organizing categories, or maintaining README.md consistency (no duplicates).
Implement and debug wallet connection and authentication in this repo using thirdweb v5 and the SIWE-style flow in `app/hooks/useWalletAuth.ts` and `app/hooks/server_actions.ts`. Use for ConnectButton setup, ac...
Expert-level blockchain, Web3, smart contracts, DeFi, and cryptocurrency development
Master Web3 frontend development with wallet integration, viem/wagmi, and dApp UX
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi...
Full-stack Aptos dApp development combining Move contracts, TypeScript SDK, indexer queries, wallet integration, and modern frontend frameworks. Production-ready patterns for Web3 applications.
Expert guide for testing Drupal modules including PHPUnit setup, Kernel tests, Functional tests, crypto testing patterns, and coverage analysis. Use when creating tests for Drupal contrib modules, especially au...
Specialized development guidelines for the Zap Pilot frontend built with Next.js 15, React 19, Tailwind CSS v4, and TypeScript. Covers service-first architecture, component composition patterns, TanStack Query...
"Specialist in Wagmi v2, Viem, React integration. Expert in optimistic UI, state synchronization, and Web3 frontend patterns."
Handle MetaMask signature and transaction popups during Web3 DApp testing - approve signatures, send transactions, call contracts. Detects popup type and handles gas errors.
Set up MetaMask wallet extension for Web3 DApp testing - download extension, import wallet from private key. Run at test start if tests/config.yaml has web3.enabled=true.
Execute tests from persistent test cases. Reads ./tests/ directory, runs cleanup, wallet setup (if Web3), executes tests, and generates report.
Analyze ANY web project - detect if Web3 DApp, research dependencies via WebSearch, understand business functions from code AND UI screenshots, generate test requirements.
Connect wallet to Web3 DApp - navigate to DApp, click Connect Wallet, approve in MetaMask popup, verify connection. Can be used as a test case or as a precondition for other tests.
Next.js + Web3開発の知識。「ウォレット接続」「ethers」「wagmi」で使用。
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi...
Expert on building decentralized applications with Shelby Protocol storage on Aptos. Helps with dApp architecture, wallet integration (Petra), browser SDK usage, React/Vue integration, file uploads, content del...
Expert on Aptos blockchain, Move language, smart contracts, NFTs, DeFi, and Aptos development. Triggers on keywords aptos, move, blockchain, smart contract, nft, defi, web3, mainnet, testnet, devnet
Build DAO governance agents with SpoonOS. Use when monitoring proposals, automating voting, managing delegations, or analyzing governance patterns.
Ready-to-use agent application templates for common Web3 use cases. Use when building trading bots, NFT minters, DAO assistants, portfolio managers, or research agents with SpoonOS framework.
Omniscient APEX Ecosystem development skill. Triggers: apex code, omnihub development, tradeline build, aspiral feature, apex bug, fix apex, apex architecture, omnidash component, triforce guardian, man mode, a...
Comprehensive testing approaches covering unit, integration, and end-to-end testing with domain-specific patterns for Web2, Web3, and infrastructure components.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.