How we handle GDPR data-subject requests on a deadline
Legal
The reporting agent we run on Kortix — connected to our Postgres database and Slack. Every Monday it queries the metrics, writes the report with commentary on what moved, and posts it.

Every team has a weekly metrics report, and someone spends part of their Monday building it: running the same queries, dropping the numbers into a template, and writing a line or two about what changed. It's routine, it's on a schedule, and it's exactly the kind of thing that gets skipped the week it's most needed.
We run a reporting agent on Kortix that builds it. A Monday cron queries the metrics from our Postgres database, writes the weekly report with commentary on what moved and why, and posts it to Slack. Access to the database is read-only. This write-up covers how the setup works: the trigger, the session model, and the guardrails.
The weekly report is low-skill, high-consistency work: the same queries, the same layout, every week. Done by hand it eats an hour of someone's Monday, and the week things are busiest is the week it's most likely to slip — which is usually the week the numbers most needed a look.
The common fixes are incomplete. A static dashboard shows the numbers but doesn't say what moved or why, so someone still has to read it and write the summary. A scheduled SQL job can post the figures but not the commentary. The interpretation — what changed, whether it matters — is the part that takes a person, and it's the part that gets dropped.
On Kortix, a Monday cron triggers a reporting agent. Each run spawns an isolated session (a cloud sandbox) with scoped, read-only access to the Postgres database and permission to post to one Slack channel. The agent runs the metric queries, compares them against the prior weeks, writes commentary on what moved, and posts the report to Slack. It cannot write to the database.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the report skill and the weekly trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a weekly metrics report agent in this workspace.
Create the agent agents/weekly-report.md. Its job is to build the weekly metrics report from Postgres and post it to Slack. It may use the PostgreSQL connector, read-only.
Create the skill skills/weekly-metrics-report/SKILL.md with these rules:
Add a cron trigger weekly-metrics-report to kortix.yaml. It runs the weekly-report agent every Monday at 06:00 with the prompt "Load the weekly-metrics-report skill and post this week's metrics report to #metrics."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect your database with a role that can only select, and Slack for the report. Credentials are brokered server-side and never enter the agent's machine.
Queries the metrics tables, read-only.
Posts the weekly report with commentary on what moved.

Merge the change request, then start a session with the weekly-report agent and send this prompt. Check the numbers against your own dashboard before you let the schedule take over.
Build this week's metrics report.
The change request added this trigger to kortix.yaml. From now on the agent
runs every Monday at 06:00, each run in a new session on its own cloud computer.
To change the time, edit the cron line, or open Triggers in the workspace.
triggers:- slug: weekly-metrics-report name: Weekly metrics report on: cron: "0 0 6 * * 1" run: agent: weekly-report prompt: Load the weekly-metrics-report skill and post this week's metrics report to #metrics.The Postgres role can run SELECT and nothing else, and it reaches only the metrics tables. The report cannot change the data it reports on. The Slack post is the only output, and the team decides what to do about each move.
Each run ends with one message in #metrics. This is what a run looks like in the session:
Posted the report for 12 metrics. 2 moves are notable: signups rose 18% week over week, and trial conversion fell to 9.4%, below its 4-week average. 1 metric had no data for Sunday.
Once it works, paste any of these into the same session.
Attach a line chart of each notable metric over the last 8 weeks to the report.
When a metric moves 15% or more, break it down by plan and add the biggest driver to the commentary.
On the first Monday of each month, add a section that compares last month to the month before.
The agent reads production data, so the access is scoped and contained:
The weekly report stops depending on someone having a free Monday, and it arrives with a read of what changed rather than a table to interpret. The team starts the week looking at the movement that matters instead of assembling the numbers by hand.