clinical-reports

K-Dense-AI/scientific-agent-skills · updated Jun 4, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/K-Dense-AI/scientific-agent-skills --skill clinical-reports
0 commentsdiscussion
summary

### Clinical Reports

  • name: "clinical-reports"
  • description: "Write comprehensive clinical reports including case reports (CARE guidelines), diagnostic reports (radiology/pathology/lab), clinical trial reports (ICH-E3, SAE, CSR), and patient documentation (SOAP,..."
  • allowed-tools: "Read Write Edit Bash"
skill.md
name
clinical-reports
description
Write comprehensive clinical reports including case reports (CARE guidelines), diagnostic reports (radiology/pathology/lab), clinical trial reports (ICH-E3, SAE, CSR), and patient documentation (SOAP, H&P, discharge summaries). Full support with templates, regulatory compliance (HIPAA, FDA, ICH-GCP), and validation tools.
allowed-tools
Read Write Edit Bash
license
MIT License
metadata
version: "1.0" skill-author: K-Dense Inc.

Clinical Report Writing

Overview

Clinical report writing is the process of documenting medical information with precision, accuracy, and compliance with regulatory standards. This skill covers four major categories of clinical reports: case reports for journal publication, diagnostic reports for clinical practice, clinical trial reports for regulatory submission, and patient documentation for medical records. Apply this skill for healthcare documentation, research dissemination, and regulatory compliance.

Critical Principle: Clinical reports must be accurate, complete, objective, and compliant with applicable regulations (HIPAA, FDA, ICH-GCP). Patient privacy and data integrity are paramount. All clinical documentation must support evidence-based decision-making and meet professional standards.

When to Use This Skill

This skill should be used when:

  • Writing clinical case reports for journal submission (CARE guidelines)
  • Creating diagnostic reports (radiology, pathology, laboratory)
  • Documenting clinical trial data and adverse events
  • Preparing clinical study reports (CSR) for regulatory submission
  • Writing patient progress notes, SOAP notes, and clinical summaries
  • Drafting discharge summaries, H&P documents, or consultation notes
  • Ensuring HIPAA compliance and proper de-identification
  • Validating clinical documentation for completeness and accuracy
  • Preparing serious adverse event (SAE) reports
  • Creating data safety monitoring board (DSMB) reports

Visual Enhancement with Scientific Schematics

⚠️ MANDATORY: Every clinical report MUST include at least 1 AI-generated figure using the scientific-schematics skill.

This is not optional. Clinical reports benefit greatly from visual elements. Before finalizing any document:

  1. Generate at minimum ONE schematic or diagram (e.g., patient timeline, diagnostic algorithm, or treatment workflow)
  2. For case reports: include clinical progression timeline
  3. For trial reports: include CONSORT flow diagram

How to generate figures:

  • Use the scientific-schematics skill to generate AI-powered publication-quality diagrams
  • Simply describe your desired diagram in natural language
  • Nano Banana Pro will automatically generate, review, and refine the schematic

How to generate schematics:

python scripts/generate_schematic.py "your diagram description" -o figures/output.png

The AI will automatically:

  • Create publication-quality images with proper formatting
  • Review and refine through multiple iterations
  • Ensure accessibility (colorblind-friendly, high contrast)
  • Save outputs in the figures/ directory

When to add schematics:

  • Patient case timelines and clinical progression diagrams
  • Diagnostic algorithm flowcharts
  • Treatment protocol workflows
  • Anatomical diagrams for case reports
  • Clinical trial participant flow diagrams (CONSORT)
  • Adverse event classification trees
  • Any complex concept that benefits from visualization

For detailed guidance on creating schematics, refer to the scientific-schematics skill documentation.


Core Capabilities

1. Clinical Case Reports for Journal Publication

Clinical case reports describe unusual clinical presentations, novel diagnoses, or rare complications. They contribute to medical knowledge and are published in peer-reviewed journals.

CARE Guidelines Compliance

The CARE (CAse REport) guidelines provide a standardized framework for case report writing. All case reports should follow this checklist:

Title

  • Include the words "case report" or "case study"
  • Indicate the area of focus
  • Example: "Unusual Presentation of Acute Myocardial Infarction in a Young Patient: A Case Report"

Keywords

  • 2-5 keywords for indexing and searchability
  • Use MeSH (Medical Subject Headings) terms when possible

Abstract (structured or unstructured, 150-250 words)

  • Introduction: What is unique or novel about the case?
  • Patient concerns: Primary symptoms and key medical history
  • Diagnoses: Primary and secondary diagnoses
  • Interventions: Key treatments and procedures
  • Outcomes: Clinical outcome and follow-up
  • Conclusions: Main takeaway or clinical lesson

Introduction

  • Brief background on the medical condition
  • Why this case is novel or important
  • Literature review of similar cases (brief)
  • What makes this case worth reporting

Patient Information

  • Demographics (age, sex, race/ethnicity if relevant)
  • Medical history, family history, social history
  • Relevant comorbidities
  • De-identification: Remove or alter 18 HIPAA identifiers
  • Patient consent: Document informed consent for publication

Clinical Findings

  • Chief complaint and presenting symptoms
  • Physical examination findings
  • Timeline of symptoms (consider timeline figure or table)
  • Relevant clinical observations

Timeline

  • Chronological summary of key events
  • Dates of symptoms, diagnosis, interventions, outcomes
  • Can be presented as a table or figure
  • Example format:
    • Day 0: Initial presentation with symptoms X, Y, Z
    • Day 2: Diagnostic test A performed, revealed finding B
    • Day 5: Treatment initiated with drug C
    • Day 14: Clinical improvement noted
    • Month 3: Follow-up examination shows complete resolution

Diagnostic Assessment

  • Diagnostic tests performed (labs, imaging, procedures)
  • Results and interpretation
  • Differential diagnosis considered
  • Rationale for final diagnosis
  • Challenges in diagnosis

Therapeutic Interventions

  • Medications (names, dosages, routes, duration)
  • Procedures or surgeries performed
  • Non-pharmacological interventions
  • Reasoning for treatment choices
  • Alternative treatments considered

Follow-up and Outcomes

  • Clinical outcome (resolution, improvement, unchanged, worsened)
  • Follow-up duration and frequency
  • Long-term outcomes if available
  • Patient-reported outcomes
  • Adherence to treatment

Discussion

  • Strengths and novelty of the case
  • How this case compares to existing literature
  • Limitations of the case report
  • Potential mechanisms or explanations
  • Clinical implications and lessons learned
  • Unanswered questions or areas for future research

Patient Perspective (optional but encouraged)

  • Patient's experience and viewpoint
  • Impact on quality of life
  • Patient-reported outcomes
  • Quote from patient if appropriate

Informed Consent

  • Statement documenting patient consent for publication
  • If patient deceased or unable to consent, describe proxy consent
  • For pediatric cases, parental/guardian consent
  • Example: "Written informed consent was obtained from the patient for publication of this case report and accompanying images. A copy of the written consent is available for review by the Editor-in-Chief of this journal."

For detailed CARE guidelines, refer to references/case_report_guidelines.md.

Journal-Specific Requirements

Different journals have specific formatting requirements:

  • Word count limits (typically 1500-3000 words)
  • Number of figures/tables allowed
  • Reference style (AMA, Vancouver, APA)
  • Structured vs. unstructured abstract
  • Supplementary materials policies

Check journal instructions for authors before submission.

De-identification and Privacy

18 HIPAA Identifiers to Remove or Alter:

  1. Names
  2. Geographic subdivisions smaller than state
  3. Dates (except year)
  4. Telephone numbers
  5. Fax numbers
  6. Email addresses
  7. Social Security numbers
  8. Medical record numbers
  9. Health plan beneficiary numbers
  10. Account numbers
  11. Certificate/license numbers
  12. Vehicle identifiers and serial numbers
  13. Device identifiers and serial numbers
  14. Web URLs
  15. IP addresses
  16. Biometric identifiers
  17. Full-face photographs
  18. Any other unique identifying characteristic

Best Practices:

  • Use "the patient" instead of names
  • Report age ranges (e.g., "a woman in her 60s") or exact age if relevant
  • Use approximate dates or time intervals (e.g., "3 months prior")
  • Remove institution names unless necessary
  • Blur or crop identifying features in images
  • Obtain explicit consent for any potentially identifying information

2. Clinical Diagnostic Reports

Diagnostic reports communicate findings from imaging studies, pathological examinations, and laboratory tests. They must be clear, accurate, and actionable.

Radiology Reports

Radiology reports follow a standardized structure to ensure clarity and completeness.

Standard Structure:

1. Patient Demographics

  • Patient name (or ID in research contexts)
  • Date of birth or age
  • Medical record number
  • Examination date and time

2. Clinical Indication

  • Reason for examination
  • Relevant clinical history
  • Specific clinical question to be answered
  • Example: "Rule out pulmonary embolism in patient with acute dyspnea"

3. Technique

  • Imaging modality (X-ray, CT, MRI, ultrasound, PET, etc.)
  • Anatomical region examined
  • Contrast administration (type, route, volume)
  • Protocol or sequence used
  • Technical quality and limitations
  • Example: "Contrast-enhanced CT of the chest, abdomen, and pelvis was performed using 100 mL of intravenous iodinated contrast. Oral contrast was not administered."

4. Comparison

  • Prior imaging studies available for comparison
  • Dates of prior studies
  • Stability or change from prior imaging
  • Example: "Comparison: CT chest from [date]"

5. Findings

  • Systematic description of imaging findings
  • Organ-by-organ or region-by-region approach
  • Positive findings first, then pertinent negatives
  • Measurements of lesions or abnormalities
  • Use of standardized terminology (ACR lexicon, RadLex)
  • Example:
    • Lungs: Bilateral ground-glass opacities, predominant in the lower lobes. No consolidation or pleural effusion.
    • Mediastinum: No lymphadenopathy. Heart size normal.
    • Abdomen: Liver, spleen, pancreas unremarkable. No free fluid.

6. Impression/Conclusion

  • Concise summary of key findings
  • Answers to the clinical question
  • Differential diagnosis if applicable
  • Recommendations for follow-up or additional studies
  • Level of suspicion or diagnostic certainty
  • Example:
    • "1. Bilateral ground-glass opacities consistent with viral pneumonia or atypical infection. COVID-19 cannot be excluded. Clinical correlation recommended.
      1. No evidence of pulmonary embolism.
      1. Recommend follow-up imaging in 4-6 weeks to assess resolution."

Structured Reporting:

Many radiology departments use structured reporting templates for common examinations:

  • Lung nodule reporting (Lung-RADS)
  • Breast imaging (BI-RADS)
  • Liver imaging (LI-RADS)
  • Prostate imaging (PI-RADS)
  • CT colonography (C-RADS)

Structured reports improve consistency, reduce ambiguity, and facilitate data extraction.

For radiology reporting standards, see references/diagnostic_reports_standards.md.

Pathology Reports

Pathology reports document microscopic findings from tissue specimens and provide diagnostic conclusions.

Surgical Pathology Report Structure:

1. Patient Information

  • Patient name and identifiers
  • Date of birth, age, sex
  • Ordering physician
  • Medical record number
  • Specimen received date

2. Specimen Information

  • Specimen type (biopsy, excision, resection)
  • Anatomical site
  • Laterality if applicable
  • Number of specimens/blocks/slides
  • Example: "Skin, left forearm, excisional biopsy"

3. Clinical History

  • Relevant clinical information
  • Indication for biopsy
  • Prior diagnoses
  • Example: "History of melanoma. New pigmented lesion, rule out recurrence."

4. Gross Description

  • Macroscopic appearance of specimen
  • Size, weight, color, consistency
  • Orientation markers if present
  • Sectioning and sampling approach
  • Example: "The specimen consists of an ellipse of skin measuring 2.5 x 1.0 x 0.5 cm. A pigmented lesion measuring 0.6 cm in diameter is present on the surface. The specimen is serially sectioned and entirely submitted in cassettes A1-A3."

5. Microscopic Description

  • Histological findings
  • Cellular characteristics
  • Architectural patterns
  • Presence of malignancy
  • Margins if applicable
  • Special stains or immunohistochemistry results

6. Diagnosis

  • Primary diagnosis
  • Grade and stage if applicable (cancer)
  • Margin status
  • Lymph node status if applicable
  • Synoptic reporting for cancers (CAP protocols)
  • Example:
    • "MALIGNANT MELANOMA, SUPERFICIAL SPREADING TYPE
    • Breslow thickness: 1.2 mm
    • Clark level: IV
    • Mitotic rate: 3/mm²
    • Ulceration: Absent
    • Margins: Negative (closest margin 0.4 cm)
    • Lymphovascular invasion: Not identified"

7. Comment (if needed)

  • Additional context or interpretation
  • Differential diagnosis
  • Recommendations for additional studies
  • Clinical correlation suggestions

Synoptic Reporting:

The College of American Pathologists (CAP) provides synoptic reporting templates for cancer specimens. These checklists ensure all relevant diagnostic elements are documented.

Key elements for cancer reporting:

  • Tumor site
  • Tumor size
  • Histologic type
  • Histologic grade
  • Extent of invasion
  • Lymph-vascular invasion
  • Perineural invasion
  • Margins
  • Lymph nodes (number examined, number positive)
  • Pathologic stage (TNM classification)
  • Ancillary studies (molecular markers, biomarkers)

Laboratory Reports

Laboratory reports communicate test results for clinical specimens (blood, urine, tissue, etc.).

Standard Components:

1. Patient and Specimen Information

  • Patient identifiers
  • Specimen type (blood, serum, urine, CSF, etc.)
  • Collection date and time
  • Received date and time
  • Ordering provider

2. Test Name and Method

  • Full test name
  • Methodology (immunoassay, spectrophotometry, PCR, etc.)
  • Laboratory accession number

3. Results

  • Quantitative or qualitative result
  • Units of measurement
  • Reference range (normal values)
  • Flags for abnormal values (H = high, L = low)
  • Critical values highlighted
  • Example:
    • Hemoglobin: 8.5 g/dL (L) [Reference: 12.0-16.0 g/dL]
    • White Blood Cell Count: 15.2 x10³/μL (H) [Reference: 4.5-11.0 x10³/μL]

4. Interpretation (when applicable)

  • Clinical significance of results
  • Suggested follow-up or additional testing
  • Correlation with diagnosis
  • Drug levels and therapeutic ranges

5. Quality Control Information

  • Specimen adequacy
  • Specimen quality issues (hemolyzed, lipemic, clotted)
  • Delays in processing
  • Technical limitations

Critical Value Reporting:

  • Life-threatening results require immediate notification
  • Examples: glucose <40 or >500 mg/dL, potassium <2.5 or >6.5 mEq/L
  • Document notification time and recipient

For laboratory standards and terminology, see references/diagnostic_reports_standards.md.

3. Clinical Trial Reports

Clinical trial reports document the conduct, results, and safety of clinical research studies. These reports are essential for regulatory submissions and scientific publication.

Serious Adverse Event (SAE) Reports

SAE reports document unexpected serious adverse reactions during clinical trials. Regulatory requirements mandate timely reporting to IRBs, sponsors, and regulatory agencies.

Definition of Serious Adverse Event: An adverse event is serious if it:

  • Results in death
  • Is life-threatening
  • Requires inpatient hospitalization or prolongation of existing hospitalization
  • Results in persistent or significant disability/incapacity
  • Is a congenital anomaly/birth defect
  • Requires intervention to prevent permanent impairment or damage

SAE Report Components:

1. Study Information

  • Protocol number and title
  • Study phase
  • Sponsor name
  • Principal investigator
  • IND/IDE number (if applicable)
  • Clinical trial registry number (NCT number)

2. Patient Information (De-identified)

  • Subject ID or randomization number
  • Age, sex, race/ethnicity
  • Study arm or treatment group
  • Date of informed consent
  • Date of first study intervention

3. Event Information

  • Event description (narrative)
  • Date of onset
  • Date of resolution (or ongoing)
  • Severity (mild, moderate, severe)
  • Seriousness criteria met
  • Outcome (recovered, recovering, not recovered, fatal, unknown)

4. Causality Assessment

  • Relationship to study intervention (unrelated, unlikely, possible, probable, definite)
  • Relationship to study procedures
  • Relationship to underlying disease
  • Rationale for causality determination

5. Action Taken

  • Modification of study intervention (dose reduction, temporary hold, permanent discontinuation)
  • Concomitant medications or treatments administered
  • Hospitalization details
  • Outcome and follow-up plan

6. Expectedness

  • Expected per protocol or investigator's brochure
  • Unexpected event requiring expedited reporting
  • Comparison to known safety profile

7. Narrative

  • Detailed description of the event
  • Timeline of events
  • Clinical course and management
  • Laboratory and diagnostic test results
  • Final diagnosis or conclusion

8. Reporter Information

  • Name and contact of reporter
  • Report date
  • Signature

Regulatory Timelines:

  • Fatal or life-threatening unexpected SAEs: 7 days for preliminary report, 15 days for complete report
  • Other serious unexpected events: 15 days
  • IRB notification: per institutional policy, typically within 5-10 days

For detailed SAE reporting guidance, see references/clinical_trial_reporting.md.

Clinical Study Reports (CSR)

Clinical study reports are comprehensive documents summarizing the design, conduct, and results of clinical trials. They are submitted to regulatory agencies as part of drug approval applications.

ICH-E3 Structure:

The ICH E3 guideline defines the structure and content of clinical study reports.

Main Sections:

1. Title Page

  • Study title and protocol number
  • Sponsor and investigator information
  • Report date and version

2. Synopsis (5-15 pages)

  • Brief summary of entire study
  • Objectives, methods, results, conclusions
  • Key efficacy and safety findings
  • Can stand alone

3. Table of Contents

4. List of Abbreviations and Definitions

5. Ethics (Section 2)

  • IRB/IEC approvals
  • Informed consent process
  • GCP compliance statement

6. Investigators and Study Administrative Structure (Section 3)

  • List of investigators and sites
  • Study organization
  • Monitoring and quality assurance

7. Introduction (Section 4)

  • Background and rationale
  • Study objectives and purpose

8. Study Objectives and Plan (Section 5)

  • Overall design and plan
  • Objectives (primary and secondary)
  • Endpoints (efficacy and safety)
  • Sample size determination

9. Study Patients (Section 6)

  • Inclusion and exclusion criteria
  • Patient disposition
  • Protocol deviations
  • Demographic and baseline characteristics

10. Efficacy Evaluation (Section 7)

  • Data sets analyzed (ITT, PP, safety)
  • Demographic and other baseline characteristics
  • Efficacy results for primary and secondary endpoints
  • Subgroup analyses
  • Dropouts and missing data

11. Safety Evaluation (Section 8)

  • Extent of exposure
  • Adverse events (summary tables)
  • Serious adverse events (narratives)
  • Laboratory values
  • Vital signs and physical findings
  • Deaths and other serious events

12. Discussion and Overall Conclusions (Section 9)

  • Interpretation of results
  • Benefit-risk assessment
  • Clinical implications

13. Tables, Figures, and Graphs (Section 10)

14. Reference List (Section 11)

15. Appendices (Section 12)

  • Study protocol and amendments
  • Sample case report forms
  • List of investigators and ethics committees
  • Patient information and consent forms
  • Investigator's brochure references
  • Publications based on the study

Key Principles:

  • Objectivity and transparency
  • Comprehensive data presentation
  • Adherence to statistical analysis plan
  • Clear presentation of safety data
  • Integration of appendices

For ICH-E3 templates and detailed guidance, see references/clinical_trial_reporting.md and assets/clinical_trial_csr_template.md.

Protocol Deviations

Protocol deviations are departures from the approved study protocol. They must be documented, assessed, and reported.

Categories:

  • Minor deviation: Does not significantly impact patient safety or data integrity
  • Major deviation: May impact patient safety, data integrity, or study conduct
  • Violation: Serious deviation requiring immediate action and reporting

Documentation Requirements:

  • Description of deviation
  • Date of occurrence
  • Subject ID affected
  • Impact on safety and data
  • Corrective and preventive actions (CAPA)
  • Root cause analysis
  • Preventive measures implemented

4. Patient Clinical Documentation

Patient documentation records clinical encounters, progress, and care plans. Accurate documentation supports continuity of care, billing, and legal protection.

SOAP Notes

SOAP notes are the most common format for progress notes in clinical practice.

Structure:

S - Subjective

  • Patient's reported symptoms and concerns
  • History of present illness (HPI)
  • Review of systems (ROS) relevant to visit
  • Patient's own words (use quotes when helpful)
  • Example: "Patient reports worsening shortness of breath over the past 3 days, particularly with exertion. Denies chest pain, fever, or cough."

O - Objective

  • Measurable clinical findings
  • Vital signs (temperature, blood pressure, heart rate, respiratory rate, oxygen saturation)
  • Physical examination findings (organized by system)
  • Laboratory and imaging results
  • Example:
    • Vitals: T 98.6°F, BP 142/88, HR 92, RR 22, SpO2 91% on room air
    • General: Mild respiratory distress
    • Cardiovascular: Regular rhythm, no murmurs
    • Pulmonary: Bilateral crackles at bases
    • Extremities: 2+ pitting edema bilaterally

A - Assessment

  • Clinical impression or diagnosis
  • Differential diagnosis
  • Severity and stability
  • Progress toward treatment goals
  • Example:
    • "1. Acute decompensated heart failure, NYHA Class III
      1. Hypertension, poorly controlled
      1. Chronic kidney disease, stage 3"

P - Plan

  • Diagnostic plan (further testing)
  • Therapeutic plan (medications, procedures)
  • Patient education and counseling
  • Follow-up arrangements
  • Example:
    • "Diagnostics: BNP, chest X-ray, echocardiogram
    • Therapeutics: Increase furosemide to 40 mg PO BID, continue lisinopril 10 mg daily, strict fluid restriction to 1.5 L/day
    • Education: Signs of worsening heart failure, daily weights
    • Follow-up: Cardiology appointment in 1 week, call if weight gain >2 lbs in 1 day"

Documentation Tips:

  • Be concise but complete
  • Use standard medical abbreviations
  • Document time of encounter
  • Sign and date all notes
  • Avoid speculation or judgment
  • Document medical necessity for billing
  • Include patient's response to treatment

For SOAP note templates and examples, see assets/soap_note_template.md.

History and Physical (H&P)

The H&P is a comprehensive assessment performed at admission or initial encounter.

Components:

1. Chief Complaint (CC)

  • Brief statement of why patient is seeking care
  • Use patient's own words
  • Example: "Chest pain for 2 hours"

2. History of Present Illness (HPI)

  • Detailed chronological narrative of current problem
  • Use OPQRST mnemonic for pain:
    • Onset: When did it start?
    • Provocation/Palliation: What makes it better or worse?
    • Quality: What does it feel like?
    • Region/Radiation: Where is it? Does it spread?
    • Severity: How bad is it (0-10 scale)?
    • Timing:
how to use clinical-reports

How to use clinical-reports on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add clinical-reports
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/K-Dense-AI/scientific-agent-skills --skill clinical-reports

The skills CLI fetches clinical-reports from GitHub repository K-Dense-AI/scientific-agent-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/clinical-reports

Reload or restart Cursor to activate clinical-reports. Access the skill through slash commands (e.g., /clinical-reports) or your agent's skill management interface.

Security & Verification Notice

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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.736 reviews
  • Aanya Rahman· Dec 24, 2024

    I recommend clinical-reports for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Sakura Sharma· Dec 4, 2024

    Useful defaults in clinical-reports — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Hiroshi Sethi· Nov 23, 2024

    clinical-reports has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Ishan Mensah· Nov 19, 2024

    Registry listing for clinical-reports matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Noah Ghosh· Nov 15, 2024

    Solid pick for teams standardizing on skills: clinical-reports is focused, and the summary matches what you get after install.

  • Ishan Singh· Oct 14, 2024

    Solid pick for teams standardizing on skills: clinical-reports is focused, and the summary matches what you get after install.

  • Yusuf Brown· Oct 10, 2024

    clinical-reports reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Kiara Jain· Oct 6, 2024

    clinical-reports has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Benjamin Agarwal· Sep 25, 2024

    clinical-reports fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Oshnikdeep· Sep 9, 2024

    We added clinical-reports from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

showing 1-10 of 36

1 / 4