diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json
index d8c3d38..ee3cd92 100644
--- a/.claude-plugin/plugin.json
+++ b/.claude-plugin/plugin.json
@@ -1,7 +1,7 @@
 {
   "name": "microsoft-events",
   "description": "Connect your project to Microsoft Build and Ignite sessions — discover relevant talks, explore what's new for your stack, and plan next steps from your development environment.",
-  "version": "1.0.1",
+  "version": "1.0.2",
   "author": {
     "name": "Microsoft"
   },
diff --git a/.github/plugin/plugin.json b/.github/plugin/plugin.json
index 77ea67e..7922611 100644
--- a/.github/plugin/plugin.json
+++ b/.github/plugin/plugin.json
@@ -1,7 +1,7 @@
 {
   "name": "microsoft-events",
   "description": "Connect your project to Microsoft Build and Ignite sessions — discover relevant talks, explore what's new for your stack, and plan next steps from your development environment.",
-  "version": "1.0.1",
+  "version": "1.0.2",
   "author": {
     "name": "Microsoft",
     "url": "https://www.microsoft.com"
diff --git a/skills/microsoft-build/SKILL.md b/skills/microsoft-build/SKILL.md
index 63ae69f..06eee44 100644
--- a/skills/microsoft-build/SKILL.md
+++ b/skills/microsoft-build/SKILL.md
@@ -218,8 +218,9 @@ The user wants to know what recent Microsoft updates are relevant to their proje
    - Documentation updates: what changed in the SDKs and services they use, with links to current docs
    - Relevant sessions: event sessions that cover their technologies, sorted by relevance
 7. For high-confidence matches, offer to explain the migration path or impact on the developer's project
+8. **Version check**: Fetch `https://raw.githubusercontent.com/microsoft/Build-CLI/refs/heads/main/.github/plugin/plugin.json` and read the `version` field. Compare it to the local `.github/plugin/plugin.json` version in this repo. If the remote version is higher, append to your response: "💡 A newer version of the Build CLI skill (v{remote}) is available. Run `/plugin update microsoft/Build-CLI` to get the latest sessions and features."
 
-Be specific. "The new Azure Functions v4 streaming support affects your queue trigger in /api/process.ts" is useful. "There were updates to Azure Functions" is not.
+Be specific."The new Azure Functions v4 streaming support affects your queue trigger in /api/process.ts" is useful. "There were updates to Azure Functions" is not.
 
 **Output format:**
 ```
@@ -258,6 +259,7 @@ The user wants a personalized event schedule based on their projects or interest
 6. For each recommended session, include: session code, title, one-line reason it's relevant, speaker(s), location, time slot, type (lab/breakout/demo), level
 7. If they have time for multiple sessions, suggest a learning path order: foundational first, then intermediate/advanced, ending with hands-on labs to apply what they learned
 8. After helping the user build a schedule (finding sessions, flagging conflicts), offer: "Would you like me to save this as a markdown file?" Do not create a file until the user confirms. Include day, time, session code, title, and location.
+9. **Version check**: Fetch `https://raw.githubusercontent.com/microsoft/Build-CLI/refs/heads/main/.github/plugin/plugin.json` and read the `version` field. Compare it to the local `.github/plugin/plugin.json` version in this repo. If the remote version is higher, append to your response: "💡 A newer version of the Build CLI skill (v{remote}) is available. Run `/plugin update microsoft/Build-CLI` to get the latest sessions and features."
 
 **Output format:**
 ```
@@ -356,6 +358,7 @@ The user just attended or watched a session and wants next steps.
    - **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"
+5. **Version check**: Fetch `https://raw.githubusercontent.com/microsoft/Build-CLI/refs/heads/main/.github/plugin/plugin.json` and read the `version` field. Compare it to the local `.github/plugin/plugin.json` version in this repo. If the remote version is higher, append to your response: "💡 A newer version of the Build CLI skill (v{remote}) is available. Run `/plugin update microsoft/Build-CLI` to get the latest sessions and features."
 
 **Output format:**
 ```