If you work in cloud you’ll understand the difficulty in keeping track of the changing landscape across all the different services and tooling that you use. Every morning I would log in and open up 2 dozen tabs worth of tech news and read through them all to understand if there’s any new features we can implement, or any security issues we need to be aware of. None of them knew what I actually run, so none of them could tell me which CVE deserved my attention and which one I could happily scroll past. What I wanted to do was find an easier way to digest all this info – but also tailor it to my specific stack.
So with the addition of Claude Code routines, this allowed me to setup a scheduled task that runs every morning; that can runs a skill but also has context to my github repo. So it can digest all the new Azure updates, or AI updates – but then also look at my code where everything is IAC and documented, and tell me which ones actually apply to me.
Before the agent decides anything is worth telling me, it reads my own infrastructure. So it takes into context the repo, the IaC, the manifests and builds a picture of what I have deployed, then checks every story against that. So a generic “new high-severity vuln in X” turns into “X is the thing you run here, in this file, and here’s what you’d change.” I find this particularly useful for azure service updates – there’s just so many coming out now that it’s hard to keep track – so this gives me a easy way to see which ones apply to me and gives me easy implementation guidance. If the change is easy enough )maybe it’s just a new property or feature to enable) – I sometimes even get that current Claude window that ran my daily brief to just implement the change and raise a PR.
What it actually does
Each morning it pull`s from around twenty sources in parallel including cloud provider blogs, infrastructure-as-code release notes, a handful of vendor security blogs, AI model release notes, GitHub’s changelog, an Aussie tech feed like IT Brief, and Hacker News for anything the official channels are slow to mention. Then it grades everything into three buckets:
- Something I run is affected (or under active exploit)
- Worth scheduling
- Worth knowing.
The output is a single self-contained HTML page that I can read in the browser, or save as a PDF if I want to keep a copy. It opens with a short summary so I can get the overall picture in a few seconds, and then groups the rest into sections such as AI and models, cloud and infrastructure, security and developer tooling, so I can go straight to whatever is relevant that day. The items that affect something I actually run are pulled to the top and flagged, each with a short note on why it matters and which file or service it relates to.
The last section is the one I get the most out of, a short list of actionable items. Each one is written so that it is specific enough to act on and names the file or service it applies to, which means I can either make the change there and then or save it as a task for later. If nothing meaningful came up that morning the list is left empty, since I would rather see that it is a quiet day than have the page padded out with things that don’t need doing.
The skill
---name: morning-briefdescription: A daily cloud / AI / security brief tailored to your own stack. Fetches a curated set of sources, filters them against your infrastructure-as-code, groups items by importance, and renders a single self-contained HTML page that ends with actionable items. Triggers on "morning brief", "run my brief", "what happened overnight", or /morning-brief.---# Morning BriefA daily operational brief for someone working across cloud, infrastructure, AI and security. It reads a curated set of sources, filters them against what you actually run, and produces a single self-contained HTML page you can read in a minute and act on.Self-contained: the output is one HTML file. If you want a PDF, print it from the browser rather than rendering one in the skill.## Workflow### 1. Establish the dateRead today's local date so the file name and header are current.### 2. Fetch sources in parallelFire the source list below as parallel fetches. Some pages are JavaScript-rendered and may come back empty; if one does, note it and move on rather than retrying.### 3. Ground against your own stackThis is the step that makes the brief useful rather than just another feed. If you have access to your repository, grep your infrastructure-as-code (Bicep, Terraform, and similar) and your package manifests to build a picture of what is actually deployed: the compute and hosting you use, your databases and caches, your secrets store and API gateway, the AI and model services and SDKs you depend on, and your endpoint-management tooling. Filter any region-specific availability docs to your own region. Every item that touches your stack gets an impact note naming the specific file or service it relates to.### 4. Classify by importanceAssign one rating to each item:- must: production impact, or an active exploit affecting something you run- high: relevant to your stack and worth scheduling- med: worth knowingCut anything below med. This is a brief, not a news aggregator.### 5. Write the recommended actionsThe actions section is the payoff. Each item should be specific enough to act on and should name the file or service it applies to, rather than "consider reviewing X". Cap the list at around four. If nothing genuinely warrants action, leave the section empty rather than padding it.### 6. Render the HTMLProduce a single self-contained HTML page with inline CSS, following the structure and styling below.## Output structure (in order)1. Header: title, a short subtitle, and today's date.2. An optional status panel: a quiet neutral card for whatever you most want to see at a glance, for example model or service availability in your region. Keep it factual, and if nothing changed say so rather than dramatising it.3. TL;DR: four to six bullets, each a short tag plus a one-line summary.4. Must read: three to five items, each with a short "why it matters to you" note tied to a specific file or service.5. AI and models.6. Cloud and infrastructure.7. Security.8. Developer tooling.9. Worth a glance: a short tail of lower-priority items.10. Recommended actions: at most four, each specific and naming a file or service. Empty if nothing fits.11. Sources scanned: just what was actually fetched.12. Footer: generation date.## StylingSelf-contained HTML with inline CSS that reads well on screen and prints cleanly, since the PDF path is just Print from the browser.- Dark mode via prefers-color-scheme- A4 print page with a small margin, and page-break-inside: avoid on the main cards- Importance badges: must (red), high (orange), med (teal)- Must-read and recommended-action cards carry a coloured left border- The header panel is quiet and neutral, not a loud gradient## SourcesA starting set. Swap these for the feeds that match your own stack.AI and models- Your cloud provider's model-availability docs, filtered to your region- Anthropic / Claude release notes and the Claude blog- Your other model providers' release notesCloud and infrastructure- Your cloud provider's main blog and its AI blog- Cloud "what's new" update pages (often JavaScript-rendered and empty)- Infrastructure-as-code release notes (for example, terraform releases on GitHub)- Your endpoint-management vendor's blog- Cloud blogs you trustSecurity- A major threat-intelligence blog (often JavaScript-rendered)- A vulnerability research blog such as Tenable- A general security news feed such as The CyberWireDeveloper tooling- The GitHub changelogGeneral- Hacker News, AI / cloud / security stories only- An IT news feed for your region, such as IT Brief## Rules- Single self-contained HTML page. No PDF rendering in the skill; print from the browser instead.- Don't lead with regional model availability unless it actually changed.- Impact notes name a file or service, never "consider reviewing".- Recommended actions are executable and reference real files, not vague suggestions.- Cut anything below med.
And this is an example of what it looks like:
For this blog I have made the Claude skill generic; as I don’t want to give my own repository stack away – but the beauty of this skill is that you can tailor it however you want by adding your own links to the ##Sources section. So if you’re using GCP, AWS, Gitlab or whatever, just add your source links in there and it will spit out a blog tailored for you.
Setup and Final Notes
As I mentioned; I run this as a Claude Code routine with the following setup:
So I run it daily at around 8.40am so it’s available for me to read in the morning with my morning coffee 🙂 Make sure to set your repo as well to get that all important context.
One annoying thing about this skill and Claude in general is that it can’t retrieve data from Reddit. The r/Azure community is actually pretty active and is a good way of finding out about new Azure features and funnily enough; finding out about issues across Azure and the Microsoft environment. So here are some extra sources that you can’t use in the skill but is still worth checking out daily (if not for news, then for memes):
- https://www.reddit.com/r/AZURE/
- https://www.reddit.com/r/devops/
- https://www.reddit.com/r/ClaudeAI/
- https://www.reddit.com/r/cybersecurity/
I hope this serves you well and you enjoy a more tailored news brief in the morning. Comment below if there’s any improvements that you’d make; I’d love to hear them.
Alex D'Antico Tech 
Leave a comment