Help us improve
Share bugs, ideas, or general feedback.
From uber-engineer
Smart contracts, wallet UX, indexers, security review, and on-chain integration. Use when the user mentions: blockchain, Ethereum, Solidity, Foundry, Hardhat, Rust smart contracts, Solana, Anchor, wallet, ERC-20, ERC-721, NFT, DeFi, EVM, subgraph, indexer, RPC, MEV, wagmi, viem, ethers.js. Pair with the discipline-router agent for cross-cutting work. Do NOT trigger for: general web3 frontend without contract code (use frontend-development); trading bots without on-chain integration.
npx claudepluginhub blaze-sports-intel/uber-engineer --plugin uber-engineerHow this skill is triggered — by the user, by Claude, or both
Slash command
/uber-engineer:blockchain-developmentThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Smart contracts, wallet UX, indexers, security review, and on-chain integration.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
Smart contracts, wallet UX, indexers, security review, and on-chain integration.
This skill is part of the uber-engineer plugin's discipline coverage. Pair with the
discipline-router agent when a request crosses disciplines, and the build-validator agent
before claiming any work is done.
Trigger words: blockchain, Ethereum, Solidity, Foundry, Hardhat, Rust smart contracts, Solana, Anchor, wallet, ERC-20, ERC-721, NFT, DeFi, EVM, subgraph, indexer, RPC, MEV, wagmi, viem, ethers.js.
Use when the user wants any of:
discipline-router agent before splitting work.references/official-sources.md. Use the Context7 MCP for live doc lookups instead of
relying on training-data memory for fast-moving APIs./blockchain contract-review src/Vault.sol/blockchain fork-test --block=latest/blockchain wallet-flow approve-spendreferences/official-sources.md — authoritative documentation URLs.references/workflow-playbook.md — detailed step-by-step playbook.references/anti-patterns.md — anti-pattern catalog with fixes.references/quality-rubric.md — pass/fail rubric for review.references/examples.md — concrete examples, before/after diffs.scripts/validate_skill.py — sanity-checks SKILL.md frontmatter and references.A real user, operator, or downstream system experiences the correct outcome of this work. Build success and deploy success do not equal done. The discipline-specific states below must all hold:
Verification actually happened — no claim of "verified" without evidence.