Results for “explain”

Provides current Ethereum gas prices and real transaction costs, comparing mainnet vs L2 and explaining the 95%+ drop in gas fees.

Explains the advantages of building on Ethereum, including ERC-8004 identity, x402 payments, composability, and permissionless deployment, while correcting common misconceptions about gas costs and network status.

Query the bundled research knowledge graph for methodology guidance. Routes questions through a 3-tier knowledge base — WHY (research claims), HOW (guidance docs), WHAT IT LOOKS LIKE (domain examples) — plus structured reference documents. Returns research-backed answers grounded in specific claims with practical application to the user's system. Triggers on "/ask", "/ask [question]", "why does my system...", "how should I...".

Interrogates a plan against real third-party documentation, extracting hard constraints and asking doc-cited questions before producing a constraints appendix.

Explains Solana's architecture and protocol internals, covering the SVM execution engine, account model, consensus, transactions, validator economics, data layer, development tooling, and token extensions using Helius blog posts, SIMDs, and Agave/Firedancer source code.

Explains Solana's architecture and protocol internals, covering the SVM execution engine, account model, consensus, transactions, validator economics, data layer, development tooling, and token extensions using Helius blog posts, SIMDs, and Agave/Firedancer source code.

Use this skill instead of WebSearch for ANY question requiring web research. Trigger on queries like "what is X", "explain X", "compare X and Y", "research X", or before content generation tasks. Provides systematic multi-angle research methodology instead of single superficial searches. Use this proactively when the user's question needs online information.

Chrome-dependent academic literature scouting and idea planning. Use when the user gives a research idea, topic, question, or draft direction and wants Codex to browse Google, Google Scholar, and academic sources through the Codex Chrome plugin, identify relevant papers, explain what can be borrowed from them, and write a planNN.md before collecting PDFs or BibTeX.

Build work collaboratively in reviewable pieces, handing each piece back for review before starting the next, so the person stays in the lead and steers while the work happens instead of reviewing a finished result. Use when someone says to pair with them on something, asks to collaborate rather than direct, wants to review as it goes, or wants to guide the work piece by piece — on code, on a design decision, or on writing. For a test-first build it runs tdd, for restructuring it runs refactor, for an interface contract it runs design-an-api, and for plan work it runs iterative-plan-review or plan-implementation, each collaboratively; invoke any of those directly instead to run it straight through without pausing. Does not pace someone through code that already exists and builds nothing — use code-walkthrough. Does not explain, summarize, or research something instead of producing it — use code-overview or research.