AI Agent Hub
Back to skills
Medical Evidence Integration and Information Verification icon

Medical Evidence Integration and Information Verification

Professional Updated 2026.08.29

Paste the following prompt into your AI chat to install this skill:

Please follow https://skillhub.cn/install/skillhub.md to install @baitongai/medical-evidence-integration-and-information-verification into your AI assistant.

About this skill

Problem

Medical evidence integration and information verification often run through protected cloud workflows. The model should not continue from local prompts, historical context, or ambiguous authorization, because credential state, permission expiry, and untrusted output can become entangled.

How It Works and Boundaries

This skill puts authorization gates before business reasoning. Key steps:
- Run scripts/auth.py ensure first; continue only on AUTH_OK.
- If AUTH_REQUIRED, AUTH_INVALID, CREDENTIALS_MISSING, or CREDENTIALS_INVALID appears, obtain the current user JWT via WorkBuddy and pass it to the auth script for binding.
- Re-run authorization after a successful bind, then call scripts/protected.py to fetch protected instructions.
- Execute medical evidence integration and verification only after protected instructions are returned; stop on failure and report the stdout signal plus key stderr lines.

Boundary: this is not a generic summarizer. It must not silently retry, degrade, or produce business output when authorization fails. Distinguish network errors, expired signatures, and VIP expiry, and limit retries to once.

Use Cases

  • Before checking disease treatment advice, complete WorkBuddy auth, fetch protected instructions, then integrate evidence
  • When validating medical sources, require AUTH_OK and protected.py output, otherwise stop and report
  • In medical QA workflows, report CREDENTIALS_INVALID using stdout and stderr signals
  • Connect cloud protected instructions to medical verification and block business output on auth failure

Best For

  • Clinical AI engineers integrating medical evidence workflows into protected cloud services
  • Workflow engineers enforcing WorkBuddy authorization gates before medical QA
  • Platform engineers handling failure reporting and user prompts for medical verification
  • Security engineers blocking unauthorized output in medical decision-support workflows