Question
Closed · Answered

Once a monthly-report script is checked, can future runs just use a new input file?

Leonard Li

I'd like Buda to handle a monthly report: agree on the calculations and check the script on the first run, then supply a new source file each month.

I'd want later runs to reuse that script rather than rewrite the calculations. Could I keep it in Drive and use a Skill to check column names, pass the file path, and export the results? If the source sheet gains a column, I'd want the difference flagged rather than have the reporting rules changed silently.

Report
Kelly
Team

Yes. Treat month 1 as locking the script, and later months as new input + same script.

*Local demo / Diagram · First-month script stays; later months pass a new file*

Shape that stays maintainable

  1. First run — agree on calculations, save the checked script in Drive, and note the required columns.
  2. Skill (or saved prompt) — each month: check column names → pass the new file path → run the same script → export results.
  3. Schema guard — if the source gains/renames a column, flag the difference and stop for your decision; do not silently change reporting rules.

Brief for later months

Use the checked script at Drive/…/monthly_report.py (or your path). Input: this month’s file. Verify columns match the expected list; if anything differs, list the diff and wait. Do not rewrite the calculations.

How to verify

  • Month 2+ reuses the same script file (check the path in the session).
  • A deliberately added extra column produces a clear diff prompt, not a quiet new metric.
  • Output numbers match the rules you signed off in month 1.

Boundaries

  • “Just make the report work” can tempt the agent to rewrite logic — say reuse script, don’t rewrite.
  • Keep the expected column list next to the script so the check is explicit.
Report

Your reply

Sign in to join the discussion. Reading is always open; you only need an account to post.

Sign in