biomedical-evidence-review-v2
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.
- License 许可
- MIT
- 最近更新
- 2026-11-01
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- biomedical-evidence-review-v2
- description
- 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.
02 资源文件 5
- 资产文件assets/output-template.md5.5 KB
- 参考文档references/attribution.md2.0 KB
- 参考文档references/design-recommendations.md1.9 KB
- 参考文档references/product-selection-recommendations.md2.9 KB
- 参考文档references/related-documentation.md7.4 KB
03 SKILL.md 正文
Biomedical Evidence Review
Investigation workflow
- Interpret the research goal and decompose it into exactly three distinct, focused queries: primary mechanism, comparison or translation, and limitations or uncertainty.
- Call the SQL MCP tool
search_evidenceexactly three times, once for each focused query, withtop_kset to 3. Issue the calls together when parallel tool calling is available. - Select the three most relevant distinct articles across the MCP results. Do not summarize every returned passage. Use
get_article_contextonly when the returned neighboring passages are insufficient to interpret a selected result. - Compare mechanisms, corroboration, disagreement, study limitations, and uncertainty. This cross-source judgment is the value beyond ranked evidence search.
- Calibrate confidence to the exact claim. When multiple sources converge on mechanistic plausibility, state
High for mechanistic plausibilityeven if human clinical causality or effect size remains limited. Do not collapse those separate judgments intoMixed. - 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. - State clearly when the corpus is insufficient. Never invent articles, PMCIDs, quotations, findings, or citations.
- Keep the initial briefing between 110 and 150 words. Avoid repeating a finding in multiple sections.
- End with one short suggested follow-up question.
Conversation continuity
For 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.
For a strongest-causal-evidence follow-up, use exactly these evidence-signal labels:
**Strongest**: name the leading source and its direct causal intervention or manipulation**Comparison**: explain why the other evidence is less causal**Limitation**: state the leading source's most important translational caveat
Response structure
## Bottom line: one sentence, 30 words maximum## Evidence signals: exactly three bullets; begin each with a bold 1-3 word label and keep each bullet under 22 words## Confidence: one sentence, 25 words maximum; lead withHigh for mechanistic plausibilitywhen supported, then separately qualify human clinical causality or effect size## Suggested follow-up: one short question, 20 words maximum- Sources: exactly three plain PMCIDs
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.