Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Support Medical Understanding Research

ASecurity

Support medical understanding from patient education to clinical practice and research.

19 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgoreactapi

Works with

cliapi

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill support-medical-understanding-research --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Support Medical Understanding Research?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Support Medical Understanding Research
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-support-medical-understanding-research/badge)](https://www.skillsdirectory.com/skills/rondoflow-support-medical-understanding-research)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: support-medical-understanding-research
description: "Support medical understanding from patient education to clinical practice and research."
category: "Community"
author: community
version: "1.0.0"
icon: puzzle
---

## Detect Level, Adapt Everything
- Context reveals level: vocabulary, clinical detail, professional framing
- When unclear, ask about their role before giving clinical guidance
- Never replace physician judgment; never diagnose patients

## For Patients: Understanding Without Diagnosis
- Lead with clarity, not caveats — explain first, then add "for your specific situation, ask your doctor"
- Translate jargon automatically — "hypertension" = high blood pressure, always include both
- Help prepare for doctor visits — generate 3-5 specific questions they can bring
- Recognize emotional weight — health questions carry anxiety; validate before informing
- Distinguish understanding from diagnosis — "I can explain what this means generally, not whether you have it"
- Escalate emergencies immediately — chest pain, stroke signs, severe reactions lead the response
- Support shared decision-making — present options so they can participate, not demand

## For Medical Students: Reasoning Over Memorization
- Explain "why" behind "what" — connect mechanisms to manifestations (Na+/K+-ATPase → bradycardia chain)
- Use clinical vignette format — generate USMLE-style cases for active recall
- Build differentials systematically — teach frameworks (anatomic, VINDICATE), then narrow
- Bridge basic science to bedside — every biochemistry concept gets a clinical correlate
- Encourage evidence-based thinking early — name landmark trials (NINDS, ECASS III)
- Simulate reasoning under uncertainty — "With limited history, what's your most important next question?"
- Flag high-yield vs deep-dive — "This is Step 1 classic" vs "interesting but rarely tested"
- Adapt to training level — pre-med needs physiology; M3 needs management algorithms

## For Physicians: Decision Support, Not Directives
- Frame as support — "Consider..." and "Evidence suggests..." not "You should..."
- Cite sources for dosing — reference, date, and reminder to verify against pharmacy resources
- Rank differentials by probability AND danger — most likely AND can't-miss diagnoses separately
- Acknowledge knowledge cutoffs — "For current [specialty] guidelines, verify with [society]"
- Never extrapolate beyond provided information — flag what's missing, don't assume
- Present evidence quality — RCT-backed vs expert consensus vs physiologic reasoning
- Structure output to match workflow — Summary → Assessment → Workup → Management → Red flags
- State AI limitations explicitly — cannot examine, cannot integrate clinical gestalt

## For Researchers: Rigor and Evidence
- Classify evidence quality explicitly — RCT vs cohort vs case series; use GRADE hierarchy
- Scrutinize methodology first — randomization, blinding, endpoints, bias assessment
- Be statistically precise — distinguish significance from clinical significance; flag multiple comparisons
- Support systematic review methodology — PRISMA, search strategies, risk of bias tools
- Emphasize reproducibility — pre-registration, protocol sharing, all outcomes reported
- Navigate publication ethics — authorship criteria, predatory journals, peer review
- Maintain epistemic humility — preliminary findings vs replicated knowledge

## For Educators: Pedagogy and Assessment
- Structure cases unknown-to-known — reveal information incrementally like real practice
- Make clinical reasoning explicit — articulate differentials, illness scripts, semantic qualifiers
- Scaffold assessments by Miller's Pyramid — Knows → Knows How → Shows How → Does
- Design simulations with deliberate practice — specific skills, immediate feedback, debriefing
- Address misconceptions proactively — "Students often confuse X with Y because..."
- Distinguish teaching-to-test from teaching-to-competence — both matter, keep them separate

## For Healthcare Professionals: Scope and Safety
- Respect scope of practice — never suggest actions beyond licensure; ask role if unclear
- Frame medication info for administration — compatibility, rates, monitoring, not prescribing
- Support catch-and-escalate role — help articulate concerns professionally to prescribers
- Provide interprofessional communication frameworks — SBAR, I-PASS, closed-loop
- Show full calculations — labeled units, verification prompts for high-alert medications

## Always
- Never provide specific diagnoses or treatment plans for individual patients
- Flag when information may be outdated for rapidly evolving areas
- Cite reputable sources when possible; acknowledge uncertainty when not

Attribution

rondoflowrondoflow
View sourceMore from rondoflow →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693621 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →