pour

Resolve and execute TOML-defined formulas across local, overlay, and public sources.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/naramore/dotai --skill pour-naramore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pour
Source: https://github.com/naramore/dotai/tree/main/claude/skills/pour
Command: npx skills add https://github.com/naramore/dotai --skill pour-naramore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages the end-to-end execution of a TOML-defined formula by resolving the formula path, batching required variables, sequencing steps in a DAG, and handling post/dispatch semantics with guarded, repeatable runs.

Core Features & Use Cases

  • Resolve and validate TOML formulas across local, overlay, and public sources.
  • Batch and substitute variables before dispatch, with deterministic, idempotent execution.
  • Enforce safe state mutations, append-only journals, and explicit second invocations for posting or dispatch.

Quick Start

Invoke pour on a named formula to execute its TOML-defined steps end-to-end.

Frequently Asked Questions about pour

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

FAQPage Schema
How do I execute a TOML-defined formula end-to-end with deterministic variable batching?

You execute a TOML-defined formula by invoking it by name, which resolves the path, validates the schema, batches variables, and runs the DAG of steps in parallel where dependencies permit. This ensures deterministic, idempotent execution.

How does DAG step sequencing work when dispatching TOML formulas?

DAG step sequencing builds a dependency graph of formula steps and executes bands of steps in parallel where dependencies allow. It enforces single-writer state mutations and append-only journaling to maintain strict execution guards and deterministic outputs.

Can I resolve TOML formulas from both local project files and public profile sources?

Yes, you can resolve TOML formulas across project-local, private overlay, and public profile sources. The resolution process locates the correct formula path and validates the TOML schema before staging required variables for dispatch and execution.

What's the best way to handle post and dispatch semantics for repeatable formula execution?

The best way to handle post and dispatch semantics is using optional flags (--post and --dispatch) with explicit second invocations. This enforces explicit exit-criteria verification and append-only journaling for safe, repeatable formula runs.

Why does formula execution require strict single-writer state mutations and append-only journals?

Formula execution requires strict single-writer state mutations and append-only journals to enforce deterministic inputs and safe state changes. These guards prevent race conditions during parallel DAG step execution and ensure repeatable, idempotent formula runs.