Agent Templates
Engineering Standup Agent

Engineering standup agents that aggregate PRs, MRs, and Jira issues across GitHub, GitLab, and Jira

Connect four services with per-engineer OAuth. Every developer gets a personal daily digest — open PRs, MR pipeline status, and in-progress Jira issues — delivered to their own Slack DM.

Engineering Standup Agent
Sample Agent for Acme
May 22 · 10:00 AM ·
47s
Message Claude...
Trusted by teams shipping agents to production
Engineering Standup Agent
Sample Agent for Acme
May 22 · 10:00 AM ·
47s
Message Claude...

How the agent collects context across four tools and delivers a personal standup in five steps

A real working agent you can deploy

Per-engineer OAuth is non-negotiable here. Shared service accounts break currentUser() JQL in Jira and expose incorrect data sets. Scalekit handles token refresh automatically for all four connectors so every engineer's digest is scoped to their own identity.

Why choose Scalekit

Delegated identity. Not service accounts.

Credentials never touch agent code or LLM context. The agent acts as the user, not as a shared bot.
Delegated OAuth - Agent reads your calendar, your inbox — scoped to the authorizing identity, not org-wide.
Credentials outside agent runtime  -  Tokens never touch agent code or LLM context. Both failure modes covered.
Token lifecycle automatic  -  Refresh, expiry, rotation across all connectors. One SDK call. Zero management code.
200+ prebuilt connectors  -  Google, Slack, HubSpot, GitHub, Jira, Notion, Salesforce — same auth pattern everywhere.

Agents that run standups, without the auth plumbing

Four OAuth systems you'd otherwise build: GitHub, GitLab, Jira Cloud, and Slack — each with its own token lifecycle and refresh logic. Handled.

OAuth flow per connector
One SDK call returns a delegated token for any connector. Google, HubSpot, Slack, same pattern across all 200+ connectors
Secure token vault  
Scalekit stores OAuth credentials outside agent code and outside LLM context. Both are separate failure modes. Both covered
Token refresh logic
Token lifecycle handled automatically — expiry, rotation, re-auth — across every connector. Agent runs in 6 months. Same call works
Try other Agent Templates

Prebuilt agents you can ship today

Each one runs on delegated identity, scoped per user.

ENGINEERING
Auto-release notes agent
Group merged GitHub PRs by feature, fix, or chore and publish release notes per tag. No manual changelog grooming.
ENGINEERING
Slack workflow agent (LangGraph)
LangGraph agent that drives multi-step Slack workflows: triggers, approvals, and follow-up actions per user identity.
ENGINEERING
DevOps assistant agent
Triage GitHub incidents, open Linear tickets, and notify the on-call channel in Slack with context already attached.
SUPPORT
Support triage agent
Read Zendesk tickets, fetch runbooks from Notion, and route to the right Slack channel with a drafted response.
GTM
HubSpot to Slack updates agent
Watch HubSpot deal stage changes and post structured updates to the right Slack channel. Reps stop checking the CRM all day.
SALES
Sales call prep agent
Pull Granola notes and Attio contact history to draft a pre-call brief before every sales meeting. Zero rep input.
Customize the sample

Clone it and own it with connectors you choose

Don't sweat the integration. Point a coding agent at the repo. It clones, swaps in your connectors, and adds new steps for you.

1
Install a coding agent
2
Give it this prompt
Connectors used
No items found.

Build your own
multi-connector agent

Add connectors. Change the LLM. Same delegated auth pattern.