$ loading_
帮你检查 skills-for-fabric 是否有新版本并查看更新日志
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "check-updates" 技能： 1. 下载 https://raw.githubusercontent.com/microsoft/skills-for-fabric/main/plugins/fabric-consumption/skills/check-updates/SKILL.md 2. 保存为 ~/.claude/skills/check-updates/SKILL.md 3. 装好后重载技能，告诉我可以用了
请检查 skills-for-fabric 是否有可用更新，并告诉我当前版本和最新版本。
返回当前本地版本、GitHub 最新版本，以及是否需要更新的结论。
帮我查看 skills-for-fabric 最新版本的更新内容，列出主要变更。
给出最新版本的更新摘要，突出新增功能、修复内容或重要变化。
我现在使用的 skills-for-fabric 是不是最新版本？如果不是，请说明差异。
说明当前是否已是最新版本，并简要对比当前版本与最新版本的差异。
This skill checks for updates to the skills-for-fabric marketplace at the start of each session.
Run this check once per week when any skills-for-fabric skill is first invoked. Skip if already checked within the last 7 days.
The update check marker is stored in a persistent, user-level directory shared across all sessions and all plugins in the Fabric Skills marketplace:
~/.config/fabric-collection/last-update-check.json
This file contains a JSON object mapping plugin names to the UTC date (YYYY-MM-DD) of their last update check:
{
"fabric-skills": "2026-02-17",
"another-plugin": "2026-02-16"
}
Before checking, read ~/.config/fabric-collection/last-update-check.json:
IMPORTANT — use UTC consistently: Always use the current UTC date when saving and comparing the last-update-check timestamp. Do not use the local system timezone, as it varies across environments and can cause the check to run too often or be skipped. In shell, use (Linux/macOS) or (PowerShell).
date -u +%Y-%m-%d(Get-Date).ToUniversalTime().ToString("yyyy-MM-dd")Note: Create the
~/.config/fabric-collection/directory if it does not exist. On Windows, use$env:USERPROFILE\.config\fabric-collection\.
Read the version field from the local plugin manifest. Two install layouts exist:
~/.copilot/installed-plugins/fabric-collection/fabric-skills/): the manifest is .github/plugin/plugin.json — there is no package.json here.package.json at the repo root.Read whichever is present. Both files contain a top-level "version": "<semver>" field.
Read the repository field from the same manifest you used in Step 1, and parse the URL to get owner and repo. The two layouts store the field differently:
.github/plugin/plugin.json) — plain URL string:
"repository": "https://github.com/<owner>/<repo>"
package.json at the repo root) — object whose url ends with .git:
"repository": { "type": "git", "url": "https://github.com/<owner>/<repo>.git" }
There is no bare plugin.json at the repo root in either layout, and there is no top-level package.json in the Copilot CLI plugin install — always use the path that matches your actual layout.
CRITICAL: Use the owner string exactly as it appears in the URL. Do NOT alter, normalize, or "correct" the owner name — including underscores, mixed case, or any other punctuation. Whatever the manifest's
repositoryURL says, that is the correct owner. (LLMs sometimes "auto-correct" underscores to hyphens — don't.)
Use the available tools in your environment to get the latest version. Try methods in strict order — only fall back to the next method if the previous one fails or is unavailable.
IMPORTANT: Methods A and B work with both public and private repositories. Method C only works with public repos. Always attempt A or B first.
Method A — Git CLI (preferred for git-clone installs)
…