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
- ty now reads Pydantic config keywords and field metadata — charliermarsh · 2026-07-22
- Pensar Launches AI Security Agent to Autonomously Discover and Patch 0-Days — andriy_mulyar · 2026-07-22
- ty adds first-class Pydantic support, including strict and lax field handling — charliermarsh · 2026-07-22
- Google launches Gemini 3.5 Flash Cyber for CodeMender, with limited access for governments — GoogleAI · 2026-07-22
- Cursor doubles usage limits across all plans for Grok, Composer and new models — XFreeze · 2026-07-22
- Video-based proof of work is emerging as a feedback layer for coding agents — Vjeux · 2026-07-22