← Back to library

Assemble the Friday report from your source files

Suraj Khaitan, an architect writing on DEV Community, handed Claude Cowork a day of the work he dislikes. For his weekly report, he handed over his report layout and the input files; Cowork combined them and completed the real document rather than a rough draft, needing only light edits. He notes scheduled tasks could run it every Friday.

  • OutcomeHave the recurring Friday report assembled from your source files into the real template, needing only a light edit.
  • SetupMinutes
  • LevelStarter
  • CreditSuraj Khaitan
View original
Works with
Claude Cowork

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • You build the same report every week
  • Numbers come from two or three files or dashboards
  • The template format matters to readers

Not for: Reports where every number must be audited before anyone sees it; Sources the agent cannot reach

What do you need, and what do you get?

You need

  • The report template
  • Source files or exports
  • Notes on which number goes where

You get

  • A filled report in the original format
  • A list of anything it could not find

How does it work, step by step?

  1. Give the real templateUse the actual file so the output matches what readers expect.
  2. Map sources to sectionsSay which file feeds which part, at least the first time.
  3. Approve the planReview the steps it proposes before it starts.
  4. Edit lightly and send yourselfRead the draft, fix wording and confirm numbers.
  5. Schedule once it is rightSet it to run weekly after a couple of clean runs.

The prompt

Our own prompt, inspired by Suraj Khaitan and written to work in Claude Cowork. Values in lime are placeholders.

Prompt0 variables
Fill this week's report using the template [file]. Sources: [file A] for [section], [file B] for [section], [file C] for [section]. Keep the template's formatting. Next to each number, note the source file and its date in a comment. If something is missing or older than seven days, leave a placeholder and list it at the top. Do not send the report; save it as [name with date].

Inspired by Suraj Khaitan: Claude Cowork Review: I Handed It a Day of My Busywork. Here's What Came Back.. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Usage limits drain faster than plain chat; heavy users may need a bigger plan.
  • If a source file is stale, the report will be too; date-check inputs.

Our take

Recurring reports are among the best delegation targets because they combine a fixed format, known sources and little creativity, and Suraj Khaitan's test confirms it. The detail that matters is that the agent filled the actual template, not a loose summary, so the output was usable after light editing instead of needing reformatting. Before scheduling it, make the inputs trustworthy. Write a short mapping of which file feeds which section, so the agent does not guess when names change, and ask it to show the date of each source next to every number. A stale export is the most common way automated reports go wrong, and dated figures make that obvious at a glance. Keep the first few runs as drafts sent to yourself, compare them with the report you would have built manually, and only then switch on the Friday schedule. If the report goes to leadership, keep the final send manual; a minute of reading catches errors that would otherwise travel up the organization with your name attached.

Where the time goes back: The weekly assembly chore disappears, leaving a quick read-through.

FAQ

Did it produce the real document?
Yes, the author says it filled the structured template, not a Markdown approximation.
How much editing was needed?
Light editing rather than assembly, in his account.

Source and credit

Inspired by Suraj Khaitan. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Claude Cowork Review: I Handed It a Day of My Busywork. Here's What Came Back.
Creator
Suraj Khaitan
Published on
DEV Community (dev.to)
Original date
Jun 20, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Claude Cowork
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminPrompt✓ AI dry run

Aim the agent at a janky internal app after it maps the UI

Have the agent study a janky internal UI out loud, complete one end-to-end task with a recording, and stop for login walls instead of guessing credentials.

Credit: Carnage (@0xCarnagee)

Under an hour
Operations & AdminPrompt✓ AI dry run

Audit how you manage your agent team, not only the agents

Have your chief-of-staff agent review the last 30 days of how you delegated, clarified, interrupted, corrected, assigned, approved and followed up across your agent team, score eight management areas with evidence, list your three biggest weaknesses, and draft a seven-day improvement plan, without changing any bot, routine or instructions until you approve.

Credit: Michael Fenech (@Michael_Fenech_)

Under an hour
Operations & AdminPrompt✓ AI dry run

Audit how your agents pick tools before buying more usage

Have your lead agent review the recurring jobs it can see, note which apps, scripts, browser sessions or full computer control each one relies on, flag jobs that take a heavier route than needed or rely on remembered facts, check permissions and fallbacks, and then propose three side-by-side experiments before anything is changed.

Credit: Michael Fenech (@Michael_Fenech_)

Under an hour
Operations & AdminPrompt✓ AI dry run

Check your agent can undo a bulk change before it runs

Before an agent edits hundreds of files, rows or records, get a list of risky jobs, how each would be restored, a tested undo on a copy, and a change log, with nothing live touched until you approve.

Credit: Michael Fenech (@Michael_Fenech_)

Under an hour
Operations & AdminSkill✓ AI dry run

Diagnose a down machine from its history, sensors and manual

Use the breakdown-diagnosis skill from Anthropic's Claude for Manufacturing plugin to put any safety hazard first, read the sensor trace before the stoppage, search the asset's work orders and technician notes, check the manufacturer's troubleshooting guide, and get ranked likely causes with the quickest test to tell them apart plus a draft preventive maintenance change.

Credit: anthropics

An afternoon+