Weekly deck requests often need a cron job and template, not an agent
No_Medicine3371 · reddit · 2026-07-21
A consultant argues that many “agent” requests are really deterministic workflows in disguise. In the case of a weekly campaign recap deck, the actual task was just three connector steps and one API call.
The setup
- Every Friday, the system pulls the same five metrics from the same dashboard.
- Those values are inserted into a fixed outline with a headline, week-over-week delta, and one line of context.
- A deck-generation API then returns a shareable link.
The lesson
- If the output structure never changes, there is no need for an agent to decide anything.
- A real agent is only worth it when inputs are messy or each run requires interpretation.
- The author used Gamma’s API for rendering, but notes the tradeoff: the format is not easy to hand-edit in PowerPoint later, and the credit cap only makes sense because the volume is low.
The broader point is that recurring deck work often needs a cron job plus templates, not autonomy.
More from coding & agent
- Developer Moves All Prompts to Skills: AI Coding Workflow v3 Explained — rseroter · 2026-10-26
- charlie Marsh: rewrites beat external deps in the AI era — mohamedmansour · 2026-10-26
- OpenAI and Twitch launch Codex hackathon with $25,000 in prizes — OpenAIDevs · 2026-10-26
- Filtering secrets on the write path: why agent memory deserves more suspicion at ingest than retrieval — Classic-Being-7960 · 2026-10-26
- INT21's AI agent swarm rewrote Drama 3's inference runtime in Rust within one hour, beating SGLang-Omni — bingxu_ · 2026-10-26
- After OpenCode key leak: 5 practical rules for keeping keys away from agents — jacobholm_dev · 2026-10-26