ritual-dapp-skills

Quick diagnostic lookup for Ritual dApp debugging.

Deterministic, RPC-only debugging flow for scheduled and scheduled-async transactions.

End-to-end Ritual Chain dApp builder. Use this agent when building complete applications on Ritual Chain, from idea through implementation. <example> Context: User wants to build a dApp on Ritual user: "Help me build a verifiable AI oracle on Ritual Chain" assistant: "I'll use the ritual-dapp-builder agent to guide you through building this — starting with feature selection, then contracts, frontend, and testing." <commentary> User wants to build a complete dApp. The agent orchestrates feature selection, architecture, smart contracts, frontend, and testing. </commentary> </example> <example> Context: User describes a multi-feature dApp user: "I want an app that streams LLM responses and stores encrypted results" assistant: "I'll launch the ritual-dapp-builder agent to design and implement this streaming + privacy dApp." <commentary> Multi-feature dApp. The agent selects the right skills (streaming LLM, private outputs) and builds end-to-end. </commentary> </example>

Debugs Ritual Chain dApp issues: stuck transactions, missing callbacks, empty results, balance errors, encoding mismatches. Activates after builds, on detected issues, or on-demand. <example> user: "My HTTP call transaction is stuck in pending for 20 minutes" assistant: "Diagnosing: checking executor availability, TTL, and wallet balance via chain queries." </example> <example> user: "The job shows as settled but my contract never received the result" assistant: "Checking delivery selector, callback gas limit, and contract handler." </example> <example> user: "I'm getting an empty bytes response from my LLM precompile call" assistant: "Checking ABI encoding, model configuration, and executor capability." </example>

Backend services for Ritual dApps. Use when building event indexers, APIs, job monitors, or webhook services for Ritual applications.

Block-time estimation and block-to-time conversion guidance for Ritual dApps. Use when setting TTL, lock durations, scheduler frequency, or polling windows.

Ritual chain precompile addresses, system contracts, ABI encoding, and callback security. Use when writing Solidity contracts that call Ritual precompiles, handle async callbacks, or interact with the Scheduler and RitualWallet.

Data Availability (storage) patterns for Ritual dApps. Use when any precompile stores or retrieves external data — multimodal outputs, conversation history, agent state, FHE ciphertexts, or artifact files.

Deployment and chain configuration for Ritual dApps. Use when deploying contracts, configuring chain connection, or setting up development environment.