AI AGENTS
On-Demand Standup Status Agent in Slack
A Slack slash-command agent that, when a manager asks about any teammate, pulls that person's latest Loom update and recent commits and replies with a synthesized blocker-aware…
How it runs
The automated pipeline, trigger to output.
- TriggerSlack slash command naming teammateSlack
- ActionFetch teammate's latest Loom standupLoom
- ActionPull recent commits and open PRsGitHub
- ActionReconcile and write status with LLMOpenAI
- OutputReply in Slack threadSlack
What it does
Gives managers instant standup context without waiting for the daily digest. A manager invokes a Slack command naming a teammate; the agent fetches that person's most recent Loom standup and their recent GitHub commit history, reconciles the two, and replies in-thread with a concise status: current focus, what shipped, and any open blocker, all grounded in real activity.
When to use it
When a 1:1 or planning conversation needs a quick, accurate read on what someone is actually working on, and scrolling Loom and GitHub by hand is too slow.
How it works
- 1A Slack slash command naming a teammate triggers the agent.
- 2The agent resolves the named person and fetches their latest Loom standup transcript.
- 3It pulls that person's recent GitHub commits and open PRs.
- 4An OpenAI step reconciles spoken update against actual code activity and writes a focused status with any blocker flagged.
- 5The agent replies in the originating Slack thread.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect LoomVideo transcripts, libraries.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Connect OpenAIModels, embeddings, files.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.