run-keynote-demo-1
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.
- License 许可
- MIT
- 最近更新
- 2026-11-01
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- run-keynote-demo-1
- description
- 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.
- argument-hint
- Mode: prepare, preflight, rehearse, or troubleshoot
03 SKILL.md 正文
Run Keynote Demo 1
Guide the user through the existing Caldova Regional Care demo. Treat the package README and demo runbook as the sources of truth. Use repository scripts as written; do not recreate their logic with ad hoc commands.
Safety Rules
- Never display or read into chat the kubeconfig, Kubernetes API key, database
scoped credential secret, database master-key password, or a literal key from
chatLanguageModels.json. - Never retrieve a Kubernetes Secret directly for inspection. Only the existing setup and database wrappers may consume it.
- Do not provision, restart, scale, or modify Azure Local, AKS Arc, Foundry Local, the model deployment, or portal resources.
- Do not bypass TLS validation or add
--insecure. - Ask for explicit confirmation before running an elevated setup, restarting SQL Server, initializing the database, invoking the live model, or generating a live receiving briefing.
- Never request a secret through chat. If a terminal prompts for one, tell the user to enter it directly in the terminal.
Select a Mode
Infer the mode from the request. If it is unclear, ask the user to choose:
prepare: configure a demo VM and database using existing infrastructure.preflight: perform non-destructive readiness checks before presenting.rehearse: guide the locked presentation sequence one beat at a time.troubleshoot: diagnose one failed gate without broad environment changes.
Prepare
-
Confirm the user is on the intended Windows demo VM and read setup guidance.
-
Check, without printing sensitive contents:
- PowerShell is elevated before setup.
C:\setup\SJ-SQLAI-admin.kubeconfigexists, or record the alternate path.- SQL Server 2025 is running.
az,kubectl,kubelogin,curl.exe,sqlcmd, and the .NET 10 SDK are available.
-
Explain that setup imports a root certificate and restarts SQL Server. After explicit confirmation, run from an elevated PowerShell terminal:
Set-Location C:\setup Set-ExecutionPolicy -Scope Process RemoteSigned .\Setup.ps1Pass documented overrides only when the user supplied them.
-
Require exit code 0 and
Setup completed successfully. -
Ask before invoking the live model. If approved, run
C:\setup\test.ps1and require trusted HTTPS plus HTTP 200 through SQL Server. A successful directcurlcall is not sufficient. -
From
demo1-azure-local, determine whetherCaldovaRegionalCarealready exists. Use-InitializeDatabaseonly for an absent database and only after explicit confirmation:.\database\Setup-CaldovaDatabase.ps1 -InitializeDatabaseFor an existing database, run the repeat-safe update without that switch.
-
Run the live AI validation only after separate confirmation:
.\database\Setup-CaldovaDatabase.ps1 -TestFoundryAi -
Build the application. Start
app\run.ps1as a long-running process only when the user asks to launch it.
Preflight
Perform checks without repairing or provisioning:
- Confirm the application responds at
http://localhost:5099. - Confirm
/api/healthreportsHealthyforCaldovaRegionalCare. - Confirm the MSSQL extension can connect to
localhostand databaseCaldovaRegionalCare. - Confirm the Azure portal is already signed in and the Azure Local VM, AKS cluster, and Azure Virtual Desktop resources are ready to show.
- Confirm Phi-3.5 Mini appears in the VS Code model picker. Do not send a clinical prompt.
- Report each gate as
PASS,FAIL, orNOT CHECKED. Stop on a failed gate and offer the smallest relevant repair from the documented scripts.
Rehearse
Follow the runbook's locked order exactly:
- Transfer Center application.
- Azure portal: Azure Local VM, AKS, and Azure Virtual Desktop.
- VS Code MSSQL connection and ordered database scripts.
- Native RegEx extraction.
- Approved
ai.Skillrow. - Transfer-skill procedure, JSON payload, and
sys.sp_invoke_external_rest_endpoint. - Phi-3.5 Mini in VS Code Chat.
For each beat, present only its Say, Show, and Land guidance, then wait for the user to continue. Do not execute setup or repair commands during a rehearsal. Do not expose credential rows when showing endpoint metadata.
Troubleshoot
- Start from the failed gate and its exact error.
- Read the owning script before proposing a change.
- Prefer rerunning a documented validation over changing infrastructure.
- Do not use
Connect-AksArc.ps1unless direct kubeconfig access failed and the user explicitly asks to troubleshoot Arc Cluster Connect. - End with the failed command, the evidence found, and the next documented action.
Completion Report
Report the selected mode, checks performed, commands run, gates passed, and any remaining manual step. Never include secret values in the report.
04 同仓库更多 Skills
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".
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.
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.
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/import, bulk database migration, or offline Azure SQL Database migration requests.
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.
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/on-premises is not explicit; ask which source applies, then delegate.