Daily federal court opinion digest in Slack

By General Input

Every weekday at 7:30am ET, get a threaded Slack briefing of new Supreme Court and federal circuit opinions, summarized for practitioners.

Integrations

  • CourtListener
  • Slack Bot

Type

Agentic Task

Categories

  • Operations
  • Personal Productivity

Build me an agent workflow that runs every weekday at 7:30am ET and posts a "morning court report" digest to a Slack channel I choose.

On each run, the agent should pull newly filed opinions from CourtListener for a configurable set of courts. Default the watch list to the U.S. Supreme Court (scotus) and all federal circuit courts of appeals (the thirteen circuits). Scope the lookup to opinions filed in the last 24 hours, ordered newest first. Use CourtListener's Search operation or List Opinion Clusters with a date_filed filter for the last day and a court filter for the watch list — whichever returns the cleanest set of new clusters for that window.

For each new opinion cluster, fetch the cluster with Get Opinion Cluster to grab the case name, citation, panel, court, and date_filed, then pull the underlying opinion text with Get Opinion. Read the opinion and write a tight three bullet summary in this exact shape:

1. Parties and posture — who sued whom, in what posture (cert review, appeal from district court, etc.).

2. Holding — one or two sentences on what the court actually decided.

3. Why it matters — one or two sentences on the practical impact for practitioners (split deepened, standard clarified, new test announced, etc.).

Then post the digest to Slack as a single threaded message using the Slack Bot "Send a Message" operation:

- The parent message goes to the chosen channel and lists today's date plus the case names with their court abbreviations, one per line (e.g. "SCOTUS — Loper Bright v. Raimondo"). Keep it scannable.

- For each case, send a threaded reply (same channel, thread_ts set to the parent's ts) containing the case name as a bold header, the three bullet summary, and a link back to the opinion on CourtListener (https://www.courtlistener.com plus the absolute_url from the cluster).

If zero new opinions came in for the watch list in the last 24 hours, skip the run entirely — do not post a "nothing today" message. The channel should stay quiet on slow days.

Inputs the workflow should expose so I can tweak it later: the Slack channel id, the list of CourtListener court ids in the watch list, the schedule (default weekdays 7:30am America/New_York), and the lookback window (default 24 hours).

Use the slackbot integration (bot token) for the Slack posting so the digest comes from a workspace bot identity, not from a specific user. Use the courtlistener integration for all CourtListener calls.

Related prompts

Explore more prompts
A brand asset library your marketing team actually searchesTurn Mailjet email clicks into ranked HubSpot follow-upsClean out the Looker dashboards and Looks nobody opensLiveKit live operations console for room moderationWake up dormant Keap leads with a researched reasonLiveChat coverage board for planning next week's shiftsPhone routing control panel for LiveKit voice agentsLinkedIn Ads budget pacing dashboard for every client accountGive your team Looker numbers without buying more seatsPause marketing emails to escalated customers, then restore them