healthcare-ai-research-guardrails
Provides safety and compliance guardrails for AI projects in regulated healthcare and clinical domains.
Install
mkdir -p .claude/skills/healthcare-ai-research-guardrails && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13508" && unzip -o skill.zip -d .claude/skills/healthcare-ai-research-guardrails && rm skill.zipInstalls to .claude/skills/healthcare-ai-research-guardrails
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use this skill when researching, drafting, reviewing, or building healthcare, wellness, clinical, medical-device, patient-support, health-content, or health-data AI workflows that require source quality, privacy, non-diagnostic boundaries, human review, and regulated-domain guardrails.Key capabilities
- →Research healthcare AI workflows
- →Draft healthcare AI content
- →Review healthcare AI systems
- →Build healthcare AI workflows with guardrails
- →Ensure privacy in health data AI
How it works
The skill classifies the task and identifies the audience and risk level. It then prefers authoritative sources, separates facts from assumptions, and checks privacy boundaries.
Inputs & outputs
When to use healthcare-ai-research-guardrails
- →Reviewing AI clinical workflow support
- →Establishing privacy boundaries for health data
- →Defining disclaimers for patient-facing content
About this skill
Healthcare AI Research Guardrails
Support healthcare work with evidence handling and safety boundaries; do not act as a clinician or medical-device authority.
Workflow
- Classify the task: general health content, patient education, clinical workflow support, medical-device/software concern, privacy/data handling, or operational healthcare tooling.
- Identify the audience and risk level: consumer, patient, caregiver, clinician, admin staff, developer, regulator, or internal reviewer.
- Prefer primary and authoritative sources: official regulators, public-health bodies, clinical guidelines, peer-reviewed evidence, and product documentation.
- Separate facts, assumptions, uncertainty, and user-specific advice. Avoid diagnosis, treatment selection, medication changes, or emergency triage decisions.
- Check privacy boundaries before using any health data: minimum necessary data, consent, de-identification, retention, access controls, audit logs, and local policy.
- For AI workflows, define human review, escalation, fallback, disclaimers, model limitations, source citations, and post-deployment monitoring.
- For medical-device-adjacent functionality, flag that regulatory review may be required before claims, deployment, or user-facing decisions.
- Deliver a concise risk review with sources checked, unresolved evidence gaps, required human owner, and safe next step.
Checklist
- Include emergency and urgent-care escalation language when user harm could result from delay.
- Cite current sources for medical, regulatory, or public-health claims.
- Avoid personalized medical advice unless the user has explicitly provided clinician-approved context and the output remains drafting/support.
- Validate accessibility and plain-language readability for patient-facing content.
- Log neither PHI nor sensitive health details unless the system is explicitly designed and approved for that purpose.
- Treat model outputs as suggestions for qualified humans, not final clinical decisions.
Guardrails
- Do not diagnose, prescribe, interpret test results for a patient, or recommend changing treatment.
- Do not claim HIPAA, FDA, CE, or other compliance status without legal/regulatory evidence.
- Do not process or expose protected health information outside approved systems.
- Do not present AI-generated healthcare output as clinician-reviewed unless it actually was.
When not to use it
- →When the task requires diagnosing, prescribing, or interpreting test results for a patient
- →When the task involves claiming HIPAA, FDA, or CE compliance without legal evidence
- →When the task requires processing or exposing protected health information outside approved systems
Limitations
- →Does not diagnose, prescribe, interpret test results for a patient, or recommend changing treatment
- →Does not claim HIPAA, FDA, CE, or other compliance status without legal/regulatory evidence
- →Does not process or expose protected health information outside approved systems
How it compares
This skill provides specific guardrails and a structured workflow for healthcare AI, ensuring non-diagnostic boundaries and human review, unlike general AI development.
Compared to similar skills
healthcare-ai-research-guardrails side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| healthcare-ai-research-guardrails (this skill) | 0 | 1mo | No flags | Advanced |
| offensive-exploit-dev-course | 0 | 2mo | Review | Advanced |
| evidence-quality-check | 0 | 3mo | No flags | Intermediate |
| red-team-tools-and-methodology | 7 | 6mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by srednoff888-art
View all by srednoff888-art →You might also like
offensive-exploit-dev-course
26zl
Full exploit development course roadmap and syllabus: weekly topics, recommended reading, lab setup, and learning path from vulnerability classes through advanced exploitation. Use to structure exploit dev training or onboard new researchers. Use only for authorized security research, training, or a
evidence-quality-check
Std07-1
**Призначення**: перевірити що твердження у відповіді мають реальні докази, не вигадані. **Коли викликати**: при будь-якому RECON / DISCOVERY / review / ADR.
red-team-tools-and-methodology
davila7
This skill should be used when the user asks to "follow red team methodology", "perform bug bounty hunting", "automate reconnaissance", "hunt for XSS vulnerabilities", "enumerate subdomains", or needs security researcher techniques and tool configurations from top bug bounty hunters.
idapython
mrexodia
IDA Pro Python scripting for reverse engineering. Use when writing IDAPython scripts, analyzing binaries, working with IDA's API for disassembly, decompilation (Hex-Rays), type systems, cross-references, functions, segments, or any IDA database manipulation. Covers ida_* modules (50+), idautils iterators, and common patterns.
identify-vault-protocol
tradingstrategy-ai
Identify an unknown vault protocol based on its smart contract address
hunt-focus-definition
OTRF
Define a focused hunt hypothesis by synthesizing completed system internals and adversary tradecraft research. Use this skill after research has been completed to narrow a high-level hunt topic into a single, concrete attack pattern with clear investigative intent. This skill produces a structured, testable hypothesis and should be used before selecting data sources, defining environment scope, or developing analytics.