From cb3a153969fb8ea9bee6072ef2cce7ee39c07641 Mon Sep 17 00:00:00 2001
From: "Mike Kinsman (He/Him)" <32281167+mikekinsman@users.noreply.github.com>
Date: Wed, 6 May 2026 17:42:29 -0700
Subject: [PATCH 1/3] Update SKILL.md: add next-step link to Start Building,
 rename Azure AI Foundry to Microsoft Foundry

- Surface session next-step link (repo or next-steps site) in the 'What should I do after session' flow
- Update two example CLI commands to use current product name 'Microsoft Foundry'

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---
 skills/microsoft-events/SKILL.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/skills/microsoft-events/SKILL.md b/skills/microsoft-events/SKILL.md
index f7be56d..f4c85e7 100644
--- a/skills/microsoft-events/SKILL.md
+++ b/skills/microsoft-events/SKILL.md
@@ -98,7 +98,7 @@ The msevents CLI fetches, caches, indexes, and searches the session catalog loca
 
 ```sh
 # Search by keyword
-npx @microsoft/events-cli sessions --query "Azure AI Foundry" --event build-2026 --json
+npx @microsoft/events-cli sessions --query "Microsoft Foundry" --event build-2026 --json
 
 # Search by technology (matches product, tags, topic, languages, title, description)
 npx @microsoft/events-cli sessions --tech "Azure Cosmos DB" --event build-2026 --json
@@ -107,7 +107,7 @@ npx @microsoft/events-cli sessions --tech "Azure Cosmos DB" --event build-2026 -
 npx @microsoft/events-cli sessions --speaker "Scott Hanselman" --event build-2026 --json
 
 # Combine filters
-npx @microsoft/events-cli sessions --tech "Azure AI Foundry" --speaker "Yina Arenas" --event build-2026 --json
+npx @microsoft/events-cli sessions --tech "Microsoft Foundry" --speaker "Yina Arenas" --event build-2026 --json
 
 # Look up a specific session by code
 npx @microsoft/events-cli session BRK155 --json
@@ -348,7 +348,7 @@ The user just attended or watched a session and wants next steps.
    - **Without CLI**: Fetch the catalog and find by code or title
 2. Check the `relatedSessionCodes` field first — use those if populated
 3. Build a response with up to three sections:
-   - **Start building**: search Learn MCP for quickstarts and tutorials matching the session's tech. Frame around what was covered: "In BRK241 you heard about the Foundry Agent Service. Here's how to build your first agent..."
+   - **Start building**: surface the session's next-step link first (this points to either the session's GitHub repo or the Build next-steps site). Then search Learn MCP for quickstarts and tutorials matching the session's tech. Frame around what was covered: "In BRK241 you heard about the Foundry Agent Service. Here's how to build your first agent..."
    - **Go deeper**: related documentation, API references, architecture guides for the session's technologies
    - **Next sessions**: find related sessions via `relatedSessionCodes`, same `topic`, or same `product`/`tags`. Suggest a progression: if they saw a breakout, suggest the hands-on lab; if they did a lab, suggest the advanced breakout.
 4. If Learn MCP is unavailable, suggest specific search terms on learn.microsoft.com rather than generic "check the docs"

From 7f5d5e28213bc971f678dc7739e4c84c80f645a3 Mon Sep 17 00:00:00 2001
From: "Mike Kinsman (He/Him)" <32281167+mikekinsman@users.noreply.github.com>
Date: Wed, 6 May 2026 20:59:51 -0700
Subject: [PATCH 2/3] trigger re-review


From 804aaef510466438264203c4f135711ec854fafc Mon Sep 17 00:00:00 2001
From: "Mike Kinsman (He/Him)" <32281167+mikekinsman@users.noreply.github.com>
Date: Wed, 6 May 2026 21:00:04 -0700
Subject: [PATCH 3/3] trigger re-review