Skip to content

Add version check to skill workflows #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mikekinsman wants to merge 1 commit into from
Closed

Add version check to skill workflows #30

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .claude-plugin/plugin.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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"
},
Expand Down
2 changes: 1 addition & 1 deletion .github/plugin/plugin.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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"
Expand Down
5 changes: 4 additions & 1 deletion skills/microsoft-build/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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."
Copy link
Copy Markdown
Contributor

@TianqiZhang TianqiZhang May 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The local .github/plugin/plugin.json path is not a reliable source for the installed plugin version. During normal skill use, the current workspace is usually the user’s project, not this plugin repo, and users can directly install this skill via npx skills without installing plugin.

Until the industry agrees on a unified installed-plugin/skill versioning pattern, it's very difficult to make SKILL.md self-update.


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:**
```
Expand Down Expand Up @@ -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:**
```
Expand Down Expand Up @@ -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:**
```
Expand Down
Loading