[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WZGSCH9M9B2PY3V0KK49P9":3,"skill-same:01M6WZGSCH9M9B2PY3V0KK49P9":67},{"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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6WZGSCH9M9B2PY3V0KK49P9","wardgeneral",null,"Guide the cumulative Ward General Hospital Azure SQL Hyperscale demo: provision\u002Fschema, architecture, .NET 10 Blazor app, SQL AI, agentic shift handoff, security\u002FRLS, observability, failover\u002FPITR\u002Fgeo, scaling, and tuning. Use for examples\u002Fwardgeneral.","microsoft\u002Fbobsql","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M6WZDXPPPAZ6RKJZM2CQYNW8",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fbobsql\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwardgeneral\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"schema","shift handoff","for","failover","ward","rls","app","scaling","geo","general","agentic","use","examples","demo","observability","blazor","azure","sql","azure sql","architecture","2026-11-10 10:12:30",false,"---\nname: wardgeneral\ndescription: \"Guide the cumulative Ward General Hospital Azure SQL Hyperscale demo: provision\u002Fschema, architecture, .NET 10 Blazor app, SQL AI, agentic shift handoff, security\u002FRLS, observability, failover\u002FPITR\u002Fgeo, scaling, and tuning. Use for examples\u002Fwardgeneral.\"\n---\n\n# Ward General cumulative application\n\n## Procedure\n\n1. Start with the [collection map](..\u002F..\u002F..\u002Fexamples\u002Fwardgeneral\u002Freadme.md).\n   Identify the requested area and read its README, scripts, and prerequisites.\n   The database and application carry forward; do not scaffold a replacement.\n2. Verify subscription, identity, target database\u002Freplicas, PowerShell\u002FAzure CLI\n   tooling, and prior-stage readiness. The app requires .NET 10 and lives in\n   [first-app\u002Fsrc](..\u002F..\u002F..\u002Fexamples\u002Fwardgeneral\u002Ffirst-app\u002Fsrc\u002Freadme.md).\n3. If setup is missing, follow Getting Started's reviewed provisioning,\n   replica, schema, seed, and verification stages. Get approval for billable\n   resources, role\u002Ffirewall changes, database writes, or tool installation.\n4. For application or AI work, preserve the shared data\u002Fretry layer, Entra\n   authentication, replica routing, and documented feature flags. Enable AI\n   features only after their SQL\u002Fmodels\u002FDAB prerequisites are verified.\n5. Distinguish observation from mutation. Architecture\u002Fobservability evidence\n   does not authorize tuning, scaling, failover, recovery, geo-replication,\n   or security-policy changes. Use the owning area's preview and approval gates.\n6. Verify the requested outcome with that area's SQL, application, plan,\n   retry, audit, or resource evidence. Treat previous validation dates and\n   captured results as historical, not certification of the current deployment.\n7. End workload\u002Fprobe processes and follow only the approved, area-owned\n   cleanup. Never delete the shared database as routine per-area cleanup.\n\n## Scope and safety\n\nUse synthetic data only. Preserve the runtime shift-handoff skill's grounding\nand save-approval requirements; it is not the same as this workspace skill.\nInherited references to optional granular skills\u002Ffigures may not be bundled:\nuse the actual area scripts and report missing prerequisites explicitly.\nFollow [secret checks](..\u002F..\u002F..\u002FSECRET-SCANNING.md) before publishing.\n","# Ward General cumulative application\n\n## Procedure\n\n1. Start with the [collection map](..\u002F..\u002F..\u002Fexamples\u002Fwardgeneral\u002Freadme.md).\n   Identify the requested area and read its README, scripts, and prerequisites.\n   The database and application carry forward; do not scaffold a replacement.\n2. Verify subscription, identity, target database\u002Freplicas, PowerShell\u002FAzure CLI\n   tooling, and prior-stage readiness. The app requires .NET 10 and lives in\n   [first-app\u002Fsrc](..\u002F..\u002F..\u002Fexamples\u002Fwardgeneral\u002Ffirst-app\u002Fsrc\u002Freadme.md).\n3. If setup is missing, follow Getting Started's reviewed provisioning,\n   replica, schema, seed, and verification stages. Get approval for billable\n   resources, role\u002Ffirewall changes, database writes, or tool installation.\n4. For application or AI work, preserve the shared data\u002Fretry layer, Entra\n   authentication, replica routing, and documented feature flags. Enable AI\n   features only after their SQL\u002Fmodels\u002FDAB prerequisites are verified.\n5. Distinguish observation from mutation. Architecture\u002Fobservability evidence\n   does not authorize tuning, scaling, failover, recovery, geo-replication,\n   or security-policy changes. Use the owning area's preview and approval gates.\n6. Verify the requested outcome with that area's SQL, application, plan,\n   retry, audit, or resource evidence. Treat previous validation dates and\n   captured results as historical, not certification of the current deployment.\n7. End workload\u002Fprobe processes and follow only the approved, area-owned\n   cleanup. Never delete the shared database as routine per-area cleanup.\n\n## Scope and safety\n\nUse synthetic data only. Preserve the runtime shift-handoff skill's grounding\nand save-approval requirements; it is not the same as this workspace skill.\nInherited references to optional granular skills\u002Ffigures may not be bundled:\nuse the actual area scripts and report missing prerequisites explicitly.\nFollow [secret checks](..\u002F..\u002F..\u002FSECRET-SCANNING.md) before publishing.\n",{"name":5,"description":7},"main","102b51b6a889f75986729e25e6eb0901ec47e49d",".github\u002Fskills\u002Fwardgeneral",0,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fbobsql","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-11 02:50:07",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add microsoft\u002Fbobsql --skill wardgeneral",{"tool":59,"command":60},"bunx","bunx skills add microsoft\u002Fbobsql --skill wardgeneral",{"tool":62,"command":63},"pnpm","pnpm dlx skills add microsoft\u002Fbobsql --skill wardgeneral","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fbobsql\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwardgeneral\u002FSKILL.md",true,[],[68,101,116,142,160,176],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":84,"publishedAt":39},"01M711MN5XCC61F334RFT6GH1X","sql-versioning-apps","Launch, run, review, rehearse, test, or update the local SQL versioning click-through apps in examples\u002Fsqlversioning\u002Fapps. Use when the user says run the app, start the app, open the app, demo apps, browser demos, SQL versioning visuals, or asks about the Cowboys-themed demo pages. In this repository, running the app means opening a NEW normal external browser window, not the VS Code integrated browser.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fbobsql\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsql-versioning-apps\u002FSKILL.md",[74,79],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[85,86,36,87,88,89,32,90,91,92,30,93,94,95,96,97,98,99,25,100],"sql versioning apps","sql versioning","versioning","apps","normal","review","code","when","visuals","new","open","pages","local","click","integrated browser","running",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":39},"01M6WZHGWY9YNT1JPKMZ5HDAKK","shift-handoff","Find the patients who most need a shift handoff, and prepare a structured SBAR handoff for one named patient — grounded entirely in that patient's live chart — for the clinician to review and save.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fbobsql\u002Fblob\u002Fmain\u002Fexamples\u002Fwardgeneral\u002Ffirst-app\u002Fsrc\u002FWardGeneral.Agent\u002Fskills\u002Fshift-handoff\u002FSKILL.md",[],[108,20,21,109,110,111,112,113,90,114,115],"handoff","find","prepare","patient","save","structured","live","chart",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":127,"publishedAt":39},"01M6WZH8DW00ZYSDTQS7TVTR9Z","nvidianim","NVIDIA NIM on AKS with GPU — vector embeddings and chat completions from SQL Server 2025 T-SQL using GPU-accelerated inference. Use when: deploying NIM containers on AKS, creating AKS GPU node pools, testing NIM endpoints, creating external models for NIM embeddings, Azure Local edge AI pattern, working in nvidianim\u002F.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fbobsql\u002Fblob\u002Fmain\u002Fexamples\u002Fsqlserver2025\u002Fzavahealth\u002Fzavahospital\u002Fnvidianim\u002FSKILL.md",[122,125,126],{"categoryNo":123,"categoryName":124,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},[118,128,129,130,131,132,133,134,92,135,30,136,137,35,97,138,139,140,21,141],"nvidia nim","endpoints","with","server","gpu","chat","azure local","edge ai","edge","2025","testing","NVIDIA","containers","vector",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":150,"publishedAt":39},"01M6WZGZ3DCQG71VFVWXWGSEQT","zavahospital","ZavaHospital – AI-powered inpatient clinical assistant using SQL Server 2025 vector search + NVIDIA NIM on AKS. Use when: deploying zavahospital scripts, building encounter embeddings, running vector search procs, generating clinical recommendations via NIM chat, creating doctor notes search, working in zavahealth\u002Fsqlserver2025\u002Fzavahospital\u002F.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fbobsql\u002Fblob\u002Fmain\u002Fexamples\u002Fsqlserver2025\u002Fzavahealth\u002Fzavahospital\u002FSKILL.md",[148,149],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},[144,133,151,36,152,153,128,154,155,131,156,92,30,157,137,141,158,139,159,100],"scripts","aks","recommendations","via","procs","notes","clinical","search","doctor",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":39},"01M6WZGKJSGCCKEZRM8CAR0JSW","waits-latches-spinlocks","Investigate SQL Server waits, scheduler yield, buffer latches, LOCK_HASH spinlocks, and Azure SQL log governance. Use when working with examples\u002Finsidewaitslatchesspinlocks and its debugwaits, latches, spinlocks, or loggovernance areas.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fbobsql\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwaits-latches-spinlocks\u002FSKILL.md",[],[167,130,30,168,35,169,170,36,171,172,37,131,173,92,31,174,175],"waits latches spinlocks","buffer","scheduler","sql server","governance","yield","investigate","lock","log",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":39},"01M6WZGENG8RABQ7RAXKJ0K2Z7","waits-latches-spinlocks-workshop","Guide the numbered Inside Waits, Latches, and Spinlocks workshop: WinDbg basics, blocking, scheduler yield, preemptive waits, threadpool exhaustion, log governance, latches, and spinlocks. Use for examples\u002Finsidewaitslatchesspinlocks_workshop.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fbobsql\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwaits-latches-spinlocks-workshop\u002FSKILL.md",[],[183,167,169,175,184,185,21,171,30,172,31],"waits latches spinlocks workshop","guide","basics"]