demo-caldova-evidence-agent
Skill0 starsChanged 53 days agoMITView on GitHub
Guide or rehearse the Caldova Evidence Agent demo one beat at a time. Use when: demo the Caldova evidence agent, rehearse the SQL MCP demo, walk through the evidence agent, start the evidence demo, next beat, show Foundry Log stream, or practice the causal evidence follow-up.
In this repository18 other files it gives its agents.
- biomedical-evidence-review-v2Skill
- analyze-readiness-at-scaleSkill
- evaluate-azure-migration-assessmentSkill
- evaluate-offline-migration-readinessSkill
- generate-migration-prerequisite-planSkill
- get-migration-assessmentSkill
- recommend-migration-pathSkill
- recommend-sku-sizingSkill
- run-migration-assessmentSkill
- sql-backup-restore-to-azure-sql-vm-migrationSkill
- sql-bacpac-to-azure-sql-db-migrationSkill
- sql-server-to-sql-mi-lrs-migrationSkill
- validate-post-migration-dataSkill
- build-caldova-evidence-agentSkill
- run-caldova-evidence-agentSkill
- run-handsfree-indexingSkill
- run-keynote-demo-1Skill
- keynote-demo-appSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Follow the run-caldova-evidence-agent skill to open or reuse the app and verify its standalone Edge window.
- Distinctive: line 15
Ask the presenter to open the hosted agent Log stream in Microsoft Foundry if it is not already visible.
- Distinctive: line 24
Read the five-phase visual briefing.
- Distinctive: line 25
Use Find strongest causal evidence and show the visual comparison.
- Very specific: line 28
After each beat, provide only the action, expected visual proof, and concise talk track.
- Distinctive: line 32
Never run deployment scripts during a presentation walkthrough.
- Distinctive: line 33
Never reset the database or corpus during the demo.
- Distinctive: line 34
Do not claim the human clinical evidence is high-confidence.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Demo Caldova Evidence Agent
Guide the presenter from DEMO-RUNBOOK.md. Do not provision, redeploy, or modify resources during a demo request.
Preflight
- Read
DEMO-RUNBOOK.mdcompletely. - Run
deploy/11-verify-system.ps1synchronously. - Follow the
run-caldova-evidence-agentskill to open or reuse the app and verify its standalone Edge window. - Ask the presenter to open the hosted agent Log stream in Microsoft Foundry if it is not already visible.
- Report readiness and wait for the presenter to say
start.
Beat Order
Guide exactly one beat at a time:
- Establish the natural research question.
- Show the live Foundry skill and three direct SQL MCP calls.
- Read the five-phase visual briefing.
- Use Find strongest causal evidence and show the visual comparison.
- Close on the governed three-tool SQL MCP boundary.
After each beat, provide only the action, expected visual proof, and concise talk track. Wait for next before advancing.
Guardrails
- Never run deployment scripts during a presentation walkthrough.
- Never reset the database or corpus during the demo.
- Do not claim the human clinical evidence is high-confidence; say confidence is high for mechanistic plausibility and qualified for human causality.
- The causal follow-up should reuse evidence and make no new MCP search when the existing sources are sufficient.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

