[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69B8R4MPE6HAYDV46VBB40J":3,"skill-same:01M69B8R4MPE6HAYDV46VBB40J":122},{"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":34,"publishedAt":59,"linkOnly":60,"markdownContent":61,"markdownBody":62,"frontMatter":63,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":67,"repositoryHtmlUrl":68,"repositoryHomepageUrl":69,"ownerHtmlUrl":70,"ownerBlogUrl":71,"ownerDescription":72,"updatedAt":73,"install":74,"resources":87},"01M69B8R4MPE6HAYDV46VBB40J","whatsnew",null,"Step-argument skill that formalizes writing an Aspire \"What's new in N.N\" release-notes page (src\u002Ffrontend\u002Fsrc\u002Fcontent\u002Fdocs\u002Fwhats-new\u002Faspire-N-N.mdx) as a repeatable lifecycle. Invoke as `\u002Fwhatsnew {modality}` where modality is one of: draft\u002Fscaffold (init), research, critique, validate, polish, review. USE FOR: start\u002Fscaffold a new what's-new page for a release, research a release's changes into a dossier and author the draft prose, critique a draft, fact-check\u002Fvalidate the diff, polish and run data ingestion, or sign off the PR. DO NOT USE FOR: general docs pages (use doc-writer), reviewing an arbitrary docs PR (use doc-pr-reviewer), or product-repo changes. ORCHESTRATES: doc-writer, doc-pr-reviewer, doc-tester, twoslash-validator, update-integrations, update-samples, container-images.","microsoft\u002Faspire.dev","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69B7HZWV2YNDYYCP5G712FG",203,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire.dev\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwhatsnew\u002FSKILL.md",[18,23,26,29],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[5,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58],"run","new","invoke","validator","argument","writer","images","ingestion","reviewer","critique","product","release-notes","update","frontend","pr","notes","aspire","scaffold","validate","init","research","docs","review","writing","2026-11-10 10:12:30",false,"---\nname: whatsnew\ndescription: \"Step-argument skill that formalizes writing an Aspire \\\"What's new in N.N\\\" release-notes page (src\u002Ffrontend\u002Fsrc\u002Fcontent\u002Fdocs\u002Fwhats-new\u002Faspire-N-N.mdx) as a repeatable lifecycle. Invoke as `\u002Fwhatsnew {modality}` where modality is one of: draft\u002Fscaffold (init), research, critique, validate, polish, review. USE FOR: start\u002Fscaffold a new what's-new page for a release, research a release's changes into a dossier and author the draft prose, critique a draft, fact-check\u002Fvalidate the diff, polish and run data ingestion, or sign off the PR. DO NOT USE FOR: general docs pages (use doc-writer), reviewing an arbitrary docs PR (use doc-pr-reviewer), or product-repo changes. ORCHESTRATES: doc-writer, doc-pr-reviewer, doc-tester, twoslash-validator, update-integrations, update-samples, container-images.\"\n---\n\n# What's-new release-notes skill\n\nFormalizes the previously ad-hoc process of writing an Aspire **\"What's new in\nAspire N.N\"** page as a single, step-argument skill with a repeatable lifecycle.\nInvoke it as `\u002Fwhatsnew {modality}` — the modality argument selects one phase:\n\n```\n{draft\u002Fscaffold} → {research} → {critique} → {validate} → {polish} → {review}\n   init\u002Fstructure   dossier+draft  self-review   fact-check   edits+data    sign-off\n```\n\nEach phase has a dedicated spec under [`references\u002F`](.\u002Freferences\u002F). This skill\n**orchestrates** existing skills — it does not duplicate them. `{research}` is the\nphase that **authors** the article body from its dossier; `{critique}`\u002F`{validate}`\nthen review and fact-check that draft, and `{polish}` finalizes it. Because\n`{polish}` edits content *after* `{validate}`, it must end with a **fresh\n`{validate}` pass** so nothing ships unchecked (see below).\n\n## Dispatch on the modality argument\n\nRead the argument, then follow the matching spec. `draft`, `scaffold`, and `init`\nare aliases for the same phase. If no argument is given, ask which phase to run (or\ninfer from context — e.g. a fresh release with no page → `draft`).\n\n| Modality | Alias | Purpose | Spec | Edits content? |\n|----------|-------|---------|------|----------------|\n| `draft` | `scaffold`, `init` | Stand up branch, draft PR, skeleton MDX, banner, sidebar, version constants. **Structure only.** | [`01-draft-scaffold.md`](.\u002Freferences\u002F01-draft-scaffold.md) | Skeleton only |\n| `research` | — | Enumerate every change into an impact-focused **dossier**, then **author the first-draft prose** into the MDX from it. | [`02-research.md`](.\u002Freferences\u002F02-research.md) | **Yes — drafts the body** |\n| `critique` | — | Content-quality **self-review** of draft vs dossier; severity-ranked findings. | [`03-critique.md`](.\u002Freferences\u002F03-critique.md) | **No — reports only** |\n| `validate` | — | **Ralph loop** with `doc-pr-reviewer` until 100% factual; samples\u002Flinks\u002Fassets. **No `bun run build`.** | [`04-validate.md`](.\u002Freferences\u002F04-validate.md) | Fixes only |\n| `polish` | — | Editorial pass + CI triage + diagnostics-author `@mentions` + **automated data ingestion**, then a **final `{validate}` pass**. | [`05-polish.md`](.\u002Freferences\u002F05-polish.md) | **Yes** |\n| `review` | — | Undraft PR, description, reviewers + `doc-tester` **blind** run of every in-article scenario. | [`06-review.md`](.\u002Freferences\u002F06-review.md) | No |\n\n## Supporting references\n\n- [`whats-new-template.mdx`](.\u002Freferences\u002Fwhats-new-template.mdx) — structure-only\n  skeleton the `draft` phase copies (scaffold tokens, `publishDate` frontmatter, and\n  the mandated section taxonomy).\n- [`writing-guidelines.md`](.\u002Freferences\u002Fwriting-guidelines.md) — humanized voice +\n  the maintainer content standards. Defers to `doc-writer` for canonical style.\n\n## Cross-cutting rules (apply to every phase)\n\n### Git \u002F branching \u002F PR\n- Release work happens on a **`release\u002F{N.N}` branch** in the repository.\n- Cut `release\u002F{N.N}` from the **latest default branch** (e.g. `main`) — fetch first so\n  you branch from an up-to-date base and avoid merge conflicts.\n- Iterate via a **draft PR** from `release\u002F{N.N}` into the repository's **default\n  branch**. Open it **after** the scaffold is committed (a branch with no commits\n  ahead of the default branch has no diff, so the PR can't be created); `{review}`\n  marks it ready for review.\n\n### Voice & quality (see `writing-guidelines.md` + `doc-writer`)\n- **Impact first, positives first, KISS.** No walls of text, no marketing fluff.\n- **Judicious `\u003CAside>`** — a spotlight, not a floodlight. Don't burn the reader's eyes.\n- **Content standards:** Deployment and Integrations are **separate** sections; a\n  distinct **\"New integrations\"** section for brand-new ones; a **\"Default container\n  image updates\"** section for tag bumps. The release-date badge + GitHub release-notes\n  link render **automatically** from `publishDate` + slug — never hand-place them.\n- **Resource artwork:** Every new release page must set `resourceImage` to newly\n  captured screenshots demonstrating a feature introduced in that release, with\n  matching `light`\u002F`dark` variants. Verify the running product version and capture\n  its actual UI; do not substitute generic dashboard artwork, an older release's\n  screenshots, or fabricated UI. Store the files in the release's assets folder\n  before adding their paths, and show them beside the feature in the article. The\n  resource directory discovers release pages and consumes this frontmatter\n  automatically; do not add a duplicate catalog entry. Verify the card's image\n  and release metadata in the resource-catalog tests and browser preview.\n\n### Safety \u002F mechanics\n- **Never run `bun run build` locally** — validate build-readiness by inspection.\n- Each modality is **idempotent** — safe to re-run; `critique`\u002F`validate` loop to\n  convergence.\n- **Re-validate after polish.** Any edit `{polish}` makes lands *after* the\n  `{validate}` gate, so `{polish}` must finish with a fresh `{validate}` pass and\n  `{review}` confirms it — the committed article never bypasses validation.\n- Prefer built-in tools over shell; Windows-friendly paths.\n\n## Key repository paths\n\n| What | Path |\n|------|------|\n| What's-new pages | `src\u002Ffrontend\u002Fsrc\u002Fcontent\u002Fdocs\u002Fwhats-new\u002Faspire-N-N.mdx` (JA under `...\u002Fja\u002Fwhats-new\u002F`) |\n| Version constants | `src\u002Ffrontend\u002Fconfig\u002Faspire-versions.mjs` (`currentAspireMajorMinorVersion`, `currentAspireVersion`, `currentAspireReleaseDate`, `currentAspirePreviewVersion`) |\n| Sidebar | `src\u002Ffrontend\u002Fconfig\u002Fsidebar\u002Fdocs.topics.ts` (What's-new `items`) |\n| Announcement banner | `banner:` frontmatter on `src\u002Ffrontend\u002Fsrc\u002Fcontent\u002Fdocs\u002Findex.mdx`, `src\u002Ffrontend\u002Fsrc\u002Fcontent\u002Fdocs\u002Fdocs.mdx`, `src\u002Ffrontend\u002Fsrc\u002Fcontent\u002Fdocs\u002Fcommunity\u002Findex.mdx`, and each `src\u002Ffrontend\u002Fsrc\u002Fcontent\u002Fdocs\u002F{locale}\u002Findex.mdx` (+ `...\u002Fja\u002Fdocs.mdx`); rendered by `src\u002Ffrontend\u002Fsrc\u002Fcomponents\u002Fstarlight\u002FBanner.astro` |\n| Assets | `src\u002Ffrontend\u002Fsrc\u002Fassets\u002Fwhats-new\u002Faspire-\u003Cversion>\u002F` |\n| Container image data | `src\u002Ffrontend\u002Fsrc\u002Fdata\u002Fcontainer-images.json` |\n| Diagnostics articles | `src\u002Ffrontend\u002Fsrc\u002Fcontent\u002Fdocs\u002Fdiagnostics\u002Faspire\u003Carea>\u003CNNN>.mdx` → `\u002Fdiagnostics\u002Faspire\u003CNNN>\u002F` |\n| Data ingestion | `src\u002Ffrontend\u002Fscripts\u002Fupdate-integration-data.ps1` (`bun run update:all`) |\n\n## Orchestrated skills\n\n`doc-writer` (voice\u002Fstyle) · `doc-pr-reviewer` (validate loop) · `doc-tester` (review\nblind run) · `twoslash-validator` (TS samples) · `update-integrations` \u002F\n`update-samples` \u002F `container-images` (polish data ingestion).\n","# What's-new release-notes skill\n\nFormalizes the previously ad-hoc process of writing an Aspire **\"What's new in\nAspire N.N\"** page as a single, step-argument skill with a repeatable lifecycle.\nInvoke it as `\u002Fwhatsnew {modality}` — the modality argument selects one phase:\n\n```\n{draft\u002Fscaffold} → {research} → {critique} → {validate} → {polish} → {review}\n   init\u002Fstructure   dossier+draft  self-review   fact-check   edits+data    sign-off\n```\n\nEach phase has a dedicated spec under [`references\u002F`](.\u002Freferences\u002F). This skill\n**orchestrates** existing skills — it does not duplicate them. `{research}` is the\nphase that **authors** the article body from its dossier; `{critique}`\u002F`{validate}`\nthen review and fact-check that draft, and `{polish}` finalizes it. Because\n`{polish}` edits content *after* `{validate}`, it must end with a **fresh\n`{validate}` pass** so nothing ships unchecked (see below).\n\n## Dispatch on the modality argument\n\nRead the argument, then follow the matching spec. `draft`, `scaffold`, and `init`\nare aliases for the same phase. If no argument is given, ask which phase to run (or\ninfer from context — e.g. a fresh release with no page → `draft`).\n\n| Modality | Alias | Purpose | Spec | Edits content? |\n|----------|-------|---------|------|----------------|\n| `draft` | `scaffold`, `init` | Stand up branch, draft PR, skeleton MDX, banner, sidebar, version constants. **Structure only.** | [`01-draft-scaffold.md`](.\u002Freferences\u002F01-draft-scaffold.md) | Skeleton only |\n| `research` | — | Enumerate every change into an impact-focused **dossier**, then **author the first-draft prose** into the MDX from it. | [`02-research.md`](.\u002Freferences\u002F02-research.md) | **Yes — drafts the body** |\n| `critique` | — | Content-quality **self-review** of draft vs dossier; severity-ranked findings. | [`03-critique.md`](.\u002Freferences\u002F03-critique.md) | **No — reports only** |\n| `validate` | — | **Ralph loop** with `doc-pr-reviewer` until 100% factual; samples\u002Flinks\u002Fassets. **No `bun run build`.** | [`04-validate.md`](.\u002Freferences\u002F04-validate.md) | Fixes only |\n| `polish` | — | Editorial pass + CI triage + diagnostics-author `@mentions` + **automated data ingestion**, then a **final `{validate}` pass**. | [`05-polish.md`](.\u002Freferences\u002F05-polish.md) | **Yes** |\n| `review` | — | Undraft PR, description, reviewers + `doc-tester` **blind** run of every in-article scenario. | [`06-review.md`](.\u002Freferences\u002F06-review.md) | No |\n\n## Supporting references\n\n- [`whats-new-template.mdx`](.\u002Freferences\u002Fwhats-new-template.mdx) — structure-only\n  skeleton the `draft` phase copies (scaffold tokens, `publishDate` frontmatter, and\n  the mandated section taxonomy).\n- [`writing-guidelines.md`](.\u002Freferences\u002Fwriting-guidelines.md) — humanized voice +\n  the maintainer content standards. Defers to `doc-writer` for canonical style.\n\n## Cross-cutting rules (apply to every phase)\n\n### Git \u002F branching \u002F PR\n- Release work happens on a **`release\u002F{N.N}` branch** in the repository.\n- Cut `release\u002F{N.N}` from the **latest default branch** (e.g. `main`) — fetch first so\n  you branch from an up-to-date base and avoid merge conflicts.\n- Iterate via a **draft PR** from `release\u002F{N.N}` into the repository's **default\n  branch**. Open it **after** the scaffold is committed (a branch with no commits\n  ahead of the default branch has no diff, so the PR can't be created); `{review}`\n  marks it ready for review.\n\n### Voice & quality (see `writing-guidelines.md` + `doc-writer`)\n- **Impact first, positives first, KISS.** No walls of text, no marketing fluff.\n- **Judicious `\u003CAside>`** — a spotlight, not a floodlight. Don't burn the reader's eyes.\n- **Content standards:** Deployment and Integrations are **separate** sections; a\n  distinct **\"New integrations\"** section for brand-new ones; a **\"Default container\n  image updates\"** section for tag bumps. The release-date badge + GitHub release-notes\n  link render **automatically** from `publishDate` + slug — never hand-place them.\n- **Resource artwork:** Every new release page must set `resourceImage` to newly\n  captured screenshots demonstrating a feature introduced in that release, with\n  matching `light`\u002F`dark` variants. Verify the running product version and capture\n  its actual UI; do not substitute generic dashboard artwork, an older release's\n  screenshots, or fabricated UI. Store the files in the release's assets folder\n  before adding their paths, and show them beside the feature in the article. The\n  resource directory discovers release pages and consumes this frontmatter\n  automatically; do not add a duplicate catalog entry. Verify the card's image\n  and release metadata in the resource-catalog tests and browser preview.\n\n### Safety \u002F mechanics\n- **Never run `bun run build` locally** — validate build-readiness by inspection.\n- Each modality is **idempotent** — safe to re-run; `critique`\u002F`validate` loop to\n  convergence.\n- **Re-validate after polish.** Any edit `{polish}` makes lands *after* the\n  `{validate}` gate, so `{polish}` must finish with a fresh `{validate}` pass and\n  `{review}` confirms it — the committed article never bypasses validation.\n- Prefer built-in tools over shell; Windows-friendly paths.\n\n## Key repository paths\n\n| What | Path |\n|------|------|\n| What's-new pages | `src\u002Ffrontend\u002Fsrc\u002Fcontent\u002Fdocs\u002Fwhats-new\u002Faspire-N-N.mdx` (JA under `...\u002Fja\u002Fwhats-new\u002F`) |\n| Version constants | `src\u002Ffrontend\u002Fconfig\u002Faspire-versions.mjs` (`currentAspireMajorMinorVersion`, `currentAspireVersion`, `currentAspireReleaseDate`, `currentAspirePreviewVersion`) |\n| Sidebar | `src\u002Ffrontend\u002Fconfig\u002Fsidebar\u002Fdocs.topics.ts` (What's-new `items`) |\n| Announcement banner | `banner:` frontmatter on `src\u002Ffrontend\u002Fsrc\u002Fcontent\u002Fdocs\u002Findex.mdx`, `src\u002Ffrontend\u002Fsrc\u002Fcontent\u002Fdocs\u002Fdocs.mdx`, `src\u002Ffrontend\u002Fsrc\u002Fcontent\u002Fdocs\u002Fcommunity\u002Findex.mdx`, and each `src\u002Ffrontend\u002Fsrc\u002Fcontent\u002Fdocs\u002F{locale}\u002Findex.mdx` (+ `...\u002Fja\u002Fdocs.mdx`); rendered by `src\u002Ffrontend\u002Fsrc\u002Fcomponents\u002Fstarlight\u002FBanner.astro` |\n| Assets | `src\u002Ffrontend\u002Fsrc\u002Fassets\u002Fwhats-new\u002Faspire-\u003Cversion>\u002F` |\n| Container image data | `src\u002Ffrontend\u002Fsrc\u002Fdata\u002Fcontainer-images.json` |\n| Diagnostics articles | `src\u002Ffrontend\u002Fsrc\u002Fcontent\u002Fdocs\u002Fdiagnostics\u002Faspire\u003Carea>\u003CNNN>.mdx` → `\u002Fdiagnostics\u002Faspire\u003CNNN>\u002F` |\n| Data ingestion | `src\u002Ffrontend\u002Fscripts\u002Fupdate-integration-data.ps1` (`bun run update:all`) |\n\n## Orchestrated skills\n\n`doc-writer` (voice\u002Fstyle) · `doc-pr-reviewer` (validate loop) · `doc-tester` (review\nblind run) · `twoslash-validator` (TS samples) · `update-integrations` \u002F\n`update-samples` \u002F `container-images` (polish data ingestion).\n",{"name":5,"description":7},"main","f05f5561b1b858344124cd848ff06469627d7e6e",".agents\u002Fskills\u002Fwhatsnew",99,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire.dev","https:\u002F\u002Faspire.dev","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-12 03:13:45",{"source":8,"skillName":5,"commands":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add microsoft\u002Faspire.dev --skill whatsnew",{"tool":80,"command":81},"bunx","bunx skills add microsoft\u002Faspire.dev --skill whatsnew",{"tool":83,"command":84},"pnpm","pnpm dlx skills add microsoft\u002Faspire.dev --skill whatsnew","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire.dev\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwhatsnew\u002FSKILL.md",true,[88,94,98,102,106,110,114,118],{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002F01-draft-scaffold.md","REFERENCE","参考文档",5828,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire.dev\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwhatsnew\u002Freferences\u002F01-draft-scaffold.md",{"path":95,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002F02-research.md",5344,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire.dev\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwhatsnew\u002Freferences\u002F02-research.md",{"path":99,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002F03-critique.md",2852,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire.dev\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwhatsnew\u002Freferences\u002F03-critique.md",{"path":103,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002F04-validate.md",3042,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire.dev\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwhatsnew\u002Freferences\u002F04-validate.md",{"path":107,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002F05-polish.md",4266,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire.dev\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwhatsnew\u002Freferences\u002F05-polish.md",{"path":111,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002F06-review.md",3141,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire.dev\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwhatsnew\u002Freferences\u002F06-review.md",{"path":115,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002Fwhats-new-template.mdx",8417,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire.dev\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwhatsnew\u002Freferences\u002Fwhats-new-template.mdx",{"path":119,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Fwriting-guidelines.md",7095,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire.dev\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwhatsnew\u002Freferences\u002Fwriting-guidelines.md",[123,150,171,187,206,230],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":132,"publishedAt":59},"01M69B8W7K62DJP002TEBRZDTC","getting-started-with-aspire","Use this skill when a developer asks how to begin using Aspire — installing the Aspire CLI, creating a new Aspire app, running it locally, or finding the authoritative docs, integration catalog, or API reference on aspire.dev. Use it for questions like \"how do I install aspire?\", \"how do I create a new aspire app?\", \"how do I run my aspire app?\", or \"where is the documentation for aspire?\". Do not use it for operating an existing Aspire AppHost (use the official `aspire` skill at github.com\u002Fmicrosoft\u002Faspire\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Faspire), authoring AppHost code, or adding integrations to an existing app.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire.dev\u002Fblob\u002Fmain\u002Fsrc\u002Ffrontend\u002Fpublic\u002F.well-known\u002Fagent-skills\u002Fgetting-started-with-aspire\u002FSKILL.md",[129],{"categoryNo":130,"categoryName":131,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000030","开发工程师",[51,133,134,135,136,56,137,9,138,139,140,35,141,142,143,144,64,145,146,147,148,149,36],"getting started with aspire","getting started","with","cli","github","official","documentation","create","code","api","how","install","app","how to","operating","at","when",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":159,"publishedAt":59},"01M69B8ND3PR8M9EEKC2TQ94G2","update-samples","Update the samples data file by fetching sample metadata from the microsoft\u002Faspire-samples GitHub repository. Use when adding new samples, refreshing sample data, or ensuring samples.json stays in sync with the upstream repo.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire.dev\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fupdate-samples\u002FSKILL.md",[156],{"categoryNo":157,"categoryName":158,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000033","数据分析师",[160,47,137,9,161,51,162,163,164,165,166,167,168,169,170,135,149,36],"update samples","sync","metadata","file","repository","data","json","repo","use","upstream","sample",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":178,"publishedAt":59},"01M69B8JC3YJKYZFC0BX9N47SC","update-integrations","Update integration documentation links and API reference data by synchronizing NuGet package names with their documentation URLs and generating per-package API schemas. Use when adding new integrations, refreshing package data, ensuring integration-docs.json stays in sync with aspire-integrations.json, or regenerating API reference JSON files.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire.dev\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fupdate-integrations\u002FSKILL.md",[177],{"categoryNo":157,"categoryName":158,"taxonomyType":32,"taxonomyTypeDesc":33},[179,47,180,56,161,51,139,181,182,183,165,142,166,168,184,185,135,186,149,36],"update integrations","integrations","nuget","package","integration","reference","files","links",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":193,"publishedAt":59},"01M69B8F4MQJEG381FDZZ32AW4","twoslash-validator","Validate and fix two-slash TypeScript examples for aspire.dev. Use when adding or editing `twoslash` code fences, TypeScript AppHost samples, generated TypeScript API data, or failures from `bun run test:unit:twoslash-blocks`.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire.dev\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftwoslash-validator\u002FSKILL.md",[],[194,38,195,196,53,51,35,141,197,198,142,199,200,201,168,202,203,204,205,149],"twoslash validator","typescript","test","dev","examples","editing","generated","fix","bun","unit","blocks","for",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":215,"publishedAt":59},"01M69B8CEPDW2FFXZ89YE4F4T3","playwright-cli","Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire.dev\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fplaywright-cli\u002FSKILL.md",[212],{"categoryNo":213,"categoryName":214,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[136,216,217,218,219,196,220,221,165,222,168,223,224,225,226,227,228,135,205,229,149],"playwright","playwright cli","testing","screenshots","web","browser","applications","take","test web","forms","pages","form","information","navigate",{"skillNo":231,"name":232,"nameZh":6,"description":233,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":234,"categories":235,"keywords":239,"publishedAt":59},"01M69B89R72XJT8JP8JZRGCV0C","hex1b","CLI tool for automating any terminal application — TUI apps, shells, CLI tools, REPLs, and more. Use when you need to launch a process in a virtual terminal, capture its screen output, inject keystrokes or mouse input, take screenshots, record sessions, or assert on what's visible.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire.dev\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhex1b\u002FSKILL.md",[236],{"categoryNo":237,"categoryName":238,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[232,219,136,240,241,242,243,244,245,168,223,246,247,248,249,250,251,252,253,205,149],"terminal","launch","sessions","Tools","tool","virtual","record","apps","screen","input","cli tool","output","you","more"]