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
- Dev builds interactive 3D product experience with GPT-6 Astra + Hyper3D Rodin — nikola_mr64990 · 2026-09-11
- Codex tip: use Sol with Astra and Luna sub-agents to save usage — pvncher · 2026-09-11
- agents-best-practices: a provider-neutral Agent Skill for designing and auditing agentic harnesses — tom_doerr · 2026-09-11
- Cognition's SWE-2 uses a KKT duality argument in RL to shift the effort Pareto curve — YouJiacheng · 2026-09-11
- First-ever Three.js Conference lands in Paris, with a panel on AI-shortened design workflows — OdinLovis · 2026-09-11
- Data engineering, not agent frameworks, is the real bottleneck for enterprise AI agents — dhruv2038 · 2026-09-11