What problem does it solve? AI agents frequently produce incorrect RedStone integrations: they treat the Pull model like Chainlink push feeds, forget to wrap transactions with the EVM Connector SDK, mishandle bytes32 feed IDs, or misconfigure signer thresholds, causing reverts like CalldataMustHaveValidPayload and InsufficientNumberOfUniqueSigners. ## Core Features & Use Cases - Pull Model Integration: Build contracts inheriting RedstoneConsumerNumericBase that extract signed price data from transaction calldata, with frontend wrapping via WrapperBuilder from @redstone-finance/evm-connector. - Push Model & Chainlink Compatibility: Read RedStone push feeds through the standard AggregatorV3Interface with staleness, round, and decimal validation, including dual-oracle fallback patterns. - RedStone X Frontrunning Protection: Implement two-phase commit execution where users submit intents and keepers execute with post-intent price data, plus custom data feeds with whitelisted signers and custom timestamp validation. - Use Case: Build a lending vault that prices collateral on-demand via RedStone Pull, a limit order book protected from oracle frontrunning via RedStone X, or a custom data service for proprietary off-chain metrics. ## Quick Start Use the redstone skill to write a Solidity contract that reads ETH and BTC prices via the RedStone Pull model along with the frontend wrapping code.