concepts

Correct Ethereum contract execution, timing, and operator misconceptions.

1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/collat-labs/collat --skill concepts-collat-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: concepts
Source: https://github.com/collat-labs/collat/tree/main/.agents/skills/ethskills/concepts
Command: npx skills add https://github.com/collat-labs/collat --skill concepts-collat-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents common onchain design misunderstandings by teaching the mental models behind how Ethereum-style systems actually work, so you can design systems that won’t fail due to incorrect assumptions about automation, operators, state transitions, and incentives.

Core Features & Use Cases

  • What Ethereum gets wrong (and what to fix): clarifies misconceptions like “smart contracts run automatically,” “just add a timer,” and “the team will handle it.”
  • Incentive-first state machine design: explains that contracts do nothing between calls (“someone pokes it”), and that each transition must have a credible caller and incentive.
  • Practical guidance for hard primitives: covers why randomness is hard on deterministic systems and when to use commit-reveal versus VRF.
  • Teaching your human effectively: provides context-based explanations for common building blocks (DEXs/AMMs, lending, oracles, stablecoins, multisigs).
  • Use cases: onboarding new builders, validating a system design before implementation, and correcting design decisions early (before they become dead code).

Quick Start

Use the concepts skill to explain how “nothing is automatic” and incentive-driven state transitions determine which onchain actions can actually happen, then ask it to apply those principles to your system design for one concrete workflow.

Frequently Asked Questions about concepts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why do smart contracts not run automatically on Ethereum and how do state transitions work?

Smart contracts on Ethereum do not run automatically because they are inactive between calls and require an external caller to trigger state transitions. Incentive-driven design ensures a credible caller pokes the contract to execute logic.

How do I generate randomness in a deterministic smart contract system?

Generating randomness in a deterministic smart contract system requires commit-reveal schemes or Verifiable Random Functions (VRF) to prevent operator manipulation and ensure unpredictable, secure onchain outputs.

What is the best way to design incentives for permissionless onchain calling patterns?

Designing incentives for permissionless calling patterns requires mapping each state machine transition to a credible caller with sufficient motivation to trigger the action, ensuring the contract logic executes properly.

How do I validate my Ethereum smart contract system design before implementation?

Validating smart contract system design involves checking assumptions about automation, timing, and operator behavior using correct mental models to prevent incentive insufficiency and dead code before deployment.

Can I use a timer or external cron-like automation to trigger smart contract execution?

You cannot use external cron-like automation to trigger smart contract execution because Ethereum contracts are inactive between calls and rely entirely on permissionless, incentive-driven external callers to transition state.