The agent's wallet for EVM chain transactions and raw signing. Use this skill when users want to create a wallet, transfer tokens, swap on DEXs, interact with smart contracts, or sign messages. Triggers on "wallet", "create wallet", "transfer ETH", "swap tokens", "send transaction", "check balance", "EVM wallet", "raw signer", "sign message".
Transaction signing UX patterns for Ethereum dApps: EIP-712 typed structured data, human-readable transaction summaries, transaction simulation/preview, multi-step signing progress, EIP-7702 batch signing, and Sign-In with Ethereum (SIWE/EIP-4361). Use this skill whenever building or reviewing ANY signature request, transaction confirmation UI, signing flow, SIWE implementation, transaction preview, or multi-step transaction progress — even if the user just mentions 'signing', 'signature', 'confirm transaction', 'SIWE', 'sign in with ethereum', or 'transaction preview'.
Safety and security UX patterns for Ethereum dApps: risk-differentiated warnings (info/caution/danger tiers), ENS name resolution, ERC-55 address checksum validation, spam token filtering, and safe max-send calculations. Use this skill whenever building or reviewing ANY address input, warning system, risk indicator, token filtering, ENS display, send-max feature, or phishing protection — even if the user just mentions 'safety', 'security', 'warnings', 'address validation', 'ENS', 'spam tokens', or 'send max'.
Token approval UX patterns for Ethereum dApps: exact-amount approvals, Permit2 gasless signatures, EIP-5792 batched approve+action, human-readable approval display, and in-app approval management/revocation. Use this skill whenever building or reviewing ANY ERC-20 token approval flow, permit signing, spending permission UI, allowance checking, or approval revocation feature — even if the user just mentions 'approve', 'allowance', 'permit', or 'spending permission'.
Converts static web or Next.js projects into ArcBlock blocklets using provided DID. Analyzes project structure, generates configuration files, and validates setup. Requires blocklet DID as parameter.
Guide for building privacy-preserving smart contracts using Inco Lightning on EVM (Solidity) and SVM (Solana/Rust)
Architect new Python-based blockchain projects using the Ape framework. Use when users want to start a new blockchain project and need guidance on proper project structure, architecture patterns, configuration, and foundational setup. Supports SDK development, plugin creation, bot development with Silverback, protocol development, and complex blockchain applications. Determines project type and guides users through establishing the correct architectural foundation.
Design and build a new smart contract protocol using Ape Framework. Use when users want to create a new set of smart contracts that work together as a protocol, including development, testing, scripting/deployment, and potentially other aspects such as distributing a Python SDK or enabling automation of the protocol (through Silverback). Guides users through the full lifecycle from design through deployment and beyond using Ape tooling.
Reliability-first Rust skill for libraries, CLIs, async services, app backends, and FFI wrappers. Use when Rust work needs strong boundary types, typed errors, async and cancellation safety, concurrency verification, compile-fail or property testing, unsafe containment, or operational release gates.
Reliability-first TypeScript skill for implementing, refactoring, or reviewing .ts code in shared libraries, services, browser code, and cross-layer contracts. Use when work needs strict tsconfig guardrails, schema-first parsing, unknown-at-boundary handling, discriminated unions, persistence/version safety, explicit async cancellation, or behavior-first testing.
Reliability-first backend TypeScript skill for APIs, workers, queues, CLIs, and long-running services. Use when writing Node, Bun, Deno, or worker code that needs request and env parsing, branded identifiers, explicit result errors, cancellation propagation, idempotent writes, persistence evolution, or contract and integration tests.
Reviews Solana/Anchor programs for development best practices. Use when writing, reviewing, improving or auditing Solana smart contracts. 31 vulnerability patterns with 4 real-world case studies.
Audits repository security — hardcoded secrets, dependency vulnerabilities, environment variable management, and authentication patterns. Use when the user asks to "check security", "find secrets", "audit dependencies", or "secure my repo". Don't use for code review, deployment, or monitoring.
Master smart contract security best practices, vulnerability prevention, and secure Solidity development patterns.
Deploy Your Project to production safely. Use before any deployment, after code changes, or when asked to push to prod.
Prove `deliver.eds.site` capability through end-to-end execution. Use when validating Edge Delivery Services skills before EDS work, checking aem-cli and GitHub auth availability, establishing baseline confidence, or surfacing Adobe EDS tooling blockers.
Specialized knowledge in web security, vulnerability assessment, and safe coding.
Message signing and verification — SIP-018 structured Clarity data signing (on-chain verifiable), Stacks plain-text message signing (SIWS-compatible), Bitcoin message signing (BIP-137 for legacy/wrapped-SegWit, BIP-322 for native SegWit bc1q and Taproot bc1p), BIP-340 Schnorr signing for Taproot multisig, and Nostr event signing using NIP-06 key derivation. All signing requires an unlocked wallet; hash and verify operations do not.
Use when starting any Solidity feature, contract, or type — before writing implementation code — to define specs, invariants, types, and formal proofs that drive the implementation
Comprehensive Solana smart contract security auditor. Covers 25+ attack vectors across Anchor, native Rust, and Pinocchio: sealevel attacks, arithmetic safety, CPI exploits, state machine issues, Token-2022 risks, and real-world case studies.
Build production-ready gRPC services in Go with mTLS, streaming, and observability. Use when designing Protobuf contracts with Buf or implementing secure service-to-service transport.
