Generate professional clinical decision support (CDS) documents for pharmaceutical companies, clinical researchers, and medical decision-makers. This skill specializes in analytical, evidence-based documents that inform treatment strategies and drug development:
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionclinical-decision-supportExecute the skills CLI command in your project's root directory to begin installation:
Fetches clinical-decision-support from davila7/claude-code-templates and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate clinical-decision-support. Access via /clinical-decision-support in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
24.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
24.2K
stars
Generate professional clinical decision support (CDS) documents for pharmaceutical companies, clinical researchers, and medical decision-makers. This skill specializes in analytical, evidence-based documents that inform treatment strategies and drug development:
All documents are generated as publication-ready LaTeX/PDF files optimized for pharmaceutical research, regulatory submissions, and clinical guideline development.
Note: For individual patient treatment plans at the bedside, use the treatment-plans skill instead. This skill focuses on group-level analyses and evidence synthesis for pharmaceutical/research settings.
Patient Cohort Analysis
Treatment Recommendation Reports
This skill is specifically designed for pharmaceutical and clinical research applications:
Drug Development
Medical Affairs
Clinical Guidelines
Real-World Evidence
Use this skill when you need to:
Do NOT use this skill for:
treatment-plans skill)treatment-plans skill)treatment-plans skill)⚠️ MANDATORY: Every clinical decision support document MUST include at least 1-2 AI-generated figures using the scientific-schematics skill.
This is not optional. Clinical decision documents require clear visual algorithms. Before finalizing any document:
How to generate figures:
How to generate schematics:
python scripts/generate_schematic.py "your diagram description" -o figures/output.png
The AI will automatically:
When to add schematics:
For detailed guidance on creating schematics, refer to the scientific-schematics skill documentation.
CRITICAL REQUIREMENT: All clinical decision support documents MUST begin with a complete executive summary on page 1 that spans the entire first page before any table of contents or detailed sections.
The first page of every CDS document should contain ONLY the executive summary with the following components:
Required Elements (all on page 1):
Document Title and Type
Report Information Box (using colored tcolorbox)
Key Findings Boxes (3-5 colored boxes using tcolorbox)
Visual Requirements:
\thispagestyle{empty} to remove page numbers from page 1\newpage)\newpage before table of contents or detailed sectionsExample First Page LaTeX Structure:
\maketitle
\thispagestyle{empty}
% Report Information Box
\begin{tcolorbox}[colback=blue!5!white, colframe=blue!75!black, title=Report Information]
\textbf{Document Type:} Patient Cohort Analysis\\
\textbf{Disease State:} HER2-Positive Metastatic Breast Cancer\\
\textbf{Analysis Date:} \today\\
\textbf{Population:} 60 patients, biomarker-stratified by HR status
\end{tcolorbox}
\vspace{0.3cm}
% Key Finding #1: Primary Results
\begin{tcolorbox}[colback=blue!5!white, colframe=blue!75!black, title=Primary Efficacy Results]
\begin{itemize}
\item Overall ORR: 72\% (95\% CI: 59-83\%)
\item Median PFS: 18.5 months (95\% CI: 14.2-22.8)
\item Median OS: 35.2 months (95\% CI: 28.1-NR)
\end{itemize}
\end{tcolorbox}
\vspace{0.3cm}
% Key Finding #2: Biomarker Insights
\begin{tcolorbox}[colback=green!5!white, colframe=green!75!black, title=Biomarker Stratification Findings]
\begin{itemize}
\item HR+/HER2+: ORR 68\%, median PFS 16.2 months
\item HR-/HER2+: ORR 78\%, median PFS 22.1 months
\item HR status significantly associated with outcomes (p=0.041)
\end{itemize}
\end{tcolorbox}
\vspace{0.3cm}
% Key Finding #3: Clinical Implications
\begin{tcolorbox}[colback=orange!5!white, colframe=orange!75!black, title=Clinical Recommendations]
\begin{itemize}
\item Strong efficacy observed regardless of HR status (Grade 1A)
\item HR-/HER2+ patients showed numerically superior outcomes
\item Treatment recommended for all HER2+ MBC patients
\end{itemize}
\end{tcolorbox}
\newpage
\tableofcontents % TOC on page 2
\newpage % Detailed content starts page 3
Page 1 Executive Summary for Treatment Recommendations should include:
Detailed Sections (Page 3+):
MANDATORY FIRST PAGE REQUIREMENT:
Document Specifications:
Visual Elements:
This skill integrates with:
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
davila7/claude-code-templates
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
We added clinical-decision-support from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
clinical-decision-support reduced setup friction for our internal harness; good balance of opinion and flexibility.
clinical-decision-support has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: clinical-decision-support is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: clinical-decision-support is focused, and the summary matches what you get after install.
Registry listing for clinical-decision-support matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: clinical-decision-support is focused, and the summary matches what you get after install.
clinical-decision-support is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: clinical-decision-support is focused, and the summary matches what you get after install.
I recommend clinical-decision-support for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 63