[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69AFQ6JG3P8QX6D6KA474DS":3,"skill-same:01M69AFQ6JG3P8QX6D6KA474DS":58},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M69AFQ6JG3P8QX6D6KA474DS","run-keynote-demo-1",null,"Prepare, validate, rehearse, or troubleshoot SQLCon EU 2026 Keynote Demo 1, Caldova Regional Care on Azure Local. Use when running the Demo 1 setup, checking SQL Server 2025 and Foundry Local, validating the Azure Local gateway, starting the transfer-center app, or guiding the locked presenter flow.","microsoft\u002Fsqlcon-eu-2026-demos","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69AFC8P5962CJBG1RDAKA7Q",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsqlcon-eu-2026-demos\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Frun-keynote-demo-1\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"run keynote demo 1","troubleshoot","foundry","foundry local","validate","azure local","prepare","setup","sql","sql server","2026-11-10 10:12:30",false,"---\nname: run-keynote-demo-1\ndescription: \"Prepare, validate, rehearse, or troubleshoot SQLCon EU 2026 Keynote Demo 1, Caldova Regional Care on Azure Local. Use when running the Demo 1 setup, checking SQL Server 2025 and Foundry Local, validating the Azure Local gateway, starting the transfer-center app, or guiding the locked presenter flow.\"\nargument-hint: \"Mode: prepare, preflight, rehearse, or troubleshoot\"\n---\n\n# Run Keynote Demo 1\n\nGuide the user through the existing Caldova Regional Care demo. Treat the\n[package README](..\u002F..\u002F..\u002Fdemo1-azure-local\u002FREADME.md) and\n[demo runbook](..\u002F..\u002F..\u002Fdemo1-azure-local\u002FDEMO-RUNBOOK.md) as the sources of\ntruth. Use repository scripts as written; do not recreate their logic with\nad hoc commands.\n\n## Safety Rules\n\n- Never display or read into chat the kubeconfig, Kubernetes API key, database\n  scoped credential secret, database master-key password, or a literal key from\n  `chatLanguageModels.json`.\n- Never retrieve a Kubernetes Secret directly for inspection. Only the existing\n  setup and database wrappers may consume it.\n- Do not provision, restart, scale, or modify Azure Local, AKS Arc, Foundry\n  Local, the model deployment, or portal resources.\n- Do not bypass TLS validation or add `--insecure`.\n- Ask for explicit confirmation before running an elevated setup, restarting\n  SQL Server, initializing the database, invoking the live model, or generating\n  a live receiving briefing.\n- Never request a secret through chat. If a terminal prompts for one, tell the\n  user to enter it directly in the terminal.\n\n## Select a Mode\n\nInfer the mode from the request. If it is unclear, ask the user to choose:\n\n- `prepare`: configure a demo VM and database using existing infrastructure.\n- `preflight`: perform non-destructive readiness checks before presenting.\n- `rehearse`: guide the locked presentation sequence one beat at a time.\n- `troubleshoot`: diagnose one failed gate without broad environment changes.\n\n## Prepare\n\n1. Confirm the user is on the intended Windows demo VM and read\n   [setup guidance](..\u002F..\u002F..\u002Fdemo1-azure-local\u002Fsetup\u002FREADME.md).\n2. Check, without printing sensitive contents:\n   - PowerShell is elevated before setup.\n   - `C:\\setup\\SJ-SQLAI-admin.kubeconfig` exists, or record the alternate path.\n   - SQL Server 2025 is running.\n   - `az`, `kubectl`, `kubelogin`, `curl.exe`, `sqlcmd`, and the .NET 10 SDK are\n     available.\n3. Explain that setup imports a root certificate and restarts SQL Server. After\n   explicit confirmation, run from an elevated PowerShell terminal:\n\n   ```powershell\n   Set-Location C:\\setup\n   Set-ExecutionPolicy -Scope Process RemoteSigned\n   .\\Setup.ps1\n   ```\n\n   Pass documented overrides only when the user supplied them.\n4. Require exit code 0 and `Setup completed successfully.`\n5. Ask before invoking the live model. If approved, run `C:\\setup\\test.ps1` and\n   require trusted HTTPS plus HTTP 200 through SQL Server. A successful direct\n   `curl` call is not sufficient.\n6. From `demo1-azure-local`, determine whether `CaldovaRegionalCare` already\n   exists. Use `-InitializeDatabase` only for an absent database and only after\n   explicit confirmation:\n\n   ```powershell\n   .\\database\\Setup-CaldovaDatabase.ps1 -InitializeDatabase\n   ```\n\n   For an existing database, run the repeat-safe update without that switch.\n7. Run the live AI validation only after separate confirmation:\n\n   ```powershell\n   .\\database\\Setup-CaldovaDatabase.ps1 -TestFoundryAi\n   ```\n\n8. Build the application. Start `app\\run.ps1` as a long-running process only\n   when the user asks to launch it.\n\n## Preflight\n\nPerform checks without repairing or provisioning:\n\n1. Confirm the application responds at `http:\u002F\u002Flocalhost:5099`.\n2. Confirm `\u002Fapi\u002Fhealth` reports `Healthy` for `CaldovaRegionalCare`.\n3. Confirm the MSSQL extension can connect to `localhost` and database\n   `CaldovaRegionalCare`.\n4. Confirm the Azure portal is already signed in and the Azure Local VM, AKS\n   cluster, and Azure Virtual Desktop resources are ready to show.\n5. Confirm Phi-3.5 Mini appears in the VS Code model picker. Do not send a\n   clinical prompt.\n6. Report each gate as `PASS`, `FAIL`, or `NOT CHECKED`. Stop on a failed gate\n   and offer the smallest relevant repair from the documented scripts.\n\n## Rehearse\n\nFollow the runbook's locked order exactly:\n\n1. Transfer Center application.\n2. Azure portal: Azure Local VM, AKS, and Azure Virtual Desktop.\n3. VS Code MSSQL connection and ordered database scripts.\n4. Native RegEx extraction.\n5. Approved `ai.Skill` row.\n6. Transfer-skill procedure, JSON payload, and\n   `sys.sp_invoke_external_rest_endpoint`.\n7. Phi-3.5 Mini in VS Code Chat.\n\nFor each beat, present only its **Say**, **Show**, and **Land** guidance, then\nwait for the user to continue. Do not execute setup or repair commands during a\nrehearsal. Do not expose credential rows when showing endpoint metadata.\n\n## Troubleshoot\n\n- Start from the failed gate and its exact error.\n- Read the owning script before proposing a change.\n- Prefer rerunning a documented validation over changing infrastructure.\n- Do not use `Connect-AksArc.ps1` unless direct kubeconfig access failed and the\n  user explicitly asks to troubleshoot Arc Cluster Connect.\n- End with the failed command, the evidence found, and the next documented\n  action.\n\n## Completion Report\n\nReport the selected mode, checks performed, commands run, gates passed, and any\nremaining manual step. Never include secret values in the report.","# Run Keynote Demo 1\n\nGuide the user through the existing Caldova Regional Care demo. Treat the\n[package README](..\u002F..\u002F..\u002Fdemo1-azure-local\u002FREADME.md) and\n[demo runbook](..\u002F..\u002F..\u002Fdemo1-azure-local\u002FDEMO-RUNBOOK.md) as the sources of\ntruth. Use repository scripts as written; do not recreate their logic with\nad hoc commands.\n\n## Safety Rules\n\n- Never display or read into chat the kubeconfig, Kubernetes API key, database\n  scoped credential secret, database master-key password, or a literal key from\n  `chatLanguageModels.json`.\n- Never retrieve a Kubernetes Secret directly for inspection. Only the existing\n  setup and database wrappers may consume it.\n- Do not provision, restart, scale, or modify Azure Local, AKS Arc, Foundry\n  Local, the model deployment, or portal resources.\n- Do not bypass TLS validation or add `--insecure`.\n- Ask for explicit confirmation before running an elevated setup, restarting\n  SQL Server, initializing the database, invoking the live model, or generating\n  a live receiving briefing.\n- Never request a secret through chat. If a terminal prompts for one, tell the\n  user to enter it directly in the terminal.\n\n## Select a Mode\n\nInfer the mode from the request. If it is unclear, ask the user to choose:\n\n- `prepare`: configure a demo VM and database using existing infrastructure.\n- `preflight`: perform non-destructive readiness checks before presenting.\n- `rehearse`: guide the locked presentation sequence one beat at a time.\n- `troubleshoot`: diagnose one failed gate without broad environment changes.\n\n## Prepare\n\n1. Confirm the user is on the intended Windows demo VM and read\n   [setup guidance](..\u002F..\u002F..\u002Fdemo1-azure-local\u002Fsetup\u002FREADME.md).\n2. Check, without printing sensitive contents:\n   - PowerShell is elevated before setup.\n   - `C:\\setup\\SJ-SQLAI-admin.kubeconfig` exists, or record the alternate path.\n   - SQL Server 2025 is running.\n   - `az`, `kubectl`, `kubelogin`, `curl.exe`, `sqlcmd`, and the .NET 10 SDK are\n     available.\n3. Explain that setup imports a root certificate and restarts SQL Server. After\n   explicit confirmation, run from an elevated PowerShell terminal:\n\n   ```powershell\n   Set-Location C:\\setup\n   Set-ExecutionPolicy -Scope Process RemoteSigned\n   .\\Setup.ps1\n   ```\n\n   Pass documented overrides only when the user supplied them.\n4. Require exit code 0 and `Setup completed successfully.`\n5. Ask before invoking the live model. If approved, run `C:\\setup\\test.ps1` and\n   require trusted HTTPS plus HTTP 200 through SQL Server. A successful direct\n   `curl` call is not sufficient.\n6. From `demo1-azure-local`, determine whether `CaldovaRegionalCare` already\n   exists. Use `-InitializeDatabase` only for an absent database and only after\n   explicit confirmation:\n\n   ```powershell\n   .\\database\\Setup-CaldovaDatabase.ps1 -InitializeDatabase\n   ```\n\n   For an existing database, run the repeat-safe update without that switch.\n7. Run the live AI validation only after separate confirmation:\n\n   ```powershell\n   .\\database\\Setup-CaldovaDatabase.ps1 -TestFoundryAi\n   ```\n\n8. Build the application. Start `app\\run.ps1` as a long-running process only\n   when the user asks to launch it.\n\n## Preflight\n\nPerform checks without repairing or provisioning:\n\n1. Confirm the application responds at `http:\u002F\u002Flocalhost:5099`.\n2. Confirm `\u002Fapi\u002Fhealth` reports `Healthy` for `CaldovaRegionalCare`.\n3. Confirm the MSSQL extension can connect to `localhost` and database\n   `CaldovaRegionalCare`.\n4. Confirm the Azure portal is already signed in and the Azure Local VM, AKS\n   cluster, and Azure Virtual Desktop resources are ready to show.\n5. Confirm Phi-3.5 Mini appears in the VS Code model picker. Do not send a\n   clinical prompt.\n6. Report each gate as `PASS`, `FAIL`, or `NOT CHECKED`. Stop on a failed gate\n   and offer the smallest relevant repair from the documented scripts.\n\n## Rehearse\n\nFollow the runbook's locked order exactly:\n\n1. Transfer Center application.\n2. Azure portal: Azure Local VM, AKS, and Azure Virtual Desktop.\n3. VS Code MSSQL connection and ordered database scripts.\n4. Native RegEx extraction.\n5. Approved `ai.Skill` row.\n6. Transfer-skill procedure, JSON payload, and\n   `sys.sp_invoke_external_rest_endpoint`.\n7. Phi-3.5 Mini in VS Code Chat.\n\nFor each beat, present only its **Say**, **Show**, and **Land** guidance, then\nwait for the user to continue. Do not execute setup or repair commands during a\nrehearsal. Do not expose credential rows when showing endpoint metadata.\n\n## Troubleshoot\n\n- Start from the failed gate and its exact error.\n- Read the owning script before proposing a change.\n- Prefer rerunning a documented validation over changing infrastructure.\n- Do not use `Connect-AksArc.ps1` unless direct kubeconfig access failed and the\n  user explicitly asks to troubleshoot Arc Cluster Connect.\n- End with the failed command, the evidence found, and the next documented\n  action.\n\n## Completion Report\n\nReport the selected mode, checks performed, commands run, gates passed, and any\nremaining manual step. Never include secret values in the report.",{"name":5,"description":7,"argument-hint":34},"Mode: prepare, preflight, rehearse, or troubleshoot","main","d2b16500cb10bf44117390e08717ca731032d423",".github\u002Fskills\u002Frun-keynote-demo-1",0,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsqlcon-eu-2026-demos","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-01 23:31:12",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add microsoft\u002Fsqlcon-eu-2026-demos --skill run-keynote-demo-1",{"tool":50,"command":51},"bunx","bunx skills add microsoft\u002Fsqlcon-eu-2026-demos --skill run-keynote-demo-1",{"tool":53,"command":54},"pnpm","pnpm dlx skills add microsoft\u002Fsqlcon-eu-2026-demos --skill run-keynote-demo-1","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsqlcon-eu-2026-demos\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Frun-keynote-demo-1\u002FSKILL.md",true,[],[59,74,89,99,110,121],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":70,"publishedAt":29},"01M69AGTKN8F66BXE45KQ3MDMX","keynote-demo-app","Build or extend a SQLCon EU 2026 keynote demo application so it looks and behaves like the other keynote apps. Use when creating a new demo view (invoices, operations, orders), restyling an existing app to match, adding a deliberate database anti-pattern for a troubleshooting demo, or wiring an app to Azure SQL or Fabric SQL with managed identity. Triggers include \"make this look like the keynote app\", \"build a demo view\", \"add the slow query demo\", \"match Caldova styling\".","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsqlcon-eu-2026-demos\u002Fblob\u002Fmain\u002Fshared\u002FSKILL.md",[65],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[71,27,72,73],"keynote demo app","azure sql","identity",{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":86,"publishedAt":29},"01M69AGRAPA61AN2A2N2RF6NCJ","validate-post-migration-data","Validate data and schema after migrating SQL Server to Azure SQL Database, Azure SQL Managed Instance, or SQL Server on Azure VM. Use after migration, restore, BACPAC import, LRS completion, cutover validation, row-count comparison, or source-target reconciliation.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsqlcon-eu-2026-demos\u002Fblob\u002Fmain\u002Fcorenote\u002Fmigration\u002Fskills\u002Fvalidate-post-migration-data\u002FSKILL.md",[80,81],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[87,23,28,27,88,72],"validate post migration data","azure sql database",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":97,"publishedAt":29},"01M69AGNG0HQK50EW1CNEFTR1N","sql-server-to-sql-mi-lrs-migration","Migrate SQL Server databases to Azure SQL Managed Instance with Log Replay Service (LRS) using managed identity for Blob access. Use for SQL Server to SQL MI, LRS, log replay, continuous restore, or low-downtime backup-chain migrations.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsqlcon-eu-2026-demos\u002Fblob\u002Fmain\u002Fcorenote\u002Fmigration\u002Fskills\u002Fsql-server-to-sql-mi-lrs-migration\u002FSKILL.md",[95,96],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[98,28,27,72,73],"sql server to sql mi lrs migration",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":107,"publishedAt":29},"01M69AGJC50G0YX7VQ52SQ0AD0","sql-bacpac-to-azure-sql-db-migration","Migrate one or all user databases from SQL Server to Azure SQL Database with an offline BACPAC workflow. Use for BACPAC, SqlPackage export\u002Fimport, bulk database migration, or offline Azure SQL Database migration requests.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsqlcon-eu-2026-demos\u002Fblob\u002Fmain\u002Fcorenote\u002Fmigration\u002Fskills\u002Fsql-bacpac-to-azure-sql-db-migration\u002FSKILL.md",[105,106],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[108,27,72,28,88,109],"sql bacpac to azure sql db migration","workflow",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":118,"publishedAt":29},"01M69AGFTTX13PCFKM3YVHKGDV","sql-backup-restore-to-azure-sql-vm-migration","Migrate a SQL Server 2008 through SQL Server 2025 source to a SQL Server 2025 target wherever it runs, including SQL Server on Azure VM, by creating a local full backup, uploading it to Azure Blob Storage with AzCopy and the operator's Microsoft Entra identity, and restoring from URL with the target SQL Server managed identity. Sources newer than SQL Server 2025 are blocked because target restore compatibility has not been validated. Use for SQL-to-SQL, local-backup, AzCopy, managed-identity, Azure SQL VM, or SQL Server 2025 restore migrations.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsqlcon-eu-2026-demos\u002Fblob\u002Fmain\u002Fcorenote\u002Fmigration\u002Fskills\u002Fsql-backup-restore-to-azure-sql-vm-migration\u002FSKILL.md",[116,117],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[27,72,119,9,120,73,28],"sql backup restore to azure sql vm migration","storage",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":128,"publishedAt":29},"01M69AGDP6XXM1YW7X1VV1QKE5","run-migration-assessment","Route generic or unresolved SQL Server assessment, readiness, compatibility, cost, and SKU recommendation requests. Use for bare server names or whenever Azure versus local\u002Fon-premises is not explicit; ask which source applies, then delegate.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsqlcon-eu-2026-demos\u002Fblob\u002Fmain\u002Fcorenote\u002Fmigration\u002Fskills\u002Frun-migration-assessment\u002FSKILL.md",[127],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},[129,28,27],"run migration assessment"]