[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69AFSCTBPTEM1KRJHWVGAPF":3,"skill-same:01M69AFSCTBPTEM1KRJHWVGAPF":74},{"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":22,"linkOnly":23,"markdownContent":24,"markdownBody":25,"frontMatter":26,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M69AFSCTBPTEM1KRJHWVGAPF","biomedical-evidence-review-v2",null,"Use for broad, comparative, or follow-up biomedical evidence questions that require focused parallel retrieval, cross-source synthesis, limitations, concise citations, and a next research question.","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\u002Fcorenote\u002Fcaldovaevidenceagent\u002Fagent\u002Fhosted\u002Fcaldova-evidence-hosted\u002Fskills\u002Fbiomedical-evidence-review\u002FSKILL.md",[],[19,20,21],"review","biomedical evidence review v2","research","2026-11-10 10:12:30",false,"---\nname: biomedical-evidence-review-v2\ndescription: Use for broad, comparative, or follow-up biomedical evidence questions that require focused parallel retrieval, cross-source synthesis, limitations, concise citations, and a next research question.\n---\n\n# Biomedical Evidence Review\n\n## Investigation workflow\n\n1. Interpret the research goal and decompose it into exactly three distinct, focused queries: primary mechanism, comparison or translation, and limitations or uncertainty.\n2. Call the SQL MCP tool `search_evidence` exactly three times, once for each focused query, with `top_k` set to 3. Issue the calls together when parallel tool calling is available.\n3. Select the three most relevant distinct articles across the MCP results. Do not summarize every returned passage. Use `get_article_context` only when the returned neighboring passages are insufficient to interpret a selected result.\n4. Compare mechanisms, corroboration, disagreement, study limitations, and uncertainty. This cross-source judgment is the value beyond ranked evidence search.\n5. Calibrate confidence to the exact claim. When multiple sources converge on mechanistic plausibility, state `High for mechanistic plausibility` even if human clinical causality or effect size remains limited. Do not collapse those separate judgments into `Mixed`.\n6. Cite a source once per compact claim group using its plain PMCID, such as `PMC10142784`. Do not emit Markdown links or raw URLs; the application renders PMCIDs as links.\n7. State clearly when the corpus is insufficient. Never invent articles, PMCIDs, quotations, findings, or citations.\n8. Keep the initial briefing between 110 and 150 words. Avoid repeating a finding in multiple sections.\n9. End with one short suggested follow-up question.\n\n## Conversation continuity\n\nFor follow-up questions, retain the earlier investigation and answer from it when sufficient. If new evidence is needed, call `search_evidence` only for the evidence gap and use `get_article_context` only when necessary. Every follow-up must use the same visual response structure below; never return a prose-only paragraph. Keep follow-ups concise and no longer than the initial briefing.\n\nFor a strongest-causal-evidence follow-up, use exactly these evidence-signal labels:\n\n- `**Strongest**`: name the leading source and its direct causal intervention or manipulation\n- `**Comparison**`: explain why the other evidence is less causal\n- `**Limitation**`: state the leading source's most important translational caveat\n\n## Response structure\n\n- `## Bottom line`: one sentence, 30 words maximum\n- `## Evidence signals`: exactly three bullets; begin each with a bold 1-3 word label and keep each bullet under 22 words\n- `## Confidence`: one sentence, 25 words maximum; lead with `High for mechanistic plausibility` when supported, then separately qualify human clinical causality or effect size\n- `## Suggested follow-up`: one short question, 20 words maximum\n- Sources: exactly three plain PMCIDs\n","# Biomedical Evidence Review\n\n## Investigation workflow\n\n1. Interpret the research goal and decompose it into exactly three distinct, focused queries: primary mechanism, comparison or translation, and limitations or uncertainty.\n2. Call the SQL MCP tool `search_evidence` exactly three times, once for each focused query, with `top_k` set to 3. Issue the calls together when parallel tool calling is available.\n3. Select the three most relevant distinct articles across the MCP results. Do not summarize every returned passage. Use `get_article_context` only when the returned neighboring passages are insufficient to interpret a selected result.\n4. Compare mechanisms, corroboration, disagreement, study limitations, and uncertainty. This cross-source judgment is the value beyond ranked evidence search.\n5. Calibrate confidence to the exact claim. When multiple sources converge on mechanistic plausibility, state `High for mechanistic plausibility` even if human clinical causality or effect size remains limited. Do not collapse those separate judgments into `Mixed`.\n6. Cite a source once per compact claim group using its plain PMCID, such as `PMC10142784`. Do not emit Markdown links or raw URLs; the application renders PMCIDs as links.\n7. State clearly when the corpus is insufficient. Never invent articles, PMCIDs, quotations, findings, or citations.\n8. Keep the initial briefing between 110 and 150 words. Avoid repeating a finding in multiple sections.\n9. End with one short suggested follow-up question.\n\n## Conversation continuity\n\nFor follow-up questions, retain the earlier investigation and answer from it when sufficient. If new evidence is needed, call `search_evidence` only for the evidence gap and use `get_article_context` only when necessary. Every follow-up must use the same visual response structure below; never return a prose-only paragraph. Keep follow-ups concise and no longer than the initial briefing.\n\nFor a strongest-causal-evidence follow-up, use exactly these evidence-signal labels:\n\n- `**Strongest**`: name the leading source and its direct causal intervention or manipulation\n- `**Comparison**`: explain why the other evidence is less causal\n- `**Limitation**`: state the leading source's most important translational caveat\n\n## Response structure\n\n- `## Bottom line`: one sentence, 30 words maximum\n- `## Evidence signals`: exactly three bullets; begin each with a bold 1-3 word label and keep each bullet under 22 words\n- `## Confidence`: one sentence, 25 words maximum; lead with `High for mechanistic plausibility` when supported, then separately qualify human clinical causality or effect size\n- `## Suggested follow-up`: one short question, 20 words maximum\n- Sources: exactly three plain PMCIDs\n",{"name":5,"description":7},"main","d2b16500cb10bf44117390e08717ca731032d423","corenote\u002Fcaldovaevidenceagent\u002Fagent\u002Fhosted\u002Fcaldova-evidence-hosted\u002Fskills\u002Fbiomedical-evidence-review",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":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add microsoft\u002Fsqlcon-eu-2026-demos --skill biomedical-evidence-review-v2",{"tool":42,"command":43},"bunx","bunx skills add microsoft\u002Fsqlcon-eu-2026-demos --skill biomedical-evidence-review-v2",{"tool":45,"command":46},"pnpm","pnpm dlx skills add microsoft\u002Fsqlcon-eu-2026-demos --skill biomedical-evidence-review-v2","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsqlcon-eu-2026-demos\u002Fblob\u002Fmain\u002Fcorenote\u002Fcaldovaevidenceagent\u002Fagent\u002Fhosted\u002Fcaldova-evidence-hosted\u002Fskills\u002Fbiomedical-evidence-review\u002FSKILL.md",true,[50,56,62,66,70],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"assets\u002Foutput-template.md","ASSET","资产文件",5599,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-solution-rag-enterprise-search-gke-sqldb\u002Fassets\u002Foutput-template.md",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fattribution.md","REFERENCE","参考文档",2007,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-solution-rag-enterprise-search-gke-sqldb\u002Freferences\u002Fattribution.md",{"path":63,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fdesign-recommendations.md",1993,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-solution-rag-enterprise-search-gke-sqldb\u002Freferences\u002Fdesign-recommendations.md",{"path":67,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fproduct-selection-recommendations.md",2997,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-solution-rag-enterprise-search-gke-sqldb\u002Freferences\u002Fproduct-selection-recommendations.md",{"path":71,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Frelated-documentation.md",7571,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-solution-rag-enterprise-search-gke-sqldb\u002Freferences\u002Frelated-documentation.md",[75,91,108,118,129,140],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":86,"publishedAt":22},"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",[81],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[87,88,89,90],"keynote demo app","sql","azure sql","identity",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":103,"publishedAt":22},"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",[97,98],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[104,105,106,88,107,89],"validate post migration data","validate","sql server","azure sql database",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":116,"publishedAt":22},"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",[114,115],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},[117,106,88,89,90],"sql server to sql mi lrs migration",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":126,"publishedAt":22},"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",[124,125],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},[127,88,89,106,107,128],"sql bacpac to azure sql db migration","workflow",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":137,"publishedAt":22},"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",[135,136],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},[88,89,138,9,139,90,106],"sql backup restore to azure sql vm migration","storage",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":147,"publishedAt":22},"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",[146],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[148,106,88],"run migration assessment"]