Daily air quality and outdoor activity Slack digest for distributed teams

Every weekday at 8am US Eastern time, run an agent that posts a single grouped air quality and outdoor activity digest to a Slack channel for our distributed team. The trigger is a cron schedule.

Configurable inputs the user should fill in: a list of teammate cities (each as a label plus latitude and longitude), the Slack channel id or name to post to, and the cron schedule and time zone.

For each configured city, call Weather (Get Air Quality) with the latitude and longitude to read the current AQI and pollutant concentrations, then call Weather (Get Current Weather) with the same coordinates to read temperature, conditions, wind, and humidity. Request imperial units so temperatures come back in Fahrenheit and wind in mph.

Reason about the combined picture for each city instead of printing raw numbers. Translate the air quality index into a category (Good, Moderate, Unhealthy for Sensitive Groups, Unhealthy, Very Unhealthy, Hazardous). Call out the dominant pollutant (for example PM2.5, ozone, NO2) only when the category is Moderate or worse. Note weather worth knowing: heat above 90F, cold below 32F, sustained wind above 20 mph, active rain or thunderstorms. Skip mundane details when the day is unremarkable.

For each city, write one short plain-language outdoor activity recommendation tied to that city's data. Examples of the tone to aim for: safe for an outdoor run, mask suggested outside, keep windows closed and run an air purifier, sensitive groups should stay in, hold off on the lunchtime walk and try the evening. Recommendations should follow from the data, not be generic.

Group cities by risk level so the highest-risk locations float to the top of the digest. Order the sections: (1) Hazardous, Very Unhealthy, or extreme weather; (2) Unhealthy and Unhealthy for Sensitive Groups; (3) Moderate; (4) Good air and mild weather cities, condensed to one tight line each.

Post the whole digest as one Slack message with Slack Bot (Send a Message) to the configured channel. Format with Slack mrkdwn: a header line such as Air quality and outdoor activity, {date}, then a section per risk tier with each city as its own bullet. Each bullet should lead with the city in bold, then a one-line summary, then the recommendation. Keep the entire message scannable, ideally under 25 lines total even with a long city list. Do not at-mention anyone.

If a city's air quality or weather lookup fails, include that city in a short Missing data section at the bottom rather than dropping it silently. Never paste raw AQI numbers, raw pollutant concentrations, or raw wind speeds without translating them into plain language first.

Additional information

What does this prompt do?

Posts one grouped Slack message every weekday morning covering every city where your team is based.
Translates each city's air quality into plain language (good, moderate, unhealthy) and calls out the dominant pollutant when it matters.
Pairs the air score with a quick weather note (heat, cold, wind, rain) and writes a short outdoor activity tip for each city.
Sorts the digest so the highest-risk cities float to the top and good-air cities sit in a tight summary at the bottom.

What do I need to use this?

A Slack workspace and the channel where the digest should be posted.
A list of cities for where your team lives or works (city name plus latitude and longitude).
A morning time and time zone you want the digest to land at.

How can I customize it?

Change the schedule, posting channel, or time zone to match your team's working day.
Add or remove cities as people join, move, or travel.
Tighten or loosen the thresholds for when the digest recommends a mask, flags heat, or calls out wind.

Frequently asked questions

How are the outdoor activity recommendations decided?

The agent reads each city's current air quality and weather, compares them against simple thresholds, and writes a short plain-language tip such as safe for an outdoor run, mask suggested, or keep windows closed.

Will this flood the channel with separate messages per city?

No. The whole team gets one grouped digest per run, with cities sorted by risk so the worst air or weather is at the top.

What happens if a city's data is missing or the lookup fails?

That city gets called out in a short missing data section at the bottom of the digest so the rest of the report still lands on time.

Can we use this for a single location instead of a distributed team?

Yes. Configure one city and the digest will post a single short report for that location each morning.

Does it print raw AQI numbers?

No. The agent reasons about thresholds and translates the score into a plain category and an outdoor activity tip, so the message stays scannable.