Agent skill

Clinical Decision Support Documents

by jaechang-hits in jaechang-hits/SciAgent-Skills

Guidelines for clinical decision support (CDS) documents: biomarker-stratified cohort analyses and GRADE-graded treatment reports.

CC-BY-4.0Auto-check passedResearch & Science

Install Clinical Decision Support Documents

skills CLI
$ npx skills add jaechang-hits/SciAgent-Skills --skill clinical-decision-support-documents -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jaechang-hits/SciAgent-Skills clinical-decision-support-documents --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jaechang-hits/SciAgent-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/scientific-writing/clinical-decision-support-documents .claude/skills/clinical-decision-support-documents && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
clinical-decision-support-documents
GitHub stars
374
Used in
1 other repo
Token cost
~3k tokens
SKILL.md length
1,305 words
Files
1
Skills in repo
169
Repo updated
First seen
Licence
CC-BY-4.0

At a glance

Guidelines for clinical decision support (CDS) documents: biomarker-stratified cohort analyses and GRADE-graded treatment reports.

  • Works in 4 steps: Document Types → GRADE Evidence Grading System → Outcome Metrics → …
  • Pharma research docs
  • SKILL.md covers Overview, Key Concepts, Decision Framework and Best Practices, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Clinical Decision Support Documents is an agent skill from jaechang-hits/SciAgent-Skills. Guidelines for clinical decision support (CDS) documents: biomarker-stratified cohort analyses and GRADE-graded treatment reports. Covers structure, executive summaries, evidence grading (1A–2C), stats (HR, CI, survival), and biomarker integration. Use for pharma research docs, clinical guidelines, regulatory submissions.

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Research & Science, covering Clinical and healthcare research and Summarization. The repository describes itself as: 197 bioinformatics & life science skills for Claude Code and AI agents — BixBench 92.0% accuracy. RNA-seq, single-cell, drug discovery, proteomics, and more. Powers OmicsHorizon. The licence is CC-BY-4.0.

When your agent uses it

  • Pharma research docs
  • Clinical guidelines
  • Regulatory submissions

Example prompts

  • “Use the clinical-decision-support-documents skill to guideline for clinical decision support (CDS) documents: biomarker-stratified cohort analyses…”
  • “/clinical-decision-support-documents”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Document Types
  2. GRADE Evidence Grading System
  3. Outcome Metrics
  4. Statistical Reporting Standards

What it can do on your machine

Read from SKILL.md and the folder at commit 82c862c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • gdt.gradepro.org
    • doi.org
    • consort-statement.org
    • strobe-statement.org
    • ich.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Clinical Decision Support Documents loads about 3k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 1,305 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~90
When it runs · the whole SKILL.md, loaded when a task matches
~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jaechang-hits/SciAgent-Skills at commit 82c862c, republished under its CC-BY-4.0 licence (© jaechang-hits). 1,305 words, ~3,028 tokens.

Download SKILL.mdSave it as .claude/skills/clinical-decision-support-documents/SKILL.md (or your agent's skills folder).
name
clinical-decision-support-documents
description
Guidelines for clinical decision support (CDS) documents: biomarker-stratified cohort analyses and GRADE-graded treatment reports. Covers structure, executive summaries, evidence grading (1A–2C), stats (HR, CI, survival), and biomarker integration. Use for pharma research docs, clinical guidelines, regulatory submissions.
license
CC-BY-4.0

Clinical Decision Support Documents

Overview

Clinical decision support (CDS) documents are analytical reports for pharmaceutical research, guideline development, and regulatory submissions. This knowhow covers two main document types: Patient Cohort Analyses (biomarker-stratified group outcomes) and Treatment Recommendation Reports (evidence-graded clinical guidelines). For individual patient-level treatment plans, use the treatment-plans skill instead.

Key Concepts

1. Document Types

Patient Cohort Analysis — Group-level statistical comparison of patient subgroups stratified by biomarkers, molecular subtypes, or clinical characteristics.

  • Typical content: demographics, biomarker stratification, outcome metrics (OS, PFS, ORR), Kaplan-Meier curves, forest plots
  • Audience: pharmaceutical companies, clinical researchers, regulatory bodies
  • Length: 5–15 pages (1-page executive summary + detailed sections)

Treatment Recommendation Report — Evidence-based clinical guidelines with GRADE-graded recommendations for disease management.

  • Typical content: evidence review, recommendations by line of therapy, decision algorithm flowcharts, monitoring protocols
  • Audience: guideline committees, medical affairs, KOLs
  • Length: 5–20 pages
2. GRADE Evidence Grading System

The Grading of Recommendations, Assessment, Development and Evaluations (GRADE) system classifies recommendations by strength and evidence quality:

GradeStrengthEvidence QualityMeaning
1AStrongHighBenefits clearly outweigh risks; consistent RCT data
1BStrongModerateBenefits likely outweigh risks; limited RCT data
2AWeakHighTrade-offs exist; high-quality evidence but patient values matter
2BWeakModerateUncertain trade-offs; limited evidence
2CWeakLowVery uncertain; expert opinion or observational data only
3. Outcome Metrics
MetricAbbreviationDefinition
Overall SurvivalOSTime from treatment start to death from any cause
Progression-Free SurvivalPFSTime to disease progression or death
Objective Response RateORRProportion with CR + PR per RECIST 1.1
Duration of ResponseDORTime from first response to progression
Disease Control RateDCRProportion with CR + PR + SD
4. Statistical Reporting Standards
  • Hazard ratios: Report with 95% CI (e.g., HR 0.65, 95% CI 0.48–0.89, p=0.007)
  • Survival data: Median OS/PFS with 95% CI + landmark rates (6-mo, 12-mo, 24-mo)
  • Response rates: Point estimate with 95% CI
  • Kaplan-Meier curves: Include number-at-risk tables below, censoring markers, log-rank p-value
  • Subgroup analyses: Forest plots with interaction p-values; clearly label pre-specified vs exploratory

Decision Framework

Use this framework to select the appropriate document type:

Is this about a POPULATION or an INDIVIDUAL patient?
├── POPULATION (group-level analysis)
│   ├── Comparing outcomes between subgroups? → Patient Cohort Analysis
│   ├── Developing treatment guidelines? → Treatment Recommendation Report
│   └── Both analysis and recommendations? → Combined (cohort analysis + recommendations chapter)
└── INDIVIDUAL (single patient)
    └── Use treatment-plans skill instead
ScenarioDocument TypeKey Sections
Phase 2/3 trial subgroup analysisCohort AnalysisBiomarker stratification, survival curves, forest plots
Clinical practice guidelineTreatment RecommendationsGRADE-graded recs, decision algorithm, evidence tables
Companion diagnostic developmentCohort AnalysisBiomarker-response correlation, sensitivity/specificity
Medical affairs strategyTreatment RecommendationsCompetitive landscape, positioning, KOL education
Real-world evidence studyCohort AnalysisEMR cohort definition, outcomes by treatment arm

Best Practices

  1. Always start with a full-page executive summary: Page 1 should contain 3–5 colored summary boxes (findings, biomarkers, implications, statistics, safety) that are scannable in 60 seconds. No table of contents on page 1. This is the single most impactful formatting decision for CDS documents.

  2. Use GRADE consistently: Every treatment recommendation must have a GRADE rating (1A–2C) with documented rationale. Do not mix GRADE with other rating systems within the same document.

  3. Report effect sizes, not just p-values: Always include hazard ratios or odds ratios with 95% confidence intervals. A p-value alone does not convey clinical significance or effect magnitude.

  4. Specify biomarker assay details: Name the platform (e.g., FoundationOne CDx, Ventana PD-L1 SP263), cut-points, and validation status. Biomarker results are only actionable when the assay is known.

  5. Use RECIST 1.1 for response assessment: For immunotherapy cohorts, note iRECIST criteria and pseudoprogression handling. Clearly state which criteria were used.

  6. Include number-at-risk tables: Below every Kaplan-Meier curve, show the number of patients at risk at each time point. This is mandatory for credible survival analysis.

  7. Declare data completeness and follow-up: Report median follow-up time, data maturity (% events), and how missing data was handled (complete case, imputation method).

  8. De-identify per HIPAA Safe Harbor: Remove all 18 HIPAA identifiers before including any patient-level data. Add confidentiality headers for proprietary pharmaceutical data.

  9. Color-code consistently: Blue = data/information, green = biomarkers/positive, orange = clinical implications/caution, red = warnings/safety, gray = statistics/methods.

  10. Date and version all recommendations: Include analysis date, data cutoff date, and planned update schedule. Treatment guidelines become outdated as new trial data emerges.

Common Pitfalls

  1. Mixing population-level and individual-level recommendations: CDS documents analyze cohorts, not individuals. Stating "Patient X should receive..." is inappropriate. How to avoid: Use language like "Patients with biomarker X may benefit from..." or "Evidence supports [therapy] for [population] (Grade 1B)."

  2. Over-interpreting subgroup analyses: Post-hoc subgroup analyses are hypothesis-generating, not confirmatory. How to avoid: Always label exploratory vs pre-specified subgroups. Report interaction p-values. State "These findings require prospective validation."

  3. Omitting confidence intervals: Reporting median PFS = 12.5 months without CI makes the precision invisible. How to avoid: Always format as "median PFS 12.5 months (95% CI: 9.8–15.2)."

  4. Ignoring competing risks: In oncology cohorts, patients may die from non-cancer causes, biasing standard Kaplan-Meier estimates. How to avoid: For OS analysis, note competing causes. For PFS, acknowledge censoring for non-disease events.

  5. Inconsistent GRADE application: Grading one recommendation as 1A but not grading others leaves quality gaps. How to avoid: Grade every recommendation. If evidence is insufficient, assign 2C with "insufficient evidence" note.

  6. Executive summary that is too detailed: A 2-page executive summary defeats the purpose. How to avoid: Limit to page 1 only. Use bullet points in colored boxes, not paragraphs. End with \newpage before TOC.

  7. Missing regulatory compliance elements: Omitting confidentiality notices or HIPAA de-identification in pharmaceutical documents. How to avoid: Add confidentiality header to every page. Include de-identification statement in methods section.

Show full SKILL.md (414 more words)Show less

Workflow

Standard CDS Document Development Process
  1. Define scope: Identify document type (cohort analysis vs treatment recommendations), disease state, target audience, and data sources
  2. Gather evidence: Collect trial data, biomarker results, published guidelines. For recommendations, perform systematic evidence review
  3. Design document structure: Select appropriate sections based on document type (see Decision Framework). Plan visual elements (survival curves, forest plots, decision algorithms)
  4. Draft executive summary first: Write the page-1 summary boxes before detailed sections. This forces clarity about key findings
  5. Author detailed sections: Write each section with proper statistical reporting. For cohort analyses: demographics → biomarkers → outcomes → subgroup comparisons. For recommendations: evidence review → GRADE assessment → recommendations by line → algorithm
  6. Create visual elements: Generate Kaplan-Meier curves, forest plots, waterfall plots, TikZ decision algorithms. Include number-at-risk tables below survival curves
  7. Apply GRADE ratings (recommendations only): Assess each recommendation against evidence quality criteria. Document rationale for each grade
  8. Format in LaTeX/PDF: Apply document template (0.5-inch margins, colored tcolorbox elements, professional tables). Ensure page 1 is executive summary only
  9. Quality check: Verify HIPAA compliance, statistical completeness (all CIs reported), GRADE consistency, reference completeness

Protocol Guidelines

LaTeX Document Setup

CDS documents use specific LaTeX packages and formatting:

  • Margins: 0.5-inch all sides (compact, data-dense)
  • Color boxes: tcolorbox package with color-coded environments
  • Tables: booktabs for professional formatting, longtable for multi-page tables
  • Figures: TikZ for decision algorithms, pgfplots for survival curves
  • First page: \thispagestyle{empty} + executive summary boxes + \newpage
Executive Summary Box Pattern

Each CDS document's page 1 should have 3–5 tcolorbox elements:

  • Report Information (blue): Document type, date, population, methodology
  • Primary Results (blue): Main efficacy findings with key statistics
  • Biomarker Insights (green): Molecular subtype findings or biomarker correlations
  • Clinical Implications (orange): Actionable recommendations or treatment implications
  • Safety/Warnings (red, if applicable): Critical adverse events or contraindications
Biomarker Classification Guide

When stratifying cohorts by biomarkers:

  • Genomic: Mutations (EGFR, KRAS), CNV (HER2 amplification), fusions (ALK, ROS1)
  • Expression: IHC scores (PD-L1 TPS/CPS), RNA-seq signatures
  • Molecular subtypes: Disease-specific (PAM50 breast cancer, GBM clusters)
  • Always specify: assay platform, cut-point, validation status, FDA companion diagnostic approval

Further Reading

  • treatment-plans — individual patient-level care plans (complementary to population-level CDS)
  • scientific-writing — manuscript structure, citation management, reporting guidelines
  • statistical-analysis — detailed statistical methods (Cox regression, Kaplan-Meier, log-rank tests)
  • matplotlib / plotly — figure generation for survival curves, forest plots, waterfall plots

© jaechang-hits, CC-BY-4.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/scientific-writing/clinical-decision-support-documents of jaechang-hits/SciAgent-Skills.

Open the folder on GitHubat commit 82c862c

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in jaechang-hits/SciAgent-Skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Clinical Decision Support Documents next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Clinical Decision Support Documents compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Clinical Decision Support Documents this skilljaechang-hits/SciAgent-Skills3741 repos~3kAutomated safety check: PassCC-BY-4.0
GitHub Deep Researchbytedance/deer-flow84k4 repos~1.3kAutomated safety check: PassMIT
Read arXiv Paperkarpathy/nanochat59k1 repos~494Automated safety check: PassMIT
Clinical Trials Databasegoogle-deepmind/science-skills3.2k2 repos~3.2kAutomated safety check: PassApache-2.0
CHARLS Paper Reproduction Guidexjtulyc/MedgeClaw6171 repos~1.8kAutomated safety check: PassNone
Rebuttal ResponseM1n-n9/paper-lifecycle693—~1.9kAutomated safety check: PassNone

Similar skills

  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    84k GitHub starsUsed in 4 repos~1.3k tokens
    Research & ScienceAuto-check passed
  • Read arXiv Paper

    karpathy/nanochat

    Fetches the TeX source of an arXiv paper from its URL, reads it and writes a markdown summary tied to the nanochat project.

    59k GitHub starsUsed in 1 repo~494 tokens
    Research & ScienceAuto-check passed
  • Clinical Trials Database

    google-deepmind/science-skills

    Query ClinicalTrials.gov via APIv2. An agent skill from google-deepmind/science-skills.

    3.2k GitHub starsUsed in 2 repos~3.2k tokens
    Research & ScienceAuto-check passed
  • Guides an agent through reproducing papers built on the CHARLS health and retirement survey, from variable mapping to cognition, depression and isolation scores.

    617 GitHub starsUsed in 1 repo~1.8k tokens
    Research & ScienceAuto-check passed
  • Rebuttal Response

    M1n-n9/paper-lifecycle

    Plan, triage, and write academic rebuttals and review responses.

    693 GitHub stars~1.9k tokensUpdated 3 mo ago
    Research & ScienceAuto-check passed
  • Daily Paper Digest

    Galaxy-Dawn/claude-scholar

    Finds recent arXiv and bioRxiv papers on a topic, narrows them in stages to one pick per field, and writes bilingual Chinese and English summaries.

    5.7k GitHub stars~1k tokensUpdated 18 days ago
    Research & ScienceAuto-check passed

More from jaechang-hits/SciAgent-Skills

All 169 skills in this repo
  • Neb Irc Activation Energy

    jaechang-hits/SciAgent-Skills

    NEB-IRC activation energy pipeline for reaction barriers using GFN2-xTB and pysisyphus.

    374 GitHub stars~4k tokensUpdated 12 days ago
    Auto-check passed
  • Molecular Visualization 3dmol

    jaechang-hits/SciAgent-Skills

    3Dmol.js WebGL molecular visualization emitted as self-contained HTML.

    374 GitHub stars~3.2k tokensUpdated 12 days ago
    Auto-check passed
  • Cobrapy Metabolic Modeling

    jaechang-hits/SciAgent-Skills

    Constraint-based (COBRA) analysis of genome-scale metabolic models: FBA, FVA, knockouts, flux sampling, production envelopes, gapfilling, media optimization.

    374 GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed
  • Rdkit Chemdraw Cdxml

    jaechang-hits/SciAgent-Skills

    Read, write, and edit ChemDraw CDX/CDXML files with RDKit's rdkit.Chem.rdChemDraw plus direct XML editing, always paired with a rendered PNG.

    374 GitHub stars~6.9k tokensUpdated 12 days ago
    Auto-check passed
  • Pubmed Database

    jaechang-hits/SciAgent-Skills

    Programmatic PubMed access via NCBI E-utilities REST API. An agent skill from jaechang-hits/SciAgent-Skills.

    374 GitHub starsUsed in 1 repo~4.4k tokens
    Auto-check passed
  • Sciagent Skill Creator

    jaechang-hits/SciAgent-Skills

    Scaffold a new SciAgent-Skills entry. An agent skill from jaechang-hits/SciAgent-Skills.

    374 GitHub stars~2.3k tokensUpdated 12 days ago
    Auto-check passed

Questions about Clinical Decision Support Documents

What does Clinical Decision Support Documents do?

Guidelines for clinical decision support (CDS) documents: biomarker-stratified cohort analyses and GRADE-graded treatment reports. Clinical Decision Support Documents is an agent skill from jaechang-hits/SciAgent-Skills. Guidelines for clinical decision support (CDS) documents: biomarker-stratified cohort analyses and GRADE-graded treatment reports.

When should I use Clinical Decision Support Documents?

Clinical Decision Support Documents fits situations like: pharma research docs; clinical guidelines; regulatory submissions.

How do I install Clinical Decision Support Documents in Claude Code?

Run `npx skills add jaechang-hits/SciAgent-Skills --skill clinical-decision-support-documents -a claude-code`. Or copy the skill folder (skills/scientific-writing/clinical-decision-support-documents in jaechang-hits/SciAgent-Skills) into .claude/skills/clinical-decision-support-documents in your project. Claude Code loads it when a task matches its description.

How do I install Clinical Decision Support Documents in Codex?

Run `npx skills add jaechang-hits/SciAgent-Skills --skill clinical-decision-support-documents -a codex`. Or copy the skill folder (skills/scientific-writing/clinical-decision-support-documents in jaechang-hits/SciAgent-Skills) into .agents/skills/clinical-decision-support-documents in your project. Codex loads it when a task matches its description.

Can I use Clinical Decision Support Documents in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jaechang-hits/SciAgent-Skills --skill clinical-decision-support-documents -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clinical-decision-support-documents, .gemini/skills/clinical-decision-support-documents, .github/skills/clinical-decision-support-documents and .opencode/skills/clinical-decision-support-documents in your project.

What does Clinical Decision Support Documents need to run?

SKILL.md names no scripts, command-line tools or credentials: Clinical Decision Support Documents is instructions for the agent only.

Does Clinical Decision Support Documents access the network?

SKILL.md names 5 domains. As links in the text: gdt.gradepro.org, doi.org, consort-statement.org, strobe-statement.org and ich.org. This is read from the text; nothing was executed.

Is Clinical Decision Support Documents safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Clinical Decision Support Documents use?

Clinical Decision Support Documents is published under the CC-BY-4.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Clinical Decision Support Documents use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Clinical Decision Support Documents?

Skills that share tags, products or a category with Clinical Decision Support Documents: GitHub Deep Research (bytedance/deer-flow, 84k stars), Read arXiv Paper (karpathy/nanochat, 59k stars), Clinical Trials Database (google-deepmind/science-skills, 3.2k stars) and CHARLS Paper Reproduction Guide (xjtulyc/MedgeClaw, 617 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Clinical Decision Support Documents?

jaechang-hits (a GitHub user) maintains it in jaechang-hits/SciAgent-Skills, which has 374 GitHub stars. The repository holds 169 skills in this directory. The repository was last updated on September 29, 2026.

Source: jaechang-hits/SciAgent-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.