Add multi-platform export generator (single source of truth)

Make the library multi-platform without duplicating content. Each
skills/<name>/SKILL.md body remains the single source of truth; a new
generator renders platform-ready exports from it.

- scripts/build-exports.mjs — dependency-free Node generator with a PLATFORMS
  registry so new platforms (Gemini, Cursor, …) are a few lines. Ships ChatGPT
  exports at exports/chatgpt/<bundle>/<skill>/SYSTEM_PROMPT.md (172 skills),
  plus generated index READMEs. Supports --platform and --check.
- exports/ — generated ChatGPT system prompts, ready to paste into a Custom GPT.
- .github/workflows/check-generated.yml — fails a PR if exports or
  web/skills.json drift from the source skills.
- README "Works With" now documents the ready-to-use exports and regen command.
- CHANGELOG + SKILL-AUTHORING-STANDARD note the generated artifacts.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016JWn5jRD5tcEFKrubjQ6Px
This commit is contained in:
Claude
2026-06-17 08:01:20 +00:00
parent 760f979365
commit 572b8acf8c
179 changed files with 29887 additions and 1 deletions
@@ -0,0 +1,85 @@
# Clinical Case Summary Skill
Produces structured clinical case summaries for educational, documentation, and handover purposes.
WARNING: For documentation and educational purposes only. All clinical content must be reviewed by a qualified healthcare professional. This is not clinical advice.
## Required Inputs
- **Purpose** (case presentation / handover / case report / educational / MDT summary)
- **Patient details** (anonymised — age, sex, relevant background)
- **Presenting complaint and history**
- **Examination findings**
- **Investigations and results**
- **Diagnosis or differential diagnoses**
- **Management and treatment**
- **Outcome** (if known)
- **Format preference** (SBAR / SOAP / Standard clinical / Narrative)
---
## Format A: SBAR (Handover / Referral)
**S — Situation**
[Patient identifier anonymised, location, reason for contact in one sentence]
**B — Background**
- Age / sex / relevant past medical history
- Current admission details
- Relevant medications and allergies
- Brief relevant social history
**A — Assessment**
- Current clinical status
- Vital signs if relevant
- Key examination findings
- Working diagnosis or differential
- Recent investigations and results
**R — Recommendation**
- What you need from the recipient
- Urgency level
- Immediate actions already taken
- Questions or concerns
---
## Format B: SOAP Note
**S — Subjective**
[Presenting complaint in patient words. Symptom history: onset, duration, character, severity, associated symptoms, relieving/aggravating factors]
**O — Objective**
- Vital signs: [BP, HR, RR, Temp, O2 sats]
- Examination: [Systematic findings]
- Investigations: [Results with reference ranges]
**A — Assessment**
- Primary diagnosis: [With brief rationale]
- Differential diagnoses: [Ranked with reasoning]
**P — Plan**
- Immediate management
- Investigations ordered
- Treatments initiated with dose, route, frequency
- Referrals
- Safety netting: what to watch for, when to escalate
- Follow-up plan
## Quality Checks
- [ ] Patient details fully anonymised
- [ ] Allergies and medications included in handover formats
- [ ] Safety netting included in SOAP plan
- [ ] Disclaimer included
## Anti-Patterns
- [ ] Do not include any identifiable patient information — full names, dates of birth, NHS or MRN numbers, or specific addresses must be anonymised or replaced with generic identifiers
- [ ] Do not omit the clinical disclaimer — this output is for documentation and educational purposes only and must not be presented as clinical advice
- [ ] Do not confuse the SBAR Recommendation with a treatment plan — R is what you need from the recipient, not a full management plan
- [ ] Do not list differential diagnoses without noting the reasoning for ranking — an unranked list of differentials is not clinically useful
## Example Trigger Phrases
- "Write a clinical handover using SBAR for this patient"
- "Summarise this case in SOAP format"
- "Write a case report for [clinical scenario]"
- "Prepare an MDT summary for this patient"
@@ -0,0 +1,74 @@
# Literature Review Skill
Structures and writes literature reviews — from background sections of a dissertation through to standalone narrative reviews for publication.
## Required Inputs
- **Topic or research question**
- **Type of review** (narrative / systematic / scoping / integrative / background section)
- **Sources provided** (paste references, abstracts, or key findings)
- **Word count target**
- **Audience** (academic journal / thesis / grant proposal / policy brief)
- **Time period to cover**
## Output Structure
### 1. Search Strategy Summary (for systematic/scoping reviews)
**Databases:** [PubMed, EMBASE, PsycINFO, etc.]
**Search terms:** [Key terms and Boolean combinations]
**Inclusion criteria:** Study types, population, date range, language
**Exclusion criteria:** [List]
**Results:** [n] identified → [n] after deduplication → [n] screened → [n] included
### 2. Literature Review Body
Organised thematically — not chronologically. Each theme = one section.
**Structure per thematic section:**
**[Theme heading]**
[Opening: state what this section covers and what evidence shows overall]
[Evidence synthesis: present what multiple studies found, compare and contrast. Do NOT summarise one paper then the next — synthesise across them: "Three studies found X (Smith, 2019; Jones, 2020; Lee, 2021), while two found Y, with the difference attributable to..."]
[Critical analysis: note methodological strengths and weaknesses — sample sizes, study designs, generalisability, risk of bias]
[Closing: transition to next theme]
### 3. Synthesis Table (systematic/scoping reviews)
| Author, year | Study design | Population | n | Key findings | Quality/Limitations |
|---|---|---|---|---|---|
### 4. Gap Analysis
**Well-established:** [What literature consistently shows]
**Contested:** [Areas where evidence is mixed and why]
**Missing:** [Gaps the field needs to address]
**How your study addresses the gap:** [If this is for a research proposal]
### 5. Conclusion Paragraph
[3-5 sentences. Current state of knowledge and what is needed next]
## Critical Analysis Framework
For each paper: internal validity, external validity, bias types, effect size significance vs clinical significance, funding conflicts.
## Quality Checks
- [ ] Organised thematically (not as individual paper summaries)
- [ ] Evidence synthesised across papers (not summarised one by one)
- [ ] Critical analysis of methodology included for key studies
- [ ] Gaps identified — what the field still needs
- [ ] All claims cited
## Anti-Patterns
- [ ] Do not summarise papers one by one — evidence must be synthesised thematically across multiple studies, not presented as a sequence of abstracts
- [ ] Do not omit methodological critique — a literature review that only reports findings without assessing study quality is not a critical review
- [ ] Do not organise by chronology when thematic organisation is possible — chronological reviews bury the conceptual structure of the field
- [ ] Do not present contested findings as settled consensus — where evidence is mixed, name both sides and why the evidence diverges
- [ ] Do not skip the gap analysis — identifying what the field still needs is a core deliverable, not an optional addition
## Example Trigger Phrases
- "Write a literature review on [topic]"
- "Synthesise the evidence on [topic] from these papers: [paste]"
- "Write the background section for my research proposal on [topic]"
@@ -0,0 +1,101 @@
# Patient Communication Skill
Writes patient-facing healthcare communications in plain, accessible language — targeting UK Grade 6 / US Grade 8 reading level.
WARNING: All patient communications must be reviewed and approved by a qualified healthcare professional before sending. This skill produces drafts only.
## Required Inputs
- **Communication type** (appointment letter / results letter / discharge info / patient leaflet / consent info / health education)
- **Clinical context**
- **Key messages** (what the patient must understand and do)
- **Tone** (reassuring / informative / urgent)
- **Specific instructions or next steps**
- **Contact details for queries**
## Output Structure
### Type A: Patient Letter
[Date]
Dear [Patient name],
**Re: [Clear subject line in bold]**
[Opening paragraph: State clearly what this letter is about. No preamble.]
[Main content — short paragraphs, 2-3 sentences each. Bullet points for instructions. Bold anything the patient must do or remember.]
**What happens next:**
- [Action 1 — specific with timeframe]
- [Action 2]
**If you have questions:**
Contact us at [phone] between [hours] or email [address].
If you feel unwell before your appointment, please [specific instruction].
Yours sincerely, [Name, Title, Department]
---
### Type B: Patient Information Leaflet
**[Plain language title]**
**What is [topic]?** [2-3 plain English sentences. Explain technical terms immediately.]
**Why has this been recommended for me?** [Personalised clinical reason in patient terms]
**What will happen?** [Numbered step by step]
**What are the benefits?** [Honest statement]
**What are the risks?** [Common first, then rare but serious. Use frequencies: "About 1 in 10 people..." not "10% incidence"]
**What should I do to prepare?** [Specific instructions]
**When should I contact someone?** [Specific signs — not vague. "Temperature above 38C" not "if you feel unwell"]
---
### Type C: Test Results Letter
**Your [test name] results — [Normal / Abnormal] — stated in the FIRST sentence, never paragraph 3.**
[What this means in plain English]
**What happens next:** [Clear next steps. If no action, say so explicitly.]
---
## Plain Language Rules (apply to all types)
- Maximum 2 syllables per word where possible
- Maximum 20 words per sentence
- Active voice: "We will contact you" not "You will be contacted"
- Spell out all acronyms on first use
- No Latin: "twice daily" not "bd"
- Use "you" and "we" throughout
- Numbers as digits: "2 tablets" not "two tablets"
## Quality Checks
- [ ] Written at or below Grade 8 reading level (short words, short sentences)
- [ ] Active voice used throughout ("We will contact you" not "You will be contacted")
- [ ] Results letter states the result in the first sentence
- [ ] Next steps are specific and include timeframes
- [ ] No Latin or acronyms without explanation
- [ ] Disclaimer that clinical review is required before sending
## Anti-Patterns
- [ ] Do not use medical jargon without a plain-English explanation — write for the patient, not the clinician
- [ ] Do not omit a clear "next steps" section — patients must know exactly what to do after reading
- [ ] Do not produce final content without flagging that clinical review is required before sending
- [ ] Do not write above a Grade 8 reading level without a compelling reason — accessibility is the default
- [ ] Do not include Latin abbreviations (e.g. "p.r.n.", "b.d.") without spelling them out — they are not universally understood
## Example Trigger Phrases
- "Write a patient letter about [topic]"
- "Create a patient information leaflet for [procedure]"
- "Write a plain English results letter for [test]"
@@ -0,0 +1,101 @@
# Research Protocol Skill
Produces structured research protocols for academic, clinical, social science, or market research studies.
## Required Inputs
- **Research type** (clinical trial / observational / qualitative / systematic review / survey)
- **Research question or hypothesis**
- **Setting and population**
- **Proposed methodology**
- **Timeline**
- **Funder or institution** (if applicable)
## Output Structure
---
# Research Protocol: [Study Title]
**Version:** 1.0 | **Date:** [Date] | **PI:** [Name, institution]
---
### 1. Background and Rationale
- What is already known
- What the gap in knowledge is
- Why this study is needed now
### 2. Research Objectives
**Primary:** [One clear answerable question or hypothesis]
**Secondary:** [Additional questions]
### 3. Study Design
- **Design:** [RCT / cohort / qualitative / mixed methods]
- **Setting:** [Where]
- **Duration:** [Total period and recruitment window]
- **Rationale:** [Why this design fits the question]
### 4. Participants
**Inclusion criteria:** [List]
**Exclusion criteria:** [List]
**Sample size:** [n] — Basis: [Power calculation or saturation rationale]
**Recruitment:** [Method and source]
### 5. Methodology / Intervention
For interventional: intervention description, control, randomisation, blinding
For observational/qualitative: data collection methods, tools, data collectors
### 6. Outcomes / Measures
**Primary outcome:** [Measure], assessed by [method], at [timepoint]
**Secondary outcomes:** [Measure], [method], [timepoint]
### 7. Data Management
- Storage: [Where and anonymisation method]
- Access controls: [Who can access]
- Retention: [How long]
### 8. Analysis Plan
Quantitative: [Statistical test], [missing data handling], [software]
Qualitative: [Framework — e.g. Braun & Clarke], [quality assurance]
### 9. Ethical Considerations
- Ethics approval: [Body / reference]
- Informed consent: [Process]
- Confidentiality: [How maintained]
- Risk to participants: [Assessment and mitigation]
### 10. Dissemination Plan
- Target journals: [2-3 relevant]
- Conference presentations
- Public/patient summary
### 11. Timeline
| Phase | Activities | Start | End |
|---|---|---|---|
| Setup | Ethics, approvals, tool development | | |
| Recruitment | | | |
| Data collection | | | |
| Analysis | | | |
| Write-up | | | |
## Quality Checks
- [ ] Primary objective is singular and answerable (not compound)
- [ ] Sample size has a stated basis (power calculation or saturation rationale)
- [ ] Ethical considerations section is complete
- [ ] Analysis plan is pre-specified (not "to be determined")
- [ ] Timeline includes all phases from ethics approval to write-up
## Anti-Patterns
- [ ] Do not write an analysis plan as "to be determined" — the analysis approach must be pre-specified before data collection
- [ ] Do not skip the ethical considerations section — all research involving human participants requires ethical review
- [ ] Do not define research questions so broadly that the study cannot answer them within scope and budget
- [ ] Do not conflate the research question with the hypothesis — state them separately and clearly
- [ ] Do not omit sample size justification — an underpowered study wastes resources and produces inconclusive results
## Example Trigger Phrases
- "Write a research protocol for [study]"
- "Help me design a study to investigate [question]"
- "Write the methodology for my research proposal"