blockchain-development

Convert blockchain requirements into contract specs, tests, and verification artifacts.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/Blaze-sports-Intel/uber-engineer --skill blockchain-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: blockchain-development
Source: https://github.com/Blaze-sports-Intel/uber-engineer/tree/main/plugins/uber-engineer/skills/blockchain-development
Command: npx skills add https://github.com/Blaze-sports-Intel/uber-engineer --skill blockchain-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Blockchain development demands security, correctness, and user-safe transaction UX, but teams often ship contracts, tests, and deployments without strong verification and clear “done” criteria.

Core Features & Use Cases

  • Smart contract engineering with explicit safety: Produce contract specs covering state, events, access roles, and upgrade paths, alongside deterministic fork-based testing to catch real-world integration issues.
  • Security review that’s actionable: Run static analysis and triage findings so high-severity issues are resolved before mainnet action.
  • Wallet UX and integration-ready indexing: Design readable wallet signing flows with simulation previews and build indexer schemas mapped to contract events for reliable off-chain querying.

Quick Start

Ask the assistant to review the user’s smart contract plan, then generate the contract spec, fork-based tests with coverage targets, and the static analysis + deployment checklist evidence needed to declare the work done.

Frequently Asked Questions about blockchain-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify smart contract security before mainnet deployment?▼

Smart contract security verification requires static analysis to triage findings, deterministic fork-based testing for mainnet alignment, and multisig sign-off to ensure zero unresolved high-severity issues before release.

What is fork testing and how does it validate Solidity contracts?▼

Fork testing validates Solidity contracts by pinning mainnet assumptions and running deterministic tests against real-world integration scenarios, catching state and event issues before deployment to ensure contract correctness.

How do I design wallet UX for readable transaction signing flows?▼

Wallet UX design creates readable signing flows with simulation previews, ensuring users see clear transaction evidence and safe interaction paths before approving on-chain contract actions.

Does blockchain development support both EVM and Solana workflows?▼

Blockchain development supports both EVM and Solana workflows, applying Solidity and Anchor frameworks to generate contract specs, tests, and deployment-ready verification artifacts across both ecosystems.

How do I map event indexing schemas to smart contract events?▼

Event indexing maps to smart contract events by building indexer schemas that capture emitted contract events, enabling reliable off-chain querying and integration with RPC data for application backends.

What coverage percentage is required to declare smart contract verification done?▼

Smart contract verification requires at least 95% test coverage, zero unresolved high static analysis findings, fork-test alignment to mainnet, and user-readable wallet simulation evidence to satisfy done criteria.