organvm-iv-taxis/blockchain-integration-builder
distributions/codex/skills/blockchain-integration-builder/SKILL.md
Design and implement blockchain integrations across chains and frameworks with emphasis on patterns over specific technologies. Use when building Web3 applications, smart contract systems, token mechanics, decentralized identity, or blockchain-verified data. Triggers on blockchain architecture, smart contract design, Web3 integration, token systems, or decentralized application development. Framework-agnostic—applies to Ethereum, Solana, or emerging chains.
$ install --global
skillsauthnpx skillsauth add organvm-iv-taxis/a-i--skills blockchain-integration-builderInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 19, 2026, 2:08 AM18.6s3 files scanned
SKILL.md
- name:
- blockchain-integration-builder
- description:
- Design and implement blockchain integrations across chains and frameworks with emphasis on patterns over specific technologies. Use when building Web3 applications, smart contract systems, token mechanics, decentralized identity, or blockchain-verified data. Triggers on blockchain architecture, smart contract design, Web3 integration, token systems, or decentralized application development. Framework-agnostic—applies to Ethereum, Solana, or emerging chains.
- license:
- MIT
- governance_phases:
- [build]
- organ_affinity:
- [organ-iii]
- triggers:
- [user-asks-about-blockchain, user-asks-about-web3, user-asks-about-smart-contracts]
Blockchain Integration Builder
Design blockchain systems using universal patterns applicable across chains.
Core Abstractions
Blockchain-agnostic thinking: focus on what you're trying to achieve, then select chain/framework.
Fundamental Primitives
| Primitive | What It Is | Chain Examples | |-----------|------------|----------------| | Account | Identity with balance | EOA (Eth), Wallet (Solana), Account (Near) | | Transaction | State change request | Signed message + gas | | Block | Batch of transactions | Time-ordered, immutable | | Contract | On-chain program | Solidity, Rust, Move | | Event/Log | Indexed side-effect | Emitted by contracts, queryable | | State | Persistent data | Mappings, storage slots |
Selection Criteria
| Need | Consider | Why | |------|----------|-----| | Programmability | Ethereum, Arbitrum, Base | Mature tooling, EVM ecosystem | | Speed/Cost | Solana, Sui, Aptos | High throughput, low fees | | Privacy | Aztec, Zcash | Zero-knowledge proofs | | Interoperability | Cosmos, Polkadot | Cross-chain communication | | Simplicity | Bitcoin, Litecoin | Limited scripting, proven security |
Pattern Library
Identity Patterns
Wallet-Based Identity
User → Wallet → Sign Message → Verify Signature → Authenticated
- No passwords stored
- User controls identity
- Works across applications
Soul-Bound Tokens (SBTs)
Issuer → Mint SBT → User Wallet (non-transferable)
- Credentials, achievements, reputation
- Cannot be sold or transferred
- Revocable by issuer (optionally)
Decentralized Identifiers (DIDs)
did:method:identifier → Resolve → DID Document → Public Keys, Services
- Self-sovereign identity
- Cross-chain portable
- W3C standard
Token Patterns
Fungible Tokens (ERC-20 pattern)
// Universal interface
balanceOf(address) → uint256
transfer(to, amount) → bool
approve(spender, amount) → bool
transferFrom(from, to, amount) → bool
Non-Fungible Tokens (ERC-721 pattern)
// Universal interface
ownerOf(tokenId) → address
transferFrom(from, to, tokenId)
tokenURI(tokenId) → string (metadata)
Semi-Fungible (ERC-1155 pattern)
// Batch operations, mixed fungible/non-fungible
balanceOf(account, id) → uint256
balanceOfBatch(accounts[], ids[]) → uint256[]
safeTransferFrom(from, to, id, amount, data)
Governance Patterns
Token Voting
Proposal → Snapshot Balances → Vote Period → Tally → Execute (if passed)
Quadratic Voting
Cost of N votes = N² tokens
Reduces plutocratic dominance
Optimistic Governance
Proposal → Challenge Period → Execute if unchallenged
Economic Patterns
Bonding Curves
Price = f(Supply)
Buy: Price increases with supply
Sell: Price decreases with supply
Creates automatic market making
Staking/Slashing
Stake tokens → Perform duties → Earn rewards
Misbehave → Lose stake (slashing)
Streaming Payments
Deposit → Linear unlock over time → Recipient claims
Architecture Patterns
On-Chain vs Off-Chain
| Aspect | On-Chain | Off-Chain | |--------|----------|-----------| | Cost | High (gas fees) | Low/free | | Speed | Slow (block time) | Fast | | Trust | Trustless | Requires trust | | Privacy | Public | Can be private | | Storage | Expensive | Cheap |
Hybrid approach:
Off-chain: Computation, storage, user experience
On-chain: Verification, settlement, ownership
Bridge: Oracles, merkle proofs, signatures
Indexing Pattern
Blockchain data is hard to query directly. Use indexers:
Blockchain → Events → Indexer → Database → API → Frontend
Tools: The Graph, Goldsky, custom indexers
Oracle Pattern
Bring external data on-chain:
External Data → Oracle Network → Consensus → On-chain Value
Use cases: Price feeds, random numbers, API data
Security Principles
Smart Contract Security
- Check-Effects-Interactions: Update state before external calls
- Reentrancy Guards: Prevent recursive calls
- Access Control: Verify caller permissions
- Input Validation: Never trust user input
- Upgrade Patterns: Plan for bug fixes (proxies, migrations)
Common Vulnerabilities
| Vulnerability | Description | Prevention | |---------------|-------------|------------| | Reentrancy | Recursive calls drain funds | Checks-effects-interactions | | Integer overflow | Math wraps around | SafeMath or Solidity 0.8+ | | Front-running | Miners/validators see pending txs | Commit-reveal, flashbots | | Oracle manipulation | Fake price data | Multiple oracles, TWAP | | Access control | Missing permission checks | Role-based access |
Integration Workflow
1. Define Requirements
- What needs to be trustless?
- What can stay off-chain?
- Who are the actors?
- What are the assets?
2. Select Chain
Based on: throughput needs, cost constraints, ecosystem fit, team expertise
3. Design Contracts
- Keep contracts simple and focused
- Separate concerns into multiple contracts
- Plan upgrade path
4. Build Indexing
- Determine query patterns
- Index relevant events
- Build API layer
5. Create Frontend
- Wallet connection
- Transaction signing
- State display
- Error handling
6. Test & Audit
- Unit tests
- Integration tests
- Formal verification (for critical contracts)
- Third-party audit
References
references/contract-patterns.md- Common smart contract patternsreferences/chain-comparison.md- Chain-specific considerations
Related Skills
organvm-iv-taxis/shell-history-hygiene
development
VerifiedTrustedCommunity
Dry-run audit + targeted cleanup for shell command history. Currently wraps atuin (stats today, prune, dedup with dated preview artifacts); extensible to zsh/bash/mcfly backends. Always previews before applying — apply commands are echoed for the human to run, never auto-executed. Triggers on "/shell-history-hygiene", "audit atuin", "audit shell history", "clean shell history", "atuin prune", "atuin dedup", "shell history hygiene", "history cleanup". Replaces ad-hoc one-liners (e.g. `... | tee cmd > file.txt` which wrote two files, swallowed dedup output, and left a junk `cmd` file).
12SKILL.mdUpdated Jul 20, 2026
organvm-iv-taxis/setup-cowork
tools
VerifiedTrustedCommunity
Guided Cowork setup — install role-matched plugins, connect your tools, try a skill.
12SKILL.mdUpdated Jul 20, 2026
organvm-iv-taxis/session-lifecycle-patterns
development
VerifiedTrustedCommunity
Manage AI agent session lifecycles with structured phases (FRAME, SHAPE, BUILD, PROVE), context preservation across sessions, handoff protocols, and session metadata tracking. Triggers on session management, agent lifecycle, or multi-session workflow requests.
12SKILL.mdUpdated Jul 20, 2026
organvm-iv-taxis/session-governance-audit
tools
VerifiedTrustedCommunity
Parse a session transcript into a structured Session Governance Index — an annotated bibliography of every file modified and commit made, internal-energy accounting (tool uses, estimated tokens), shipped-vs-tasked atom tally, and classification of missing items as Gaps or Vacuums. Triggers on "visibility-schema-substrate-sweep", "session cascade audit", "session governance audit", or any request to summarize what a session actually produced versus what it was asked to produce.
12SKILL.mdUpdated Jul 20, 2026