How we handle GDPR data-subject requests on a deadline
Legal
A daily agent that collects each person's Linear and GitHub activity, prompts anyone with nothing recorded, and posts a concise team standup to Slack. Read-only across every tool.


A standup is supposed to answer one question: what did everyone do, and what's next. In practice it costs a meeting, or a thread where half the team pastes a summary and the other half forgets. The information already exists in Linear and GitHub; someone just has to gather it, format it, and chase the people who didn't post.
We run a daily agent on Kortix that does the gathering. It reads each person's Linear and GitHub activity, nudges anyone with nothing recorded, and posts a concise standup to a Slack channel. This is how we run our own standups, and the same setup works for any team.
A live standup takes a slot on everyone's calendar to relay information that's already recorded somewhere. An async thread saves the meeting but shifts the work onto people: each person has to remember to write, summarize their own day, and post it, and the ones who don't leave gaps.
The common workarounds are partial. A recurring bot that asks "what did you do yesterday?" still depends on everyone answering. A dashboard shows activity but doesn't summarize it or tell you who's quiet. Neither reads the tools where the work actually happened, so the summary is only as complete as the people filling it in.
On Kortix, a cron fires once each weekday morning and spawns an agent. It reads each team member's recent Linear issues and GitHub activity, builds a short per-person summary, checks who has nothing recorded, and posts the standup to a Slack channel. Anyone with a quiet day gets a light prompt so they can add context the tools can't see. The agent only reads; it never writes to Linear or GitHub.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the leaderboard 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 shipping brief agent in this workspace.
Create the agent agents/leaderboard.md. Its job is to post a weekly shipping brief to Slack and open the async standup thread. It may use the GH_TOKEN secret and the Slack channel.
Create the skill skills/weekly-leaderboard/SKILL.md with these rules:
Add a cron trigger weekly-leaderboard to kortix.yaml. It runs the leaderboard agent every Monday at 09:00 with the prompt "Load the weekly-leaderboard skill and post this week's shipping brief and standup thread to #eng."
Tell me which of these connectors and secrets are not set up yet.
Open a change request with all of it. Do not merge it.
Add a GitHub token as a workspace secret, and connect Slack as a channel so the agent can post the brief and the standup thread. The token is encrypted and injected into the session at runtime, scoped to this agent.
Counts merged PRs per person across the target repos.
Posts the weekly brief and opens the standup thread.
Merge the change request, then start a session with the leaderboard agent and send this prompt. Check the counts against GitHub before you let the schedule take over.
Post this week's shipping brief to #eng.
The change request added this trigger to kortix.yaml. From now on the agent
runs every Monday at 09:00. It reads last week's entry in memory before it
counts, so deltas and streaks carry from week to week. To change the time, edit
the cron line, or open Triggers in the workspace.
triggers:- slug: weekly-leaderboard name: Weekly leaderboard on: cron: "0 0 9 * * 1" run: agent: leaderboard prompt: Load the weekly-leaderboard skill and post this week's shipping brief and standup thread to #eng.Every count, delta and streak traces to gh pr list output. Bot and agent pull requests are listed apart, and a pull request a person drove counts for that person even when an agent helped write it. The agent posts one brief per run and pastes no tokens or customer data.
Each run ends with one brief in #eng and a standup thread under it. This is what a run looks like in the session:
42 pull requests merged by 9 people this week, plus 11 from bots. The top shipper merged 8, and 3 people extended a streak past four weeks. The standup thread is open in #eng.
Once it works, paste any of these into the same session.
Every Tuesday at 10:00, read the replies in this week's standup thread and post a five-line summary of priorities and blockers to #eng.
Add a line to the brief that lists pull requests that waited more than 2 days for a first review this week.
Here is our list of GitHub logins and names. Add it to the skill's identity map so the leaderboard shows names.
The agent reads everyone's activity across two tools and posts to a shared channel, so the access is scoped and contained:
The standup now arrives each morning as a Slack post built from the work people already recorded, with quiet days flagged instead of skipped. No one spends a meeting relaying status, and no one has to write their own summary for the activity the tools already have.