Agent Templates
Engineering standup agent

AI standup bot that builds daily briefs from GitHub, GitLab, and Jira

Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.

Engineering standup agent
Sample Agent for Acme
May 22 · 10:00 AM ·
47s
Post today's standup for the engineering team
J
Fetching GitHub PRs and Jira issues
Fetch GitHub PRs
github_pull_requests_list
Query Jira issues
jira_issues_search
Post standup to Slack DM
slack_send_message
Standup posted
Top activity (last 24h)
"3 PRs merged, 2 Jira issues moved to Done"
Posted to each engineer's Slack DM
Result
8 engineers covered — GitHub, GitLab, Jira
Blockers flagged: 1 PR awaiting review for 2+ days
Message Claude...
Trusted by teams shipping agents to production
Engineering standup agent
Sample Agent for Acme
May 22 · 10:00 AM ·
47s
Post today's standup for the engineering team
J
Fetching GitHub PRs and Jira issues
Fetch GitHub PRs
github_pull_requests_list
Query Jira issues
jira_issues_search
Post standup to Slack DM
slack_send_message
Standup posted
Top activity (last 24h)
"3 PRs merged, 2 Jira issues moved to Done"
Posted to each engineer's Slack DM
Result
8 engineers covered — GitHub, GitLab, Jira
Blockers flagged: 1 PR awaiting review for 2+ days
Message Claude...

How the agent pulls activity across GitHub, GitLab, and Jira into a per-engineer brief

A real working agent you can deploy

This repo uses ENGINEER_ID and ENGINEER_NAME env vars to simulate one engineer. In production, set ENGINEERS as a JSON array to run the full team. Connector names — GITHUB_CONNECTOR, GITLAB_CONNECTOR, JIRA_CONNECTOR, SLACK_CONNECTOR — must match your Scalekit dashboard exactly, including any generated suffix.

01
Authorize, then orchestrate
run_flow.py
ensure_authorized() runs once per connector per engineer at startup. It calls connect.get_or_create_connected_account() and prints a magic link if status is not ACTIVE. Every subsequent run skips the prompt and proceeds immediately.
run_flow.py
for connector in [GITHUB_CONNECTOR, GITLAB_CONNECTOR,
                  JIRA_CONNECTOR, SLACK_CONNECTOR]:
    ensure_authorized(connector, engineer_id)
# ensure_authorized() calls
# connect.get_or_create_connected_account() and
# prints a magic link if status != "ACTIVE"
02
Fetch GitHub pull requests
run_flow.py
03
Fetch GitLab MRs and pipeline status
run_flow.py
04
Query Jira with assignee = currentUser()
run_flow.py
05
Build digest and post to Slack DM
run_flow.py

Agents that run daily standups, without the auth plumbing

Four things you'd otherwise build: GitHub OAuth per engineer, GitLab tokens, Jira OAuth with auto-refresh, Slack credentials. Handled.

1
Install
npx @scalekit-inc/cli setup
# select your coding agent
# enable scalekit MCP server on coding agent
terminal
npx @scalekit-inc/cli setup
# select your coding agent
# enable scalekit MCP server on coding agent
terminal
npx @scalekit-inc/cli setup
# select your coding agent
# enable scalekit MCP server on coding agent
terminal
npx @scalekit-inc/cli setup
# select your coding agent
# enable scalekit MCP server on coding agent
terminal
npx @scalekit-inc/cli setup
# select your coding agent
# enable scalekit MCP server on coding agent
2
You have the Scalekit authstack plugin installed (AgentKit + SaaSKit skills and MCP auth). Before coding, auto-load the AgentKit skills relevant to connectors (GitHub, GitLab, Jira, Slack) and use the Scalekit MCP server to validate tool calls instead of hand-written API logic.

For each engineer, fetch their open GitHub PRs, GitLab merge requests with pipeline status, and Jira issues assigned to them (assignee = currentUser()) via the appropriate AgentKit connector tools. Build a per-engineer digest and post it to their own Slack DM. Ask before using write tools (posting the Slack DM); fetching PRs, MRs, and issues runs without asking.
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.
Try other Agent Templates

Prebuilt agents you can ship today

Each one runs on delegated identity, scoped per user.

ENGINEERING
Engineering standup agent
Pull commits from GitHub and GitLab, track Jira issue movement, and post a per-engineer standup brief to Slack.
ENGINEERING
DevOps assistant agent
Poll GitHub for failing checks and stale pull requests, open Linear issues for the ones that need work, and digest to Slack.
ENGINEERING
Auto-release notes agent
Group merged GitHub PRs into structured release notes, publish the page to Notion, and announce the release in Slack.
ENGINEERING
Slack workflow agent (LangGraph)
LangGraph agent that drives multi-step Slack workflows: triggers, approvals, and follow-up actions per user identity.
SUPPORT
Support triage agent
Classify new Zendesk tickets, search the Notion knowledge base for an answer, and route what it cannot resolve to Slack.
OPS
Email-to-calendar scheduling agent
Read scheduling intent out of Gmail threads, resolve mutual free time, and create the Google Calendar event.

Build your own
multi-connector agent

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