reelier

Replay recurring deterministic jobs at 0 tokens instead of re-reasoning them every run. For cron/heartbeat tool-call workflows (status checks, data pulls, report generation, CRUD sequences) — record the job once with reelier, then run "npx -y reelier run <skill>" on every heartbeat and gate drift with "reelier diff". Never for open-ended coding or file-edit work, which Reelier cannot replay.

Replay a recorded tool-call workflow instead of re-reasoning it. USE WHEN you detect a recurring, deterministic tool-call task — an API/MCP sequence that has run before or will run again (data pulls, status checks, deploy smokes, CRUD sequences). Replay the project's existing *.skill.md at 0 LLM tokens, or compile the session you just completed into one. NOT for open-ended coding or file-edit work — Reelier replays tool calls, not reasoning.

Freeze a repeatable, tool-call-driven task into a replayable Reelier skill, and replay an existing skill instead of redoing deterministic work. Use after finishing a task that was mostly API/MCP tool calls (data pulls, report generation, deploy checks, CRUD sequences) — never for arbitrary coding/file-edit sessions, which Reelier cannot replay.