[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WZTK3MQCC5SDVHS2SQT5B7":3,"skill-same:01M6WZTK3MQCC5SDVHS2SQT5B7":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6WZTK3MQCC5SDVHS2SQT5B7","azd-publish",null,"Prepare and publish a new version of the waza azd extension.\nUSE FOR: \"publish extension\", \"release new version\", \"bump version\",\n\"prepare release\", \"update changelog\", \"azd publish\", \"new release\",\n\"version bump\", \"cut a release\".\nDO NOT USE FOR: running evals (use waza), writing skills (use skill-authoring),\nCI\u002FCD pipeline changes (edit workflow files directly).","microsoft\u002Fwaza","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M6WZT4PAP160SPCF851532KH",1511,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fazd-publish\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"azd publish","publish","evals","new","running","changes","for","running evals","prepare release","do","files","bump","writing","version","use","update changelog","pipeline","ci","changelog","publish extension","workflow","2026-11-10 10:12:30",false,"---\r\nname: azd-publish\r\ndescription: |\r\n  Prepare and publish a new version of the waza azd extension.\r\n  USE FOR: \"publish extension\", \"release new version\", \"bump version\",\r\n  \"prepare release\", \"update changelog\", \"azd publish\", \"new release\",\r\n  \"version bump\", \"cut a release\".\r\n  DO NOT USE FOR: running evals (use waza), writing skills (use skill-authoring),\r\n  CI\u002FCD pipeline changes (edit workflow files directly).\r\nmetadata:\r\n  author: spboyer\r\n  version: \"1.0\"\r\n---\r\n\r\n# azd Extension Publish\r\n\r\n> Automate version bumps, changelog updates, and PR creation for waza azd extension releases.\r\n\r\n## When to Use\r\n\r\n- Preparing a new release of the waza azd extension\r\n- Bumping the version number (major, minor, or patch)\r\n- Updating the changelog with changes since last release\r\n- Creating a release PR for review\r\n\r\n## Workflow\r\n\r\nFollow these steps **in order**. Ask the user for input at each decision point.\r\n\r\n### Step 1: Gather Changes and Update Changelog\r\n\r\nGet the current version from `version.txt` and `extension.yaml`, then collect commits since the last release:\r\n\r\n```bash\r\ncat version.txt\r\n\r\n# Find the latest azd extension version tags\r\ngit tag --list 'azd-ext-microsoft-azd-waza_*' --sort=-v:refname | head -5\r\n\r\n# Get commits since last azd extension tag\r\nlast_tag=$(git tag --list 'azd-ext-microsoft-azd-waza_*' --sort=-v:refname | head -1)\r\ngit log \"${last_tag}..HEAD\" --oneline --no-decorate\r\n```\r\n\r\nIf `version.txt` and `extension.yaml` differ, flag it to the user before proceeding.\r\n\r\nSummarize the changes grouped by type:\r\n- **Added** — `feat:` commits\r\n- **Fixed** — `fix:` commits\r\n- **Changed** — `refactor:`, `chore:`, `docs:` commits\r\n- **Removed** — any removal-related commits\r\n\r\nPresent the summary to the user for review.\r\n\r\nThen update `CHANGELOG.md`. The changelog follows [Keep a Changelog](https:\u002F\u002Fkeepachangelog.com\u002Fen\u002F1.1.0\u002F) format.\r\n\r\nPerform these updates (using a placeholder version `X.Y.Z` — the actual version is determined in Step 2):\r\n\r\n1. **Move Unreleased content**: Move any items currently under `## [Unreleased]` into a staging area. If `[Unreleased]` is empty, populate from the git log summary gathered above.\r\n\r\n2. **Populate from commits**: Prepare entries grouped under `### Added`, `### Fixed`, `### Changed` as appropriate based on the commits gathered above.\r\n\r\nHold these changelog entries — the new version section header and comparison links will be finalized after the version is determined in Step 2.\r\n\r\n### Step 2: Determine Version\r\n\r\nBased on the changes gathered in Step 1, **recommend** a version bump type using standard semver semantics:\r\n\r\n- **major** — Breaking changes, removals of public API (`feat!:`, `BREAKING CHANGE:`) → `(MAJOR+1).0.0`\r\n- **minor** — New features, backward compatible (`feat:`) → `MAJOR.(MINOR+1).0`\r\n- **patch** — Bug fixes, docs, refactors, chores (`fix:`, `docs:`, `refactor:`, `chore:`) → `MAJOR.MINOR.(PATCH+1)`\r\n\r\nPresent the recommendation with rationale (e.g., \"I see 3 `feat:` commits and no breaking changes — recommending a **minor** bump\").\r\n\r\n**ASK THE USER** to confirm the recommended bump or choose a different one.\r\n\r\nCompute the new version and confirm with the user before proceeding.\r\n\r\nThen finalize the changelog:\r\n\r\n1. **Create new version section**: Insert a new section below `## [Unreleased]` with today's date:\r\n   ```markdown\r\n   ## [X.Y.Z] - YYYY-MM-DD\r\n   ```\r\n\r\n2. **Add the prepared entries** from Step 1 under the new version section.\r\n\r\n3. **Update comparison links** at the bottom of the file:\r\n   ```markdown\r\n   [Unreleased]: https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza\u002Fcompare\u002Fazd-ext-microsoft-azd-waza_X.Y.Z...HEAD\r\n   [X.Y.Z]: https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza\u002Fcompare\u002Fazd-ext-microsoft-azd-waza_PREVIOUS...azd-ext-microsoft-azd-waza_X.Y.Z\r\n   ```\r\n\r\n4. **Clear the Unreleased section**: Leave `## [Unreleased]` with empty subsections or blank.\r\n\r\n### Step 3: Update Version Files\r\n\r\nUpdate these files with the new version:\r\n\r\n1. **`version.txt`** — Replace contents with new version string\r\n2. **`extension.yaml`** — Update the `version:` field\r\n\r\n### Step 4: Review Changes\r\n\r\nShow the user a summary of all changes made:\r\n- New version number\r\n- Files modified: `version.txt`, `extension.yaml`, `CHANGELOG.md`\r\n- Show the diff with `git diff`\r\n\r\n### Step 5: Ask About PR Creation\r\n\r\n**ASK THE USER**: Should I create a PR with these changes?\r\n\r\nIf **yes**:\r\n\r\n1. Create a feature branch:\r\n   ```bash\r\n   git checkout -b release\u002Fv{VERSION}\r\n   ```\r\n\r\n2. Stage and commit all changes:\r\n   ```bash\r\n   git add version.txt extension.yaml CHANGELOG.md\r\n   git commit -m \"chore: Prepare release v{VERSION}\"\r\n   ```\r\n\r\n3. Push the branch:\r\n   ```bash\r\n   git push origin release\u002Fv{VERSION}\r\n   ```\r\n\r\n4. Create a PR using the GitHub CLI:\r\n   ```bash\r\n   gh pr create \\\r\n     --title \"Release v{VERSION}\" \\\r\n     --body \"## Release v{VERSION}\r\n\r\n   ### Changes\r\n   {changelog entries for this version}\r\n\r\n   ### Checklist\r\n   - [ ] Version bumped in version.txt and extension.yaml\r\n   - [ ] CHANGELOG.md updated\r\n   - [ ] CI passes\r\n   - [ ] Ready to publish via 'Publish azd Extension' workflow\" \\\r\n     --base main \\\r\n     --head release\u002Fv{VERSION}\r\n   ```\r\n\r\nIf **no**:\r\n- Leave the changes uncommitted in the working tree\r\n- Inform the user they can review and commit manually\r\n\r\n## File Reference\r\n\r\n| File | Purpose | What Gets Updated |\r\n|------|---------|-------------------|\r\n| `version.txt` | Single source of version truth | New semver version string |\r\n| `extension.yaml` | azd extension manifest | `version:` field |\r\n| `CHANGELOG.md` | Human-readable change history | New version section with entries |\r\n\r\n## Important Notes\r\n\r\n- Always use **conventional commit** prefixes (`feat:`, `fix:`, `chore:`, `docs:`, `refactor:`) when interpreting git history\r\n- The changelog format must follow [Keep a Changelog](https:\u002F\u002Fkeepachangelog.com\u002Fen\u002F1.1.0\u002F)\r\n- Version numbering must follow [Semantic Versioning](https:\u002F\u002Fsemver.org\u002Fspec\u002Fv2.0.0.html)\r\n- The PR branch naming convention is `release\u002Fv{VERSION}`\r\n- After the PR is merged, the user should trigger the **Publish azd Extension** workflow (`azd-ext-release.yml`) to build, pack, and publish the extension\r\n","# azd Extension Publish\r\n\r\n> Automate version bumps, changelog updates, and PR creation for waza azd extension releases.\r\n\r\n## When to Use\r\n\r\n- Preparing a new release of the waza azd extension\r\n- Bumping the version number (major, minor, or patch)\r\n- Updating the changelog with changes since last release\r\n- Creating a release PR for review\r\n\r\n## Workflow\r\n\r\nFollow these steps **in order**. Ask the user for input at each decision point.\r\n\r\n### Step 1: Gather Changes and Update Changelog\r\n\r\nGet the current version from `version.txt` and `extension.yaml`, then collect commits since the last release:\r\n\r\n```bash\r\ncat version.txt\r\n\r\n# Find the latest azd extension version tags\r\ngit tag --list 'azd-ext-microsoft-azd-waza_*' --sort=-v:refname | head -5\r\n\r\n# Get commits since last azd extension tag\r\nlast_tag=$(git tag --list 'azd-ext-microsoft-azd-waza_*' --sort=-v:refname | head -1)\r\ngit log \"${last_tag}..HEAD\" --oneline --no-decorate\r\n```\r\n\r\nIf `version.txt` and `extension.yaml` differ, flag it to the user before proceeding.\r\n\r\nSummarize the changes grouped by type:\r\n- **Added** — `feat:` commits\r\n- **Fixed** — `fix:` commits\r\n- **Changed** — `refactor:`, `chore:`, `docs:` commits\r\n- **Removed** — any removal-related commits\r\n\r\nPresent the summary to the user for review.\r\n\r\nThen update `CHANGELOG.md`. The changelog follows [Keep a Changelog](https:\u002F\u002Fkeepachangelog.com\u002Fen\u002F1.1.0\u002F) format.\r\n\r\nPerform these updates (using a placeholder version `X.Y.Z` — the actual version is determined in Step 2):\r\n\r\n1. **Move Unreleased content**: Move any items currently under `## [Unreleased]` into a staging area. If `[Unreleased]` is empty, populate from the git log summary gathered above.\r\n\r\n2. **Populate from commits**: Prepare entries grouped under `### Added`, `### Fixed`, `### Changed` as appropriate based on the commits gathered above.\r\n\r\nHold these changelog entries — the new version section header and comparison links will be finalized after the version is determined in Step 2.\r\n\r\n### Step 2: Determine Version\r\n\r\nBased on the changes gathered in Step 1, **recommend** a version bump type using standard semver semantics:\r\n\r\n- **major** — Breaking changes, removals of public API (`feat!:`, `BREAKING CHANGE:`) → `(MAJOR+1).0.0`\r\n- **minor** — New features, backward compatible (`feat:`) → `MAJOR.(MINOR+1).0`\r\n- **patch** — Bug fixes, docs, refactors, chores (`fix:`, `docs:`, `refactor:`, `chore:`) → `MAJOR.MINOR.(PATCH+1)`\r\n\r\nPresent the recommendation with rationale (e.g., \"I see 3 `feat:` commits and no breaking changes — recommending a **minor** bump\").\r\n\r\n**ASK THE USER** to confirm the recommended bump or choose a different one.\r\n\r\nCompute the new version and confirm with the user before proceeding.\r\n\r\nThen finalize the changelog:\r\n\r\n1. **Create new version section**: Insert a new section below `## [Unreleased]` with today's date:\r\n   ```markdown\r\n   ## [X.Y.Z] - YYYY-MM-DD\r\n   ```\r\n\r\n2. **Add the prepared entries** from Step 1 under the new version section.\r\n\r\n3. **Update comparison links** at the bottom of the file:\r\n   ```markdown\r\n   [Unreleased]: https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza\u002Fcompare\u002Fazd-ext-microsoft-azd-waza_X.Y.Z...HEAD\r\n   [X.Y.Z]: https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza\u002Fcompare\u002Fazd-ext-microsoft-azd-waza_PREVIOUS...azd-ext-microsoft-azd-waza_X.Y.Z\r\n   ```\r\n\r\n4. **Clear the Unreleased section**: Leave `## [Unreleased]` with empty subsections or blank.\r\n\r\n### Step 3: Update Version Files\r\n\r\nUpdate these files with the new version:\r\n\r\n1. **`version.txt`** — Replace contents with new version string\r\n2. **`extension.yaml`** — Update the `version:` field\r\n\r\n### Step 4: Review Changes\r\n\r\nShow the user a summary of all changes made:\r\n- New version number\r\n- Files modified: `version.txt`, `extension.yaml`, `CHANGELOG.md`\r\n- Show the diff with `git diff`\r\n\r\n### Step 5: Ask About PR Creation\r\n\r\n**ASK THE USER**: Should I create a PR with these changes?\r\n\r\nIf **yes**:\r\n\r\n1. Create a feature branch:\r\n   ```bash\r\n   git checkout -b release\u002Fv{VERSION}\r\n   ```\r\n\r\n2. Stage and commit all changes:\r\n   ```bash\r\n   git add version.txt extension.yaml CHANGELOG.md\r\n   git commit -m \"chore: Prepare release v{VERSION}\"\r\n   ```\r\n\r\n3. Push the branch:\r\n   ```bash\r\n   git push origin release\u002Fv{VERSION}\r\n   ```\r\n\r\n4. Create a PR using the GitHub CLI:\r\n   ```bash\r\n   gh pr create \\\r\n     --title \"Release v{VERSION}\" \\\r\n     --body \"## Release v{VERSION}\r\n\r\n   ### Changes\r\n   {changelog entries for this version}\r\n\r\n   ### Checklist\r\n   - [ ] Version bumped in version.txt and extension.yaml\r\n   - [ ] CHANGELOG.md updated\r\n   - [ ] CI passes\r\n   - [ ] Ready to publish via 'Publish azd Extension' workflow\" \\\r\n     --base main \\\r\n     --head release\u002Fv{VERSION}\r\n   ```\r\n\r\nIf **no**:\r\n- Leave the changes uncommitted in the working tree\r\n- Inform the user they can review and commit manually\r\n\r\n## File Reference\r\n\r\n| File | Purpose | What Gets Updated |\r\n|------|---------|-------------------|\r\n| `version.txt` | Single source of version truth | New semver version string |\r\n| `extension.yaml` | azd extension manifest | `version:` field |\r\n| `CHANGELOG.md` | Human-readable change history | New version section with entries |\r\n\r\n## Important Notes\r\n\r\n- Always use **conventional commit** prefixes (`feat:`, `fix:`, `chore:`, `docs:`, `refactor:`) when interpreting git history\r\n- The changelog format must follow [Keep a Changelog](https:\u002F\u002Fkeepachangelog.com\u002Fen\u002F1.1.0\u002F)\r\n- Version numbering must follow [Semantic Versioning](https:\u002F\u002Fsemver.org\u002Fspec\u002Fv2.0.0.html)\r\n- The PR branch naming convention is `release\u002Fv{VERSION}`\r\n- After the PR is merged, the user should trigger the **Publish azd Extension** workflow (`azd-ext-release.yml`) to build, pack, and publish the extension\r\n",{"name":5,"metadata":50,"description":53},{"author":51,"version":52},"spboyer","1.0","Prepare and publish a new version of the waza azd extension.\nUSE FOR: \"publish extension\", \"release new version\", \"bump version\",\n\"prepare release\", \"update changelog\", \"azd publish\", \"new release\",\n\"version bump\", \"cut a release\".\nDO NOT USE FOR: running evals (use waza), writing skills (use skill-authoring),\nCI\u002FCD pipeline changes (edit workflow files directly).\n","main","116214a33b5e07766539f64c0ea21521467829bf",".github\u002Fskills\u002Fazd-publish",101,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza","https:\u002F\u002Fmicrosoft.github.io\u002Fwaza\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-15 04:18:35",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add microsoft\u002Fwaza --skill azd-publish",{"tool":70,"command":71},"bunx","bunx skills add microsoft\u002Fwaza --skill azd-publish",{"tool":73,"command":74},"pnpm","pnpm dlx skills add microsoft\u002Fwaza --skill azd-publish","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fazd-publish\u002FSKILL.md",true,[],[79,107,131,159,179,192],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":89,"publishedAt":45},"01M6X00A438VG96V20V1VMDHCM","waza-runner","Run evaluations on Agent Skills to measure their effectiveness. \nUSE FOR: \"run skill evals\", \"evaluate my skill\", \"test skill quality\", \n\"check skill triggers\", \"skill compliance check\", \"measure skill performance\",\n\"run evals on [skill-name]\", \"grade skill execution\".\nDO NOT USE FOR: writing skills (use skill-authoring), improving frontmatter \n(use sensei), or general testing unrelated to skills.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza\u002Fblob\u002Fmain\u002Fwaza-runner\u002FSKILL.md",[85,88],{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[90,91,92,93,94,95,33,96,97,30,26,98,99,100,101,102,103,104,36,105,106],"waza runner","runner","waza","frontmatter","run","triggers","my","general","unrelated","writing skills","my skill","sensei","Test Skill","run evals","performance","testing","authoring",{"skillNo":108,"name":92,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":114,"publishedAt":45},"01M6X003ZZKY5WQ5SWPAQ3MJMS","**WORKFLOW SKILL** - Evaluate AI agent skills using structured benchmarks with YAML specs, fixture isolation, and pluggable validators. USE FOR: run waza, waza help, run eval, run benchmark, evaluate skill, test agent, generate eval suite, init eval, compare results, score agent, agent evaluation, skill testing, cross-model comparison. DO NOT USE FOR: improving skill frontmatter (use waza dev), creating new skills from scratch (use skill-creator), token counting or budget checks (use waza tokens). INVOKES: Copilot SDK executor, mock engine, code\u002Fregex validators. FOR SINGLE OPERATIONS: use waza run directly for a single benchmark.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza\u002Fblob\u002Fmain\u002Fskills\u002Fwaza\u002FSKILL.md",[112,113],{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[92,94,115,116,117,118,119,120,121,122,123,124,125,126,127,44,128,105,129,27,130],"workflow skill","executor","fixture","eval","compare results","model","Evaluation","evaluate skill","code","eval suite","generate","copilot","init","ai agent","counting","skill-creator",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":146,"publishedAt":45},"01M6WZZZHCTPZ8YF9564J3QJVT","waza-interactive","Interactive workflow partner for creating, testing, and improving AI agent skills with waza. USE FOR: run my evals, check my skill, compare models, create eval suite, debug failing tests, is my skill ready, ship readiness, interpret results, improve score. DO NOT USE FOR: general coding, non-skill work, writing skill content (use skill-authoring), improving frontmatter only (use sensei).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza\u002Fblob\u002Fmain\u002Fskills\u002Fwaza-interactive\u002FSKILL.md",[137,138,143],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":144,"categoryName":145,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000036","内容创作者",[147,92,148,149,36,105,128,38,150,124,30,106,33,97,26,151,152,153,118,154,155,100,94,156,157,101,158,44],"waza interactive","interactive","tests","general coding","ready","only","failing","work","improve","create","debug","create eval",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":166,"publishedAt":45},"01M6WZZTQR955SVJ02J33DGQYK","code-explainer","Explains code snippets in plain English, breaking down what the code does step by step. Perfect for learning, code reviews, or documentation.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza\u002Fblob\u002Fmain\u002Fskills\u002Fcode-explainer\u002FSKILL.md",[165],{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},[167,168,123,169,170,171,30,172,173,174,175,176,177,178],"code explainer","explainer","learning","plain","down","reviews","step by step","english","snippets","what the","plain english","documentation",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":185,"publishedAt":45},"01M6WZZR27J4RE4J10M38ECM26","compatibility-skill","Read fixture status and report whether it is ready.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza\u002Fblob\u002Fmain\u002Finternal\u002Ftestdata\u002Fcompatibility\u002Fv1\u002FSKILL.md",[],[186,187,188,117,151,189,190,191],"compatibility skill","compatibility","it","read","report","status",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":198,"publishedAt":45},"01M6WZZMYWAKWE36WD4PHQK8V2","evidence-judge","Read a supplied report and summarize its recorded status and numeric items.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza\u002Fblob\u002Fmain\u002Fexamples\u002Fevidence-judge\u002FSKILL.md",[],[199,200,201,189,190,191,202],"evidence","evidence judge","judge","summarize"]