What problem does it solve? AI agents frequently produce incorrect RedStone integrations: they treat the Pull model like Chainlink push feeds, forget to wrap frontend transactions with signed calldata, use wrong decimal assumptions, or misconfigure signer thresholds, causing reverted transactions and broken oracle reads. ## Core Features & Use Cases - Pull Model Integration: Implement RedstoneConsumerNumericBase contracts that extract signed price data from transaction calldata, with frontend wrapping via WrapperBuilder from @redstone-finance/evm-connector. - Push Model & RedStone X: Read Chainlink-compatible AggregatorV3Interface push feeds with staleness validation, and build frontrunning-protected two-phase execution flows with keeper bots. - Custom Data Feeds: Whitelist authorized signers via getAuthorisedSignerIndex, override timestamp validation, and consume proprietary data services. - Use Case: Build a lending vault that prices collateral on-demand using RedStone Pull, with a Foundry test harness mocking oracle reads and a TypeScript frontend attaching signed price packages to every transaction. ## Quick Start Use the redstone skill to write a Solidity contract that reads the ETH/USD price via the RedStone Pull model and show me the frontend code to wrap the transaction.