clinical-reports

davila7/claude-code-templates · updated Apr 8, 2026

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

$npx skills add https://github.com/davila7/claude-code-templates --skill clinical-reports
0 commentsdiscussion
summary

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.

skill.md

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

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/davila7/claude-code-templates --skill clinical-reports

The skills CLI fetches clinical-reports from GitHub repository davila7/claude-code-templates 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

User Story & Requirements Generation

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

Competitive Analysis

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

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

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

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ 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.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

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

Ratings

4.748 reviews
  • Li Ramirez· Dec 28, 2024

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

  • Valentina Srinivasan· Dec 20, 2024

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

  • Shikha Mishra· Dec 12, 2024

    clinical-reports is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Nia Perez· Dec 4, 2024

    Keeps context tight: clinical-reports is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Min Gupta· Nov 23, 2024

    clinical-reports is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Maya Mensah· Nov 19, 2024

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

  • Aanya Rahman· Nov 11, 2024

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

  • Noor Gupta· Nov 7, 2024

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

  • Yash Thakker· Nov 3, 2024

    Keeps context tight: clinical-reports is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Chen Lopez· Oct 26, 2024

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

showing 1-10 of 48

1 / 5