Source: https://github.com/aipoch/medical-research-skills
Survival Analysis (Kaplan-Meier)
Kaplan-Meier survival analysis tool for clinical and biological research. Generates publication-ready survival curves with statistical tests.
When to Use
- Use this skill when the task needs Kaplan-Meier survival analysis tool for clinical and biological research. Generates publication-ready survival curves with statistical tests.
- Use this skill for data analysis tasks that require explicit assumptions, bounded scope, and a reproducible output format.
- Use this skill when you need a documented fallback path for missing inputs, execution errors, or partial evidence.
Key Features
See ## Features above for related details.
- Scope-focused workflow aligned to: Kaplan-Meier survival analysis tool for clinical and biological research. Generates publication-ready survival curves with statistical tests.
- Packaged executable path(s):
scripts/main.py.
- Reference material available in
references/ for task-specific guidance.
- Structured execution path designed to keep outputs consistent and reviewable.
Dependencies
lifelines: Core survival analysis library
matplotlib, seaborn: Visualization
pandas, numpy: Data handling
scipy: Statistical tests
Example Usage
See ## Usage above for related details.
cd "20260318/scientific-skills/Data Analytics/survival-analysis-km"
python -m py_compile scripts/main.py
python scripts/main.py --help
Example run plan:
- Confirm the user input, output path, and any required config values.
- Edit the in-file
CONFIG block or documented parameters if the script uses fixed settings.
- Run
python scripts/main.py with the validated inputs.
- Review the generated output and return the final artifact with any assumptions called out.
Implementation Details
See ## Workflow above for related details.
- Execution model: validate the request, choose the packaged workflow, and produce a bounded deliverable.
- Input controls: confirm the source files, scope limits, output format, and acceptance criteria before running any script.
- Primary implementation surface:
scripts/main.py.
- Reference guidance:
references/ contains supporting rules, prompts, or checklists.
- Parameters to clarify first: input path, output path, scope filters, thresholds, and any domain-specific constraints.
- Output discipline: keep results reproducible, identify assumptions explicitly, and avoid undocumented side effects.
Quick Check
Use this command to verify that the packaged script entry point can be parsed before deeper execution.
python -m py_compile scripts/main.py
Audit-Ready Commands
Use these concrete commands for validation. They are intentionally self-contained and avoid placeholder paths.
python -m py_compile scripts/main.py
# Example invocation: python scripts/main.py --help
# Example invocation: python scripts/main.py --input "Audit validation sample with explicit symptoms, history, assessment, and next-step plan."
Workflow
- Confirm the user objective, required inputs, and non-negotiable constraints before doing detailed work.
- Validate that the request matches the documented scope and stop early if the task would require unsupported assumptions.
- Use the packaged script path or the documented reasoning path with only the inputs that are actually available.
- Return a structured result that separates assumptions, deliverables, risks, and unresolved items.
- If execution fails or inputs are incomplete, switch to the fallback path and state exactly what blocked full completion.
Features
- Kaplan-Meier Curve Generation: Publication-quality survival plots with confidence intervals
- Statistical Tests: Log-rank test, Wilcoxon test, Peto-Peto test
- Hazard Ratios: Cox proportional hazards regression with 95% CI
- Summary Statistics: Median survival time, restricted mean survival time (RMST)
- Multi-group Analysis: Supports 2+ comparison groups
- Risk Tables: Optional at-risk table below curves
Usage
Python Script
# Example invocation: python scripts/main.py --input data.csv --time time_col --event event_col --group group_col --output results/
Arguments
| Argument |
Description |
Required |
--input |
Input CSV file path |
Yes |
--time |
Column name for survival time |
Yes |
--event |
Column name for event indicator (1=event, 0=censored) |
Yes |
--group |
Column name for grouping variable |
Optional |
--output |
Output directory for results |
Yes |
--conf-level |
Confidence level (default: 0.95) |
Optional |
--risk-table |
Include risk table in plot |
Optional |
Input Format
CSV with columns:
- Time column: Numeric, time to event or censoring
- Event column: Binary (1 = event occurred, 0 = censored/right-censored)
- Group column: Categorical variable for stratification
Example:
patient_id,time_months,death,treatment_group
P001,24.5,1,Drug_A
P002,36.2,0,Drug_A
P003,18.7,1,Placebo
Output Files
km_curve.png: Kaplan-Meier survival curve
km_curve.pdf: Vector version for publications
survival_stats.csv: Statistical summary (median survival, confidence intervals)
hazard_ratios.csv: Cox regression results with HR and 95% CI
- `logrank_test.csv**: Pairwise comparison p-values
- `report.txt**: Human-readable summary report
Technical Details
Statistical Methods
Kaplan-Meier Estimator: Non-parametric maximum likelihood estimate of survival function
- Product-limit estimator: Ŝ(t) = Π(tᵢ≤t) (1 - dᵢ/nᵢ)
- Greenwood's formula for variance estimation
Log-Rank Test: Most widely used test for comparing survival curves
- Null hypothesis: No difference between groups
- Weighted by number at risk at each event time
Cox Proportional Hazards: Semi-parametric regression model
- h(t|X) = h₀(t) × exp(β₁X₁ + β₂X₂ + ...)
- Proportional hazards assumption checked via Schoenfeld residuals
Technical Difficulty: High ⚠️
This skill involves advanced statistical modeling. Results should be reviewed by a biostatistician, especially for:
- Proportional hazards assumption violations
- Small sample sizes (< 30 per group)
- Heavy censoring (> 50%)
- Time-varying covariates
References
See references/ folder for:
- Kaplan EL, Meier P (1958) original paper
- Cox DR (1972) regression models paper
- Sample datasets for testing
- Clinical reporting guidelines (ATN, CONSORT)
Parameters
| Parameter |
Type |
Default |
Description |
--input |
str |
Required |
Input CSV file path |
--time |
str |
Required |
Column name for survival time |
--event |
str |
Required |
|
--group |
str |
Required |
|
--output |
str |
Required |
Output directory for results |
--conf-level |
float |
0.95 |
|
--risk-table |
str |
Required |
Include risk table in plot |
--figsize |
str |
'10 |
|
--dpi |
int |
300 |
|
Example
# Basic survival curve
# Example invocation: python scripts/main.py \
--input clinical_data.csv \
--time overall_survival_months \
--event death \
--group treatment_arm \
--output ./results/ \
--risk-table
Output includes:
- Survival curves with 95% confidence bands
- Median survival: Drug A = 28.4 months (95% CI: 24.1-32.7), Placebo = 18.2 months (95% CI: 15.3-21.1)
- Log-rank test p-value: 0.0023
- Hazard ratio: 0.62 (95% CI: 0.45-0.85), p = 0.003
Risk Assessment
| Risk Indicator |
Assessment |
Level |
| Code Execution |
Python/R scripts executed locally |
Medium |
| Network Access |
No external API calls |
Low |
| File System Access |
Read input files, write output files |
Medium |
| Instruction Tampering |
Standard prompt guidelines |
Low |
| Data Exposure |
Output files saved to workspace |
Low |
Security Checklist
Prerequisites
# Python dependencies
pip install -r requirements.txt
Evaluation Criteria
Success Metrics
Test Cases
- Basic Functionality: Standard input → Expected output
- Edge Case: Invalid input → Graceful error handling
- Performance: Large dataset → Acceptable processing time
Lifecycle Status
- Current Stage: Draft
- Next Review Date: 2026-03-06
- Known Issues: None
- Planned Improvements:
- Performance optimization
- Additional feature support
Output Requirements
Every final response should make these items explicit when they are relevant:
- Objective or requested deliverable
- Inputs used and assumptions introduced
- Workflow or decision path
- Core result, recommendation, or artifact
- Constraints, risks, caveats, or validation needs
- Unresolved items and next-step checks
Error Handling
- If required inputs are missing, state exactly which fields are missing and request only the minimum additional information.
- If the task goes outside the documented scope, stop instead of guessing or silently widening the assignment.
- If
scripts/main.py fails, report the failure point, summarize what still can be completed safely, and provide a manual fallback.
- Do not fabricate files, citations, data, search results, or execution outcomes.
Input Validation
This skill accepts requests that match the documented purpose of survival-analysis-km and include enough context to complete the workflow safely.
Do not continue the workflow when the request is out of scope, missing a critical input, or would require unsupported assumptions. Instead respond:
survival-analysis-km only handles its documented workflow. Please provide the missing required inputs or switch to a more suitable skill.
Response Template
Use the following fixed structure for non-trivial requests:
- Objective
- Inputs Received
- Assumptions
- Workflow
- Deliverable
- Risks and Limits
- Next Checks
If the request is simple, you may compress the structure, but still keep assumptions and limits explicit when they affect correctness.
Inputs to Collect
- Required inputs: the user goal, the primary data or source file, and the requested output format.
- Optional inputs: output directory, formatting preferences, and validation constraints.
- If a required input is unavailable, return a short clarification request before continuing.
Output Contract
- Return a short summary, the main deliverables, and any assumptions that materially affect interpretation.
- If execution is partial, label what succeeded, what failed, and the next safe recovery step.
- Keep the final answer within the documented scope of the skill.
Validation and Safety Rules
- Validate identifiers, file paths, and user-provided parameters before execution.
- Do not fabricate results, metrics, citations, or downstream conclusions.
- Use safe fallback behavior when dependencies, credentials, or required inputs are missing.
- Surface any execution failure with a concise diagnosis and recovery path.
1---2name: survival-analysis-km3description: Kaplan-Meier survival analysis tool for clinical and biological research. Generates publication-ready survival curves with statistical tests.4license: MIT5---6> **Source**: [https://github.com/aipoch/medical-research-skills](https://github.com/aipoch/medical-research-skills)
7
8# Survival Analysis (Kaplan-Meier)
9
10Kaplan-Meier survival analysis tool for clinical and biological research. Generates publication-ready survival curves with statistical tests.
11
12## When to Use
13
14- Use this skill when the task needs Kaplan-Meier survival analysis tool for clinical and biological research. Generates publication-ready survival curves with statistical tests.
15- Use this skill for data analysis tasks that require explicit assumptions, bounded scope, and a reproducible output format.
16- Use this skill when you need a documented fallback path for missing inputs, execution errors, or partial evidence.
17
18## Key Features
19
20See `## Features` above for related details.
21
22- Scope-focused workflow aligned to: Kaplan-Meier survival analysis tool for clinical and biological research. Generates publication-ready survival curves with statistical tests.
23- Packaged executable path(s): `scripts/main.py`.
24- Reference material available in `references/` for task-specific guidance.
25- Structured execution path designed to keep outputs consistent and reviewable.
26
27## Dependencies
28
29- `lifelines`: Core survival analysis library
30- `matplotlib`, `seaborn`: Visualization
31- `pandas`, `numpy`: Data handling
32- `scipy`: Statistical tests
33
34## Example Usage
35
36See `## Usage` above for related details.
37
38```bash
39cd "20260318/scientific-skills/Data Analytics/survival-analysis-km"
40python -m py_compile scripts/main.py
41python scripts/main.py --help
42```
43
44Example run plan:
451. Confirm the user input, output path, and any required config values.
462. Edit the in-file `CONFIG` block or documented parameters if the script uses fixed settings.
473. Run `python scripts/main.py` with the validated inputs.
484. Review the generated output and return the final artifact with any assumptions called out.
49
50## Implementation Details
51
52See `## Workflow` above for related details.
53
54- Execution model: validate the request, choose the packaged workflow, and produce a bounded deliverable.
55- Input controls: confirm the source files, scope limits, output format, and acceptance criteria before running any script.
56- Primary implementation surface: `scripts/main.py`.
57- Reference guidance: `references/` contains supporting rules, prompts, or checklists.
58- Parameters to clarify first: input path, output path, scope filters, thresholds, and any domain-specific constraints.
59- Output discipline: keep results reproducible, identify assumptions explicitly, and avoid undocumented side effects.
60
61## Quick Check
62
63Use this command to verify that the packaged script entry point can be parsed before deeper execution.
64
65```bash
66python -m py_compile scripts/main.py
67```
68
69## Audit-Ready Commands
70
71Use these concrete commands for validation. They are intentionally self-contained and avoid placeholder paths.
72
73```bash
74python -m py_compile scripts/main.py
75
76# Example invocation: python scripts/main.py --help
77
78# Example invocation: python scripts/main.py --input "Audit validation sample with explicit symptoms, history, assessment, and next-step plan."
79```
80
81## Workflow
82
831. Confirm the user objective, required inputs, and non-negotiable constraints before doing detailed work.
842. Validate that the request matches the documented scope and stop early if the task would require unsupported assumptions.
853. Use the packaged script path or the documented reasoning path with only the inputs that are actually available.
864. Return a structured result that separates assumptions, deliverables, risks, and unresolved items.
875. If execution fails or inputs are incomplete, switch to the fallback path and state exactly what blocked full completion.
88
89## Features
90
91- **Kaplan-Meier Curve Generation**: Publication-quality survival plots with confidence intervals
92- **Statistical Tests**: Log-rank test, Wilcoxon test, Peto-Peto test
93- **Hazard Ratios**: Cox proportional hazards regression with 95% CI
94- **Summary Statistics**: Median survival time, restricted mean survival time (RMST)
95- **Multi-group Analysis**: Supports 2+ comparison groups
96- **Risk Tables**: Optional at-risk table below curves
97
98## Usage
99
100### Python Script
101
102```text
103
104# Example invocation: python scripts/main.py --input data.csv --time time_col --event event_col --group group_col --output results/
105```
106
107### Arguments
108
109| Argument | Description | Required |
110|----------|-------------|----------|
111| `--input` | Input CSV file path | Yes |
112| `--time` | Column name for survival time | Yes |
113| `--event` | Column name for event indicator (1=event, 0=censored) | Yes |
114| `--group` | Column name for grouping variable | Optional |
115| `--output` | Output directory for results | Yes |
116| `--conf-level` | Confidence level (default: 0.95) | Optional |
117| `--risk-table` | Include risk table in plot | Optional |
118
119### Input Format
120
121CSV with columns:
122- **Time column**: Numeric, time to event or censoring
123- **Event column**: Binary (1 = event occurred, 0 = censored/right-censored)
124- **Group column**: Categorical variable for stratification
125
126Example:
127```csv
128patient_id,time_months,death,treatment_group
129P001,24.5,1,Drug_A
130P002,36.2,0,Drug_A
131P003,18.7,1,Placebo
132```
133
134### Output Files
135
136- `km_curve.png`: Kaplan-Meier survival curve
137- `km_curve.pdf`: Vector version for publications
138- `survival_stats.csv`: Statistical summary (median survival, confidence intervals)
139- `hazard_ratios.csv`: Cox regression results with HR and 95% CI
140- `logrank_test.csv**: Pairwise comparison p-values
141- `report.txt**: Human-readable summary report
142
143## Technical Details
144
145### Statistical Methods
146
1471. **Kaplan-Meier Estimator**: Non-parametric maximum likelihood estimate of survival function
148 - Product-limit estimator: Ŝ(t) = Π(tᵢ≤t) (1 - dᵢ/nᵢ)
149 - Greenwood's formula for variance estimation
150
1512. **Log-Rank Test**: Most widely used test for comparing survival curves
152 - Null hypothesis: No difference between groups
153 - Weighted by number at risk at each event time
154
1553. **Cox Proportional Hazards**: Semi-parametric regression model
156 - h(t|X) = h₀(t) × exp(β₁X₁ + β₂X₂ + ...)
157 - Proportional hazards assumption checked via Schoenfeld residuals
158
159### Technical Difficulty: High ⚠️
160
161This skill involves advanced statistical modeling. Results should be reviewed by a biostatistician, especially for:
162- Proportional hazards assumption violations
163- Small sample sizes (< 30 per group)
164- Heavy censoring (> 50%)
165- Time-varying covariates
166
167## References
168
169See `references/` folder for:
170- Kaplan EL, Meier P (1958) original paper
171- Cox DR (1972) regression models paper
172- Sample datasets for testing
173- Clinical reporting guidelines (ATN, CONSORT)
174
175## Parameters
176
177| Parameter | Type | Default | Description |
178|-----------|------|---------|-------------|
179| `--input` | str | Required | Input CSV file path |
180| `--time` | str | Required | Column name for survival time |
181| `--event` | str | Required | |
182| `--group` | str | Required | |
183| `--output` | str | Required | Output directory for results |
184| `--conf-level` | float | 0.95 | |
185| `--risk-table` | str | Required | Include risk table in plot |
186| `--figsize` | str | '10 | |
187| `--dpi` | int | 300 | |
188
189## Example
190
191```text
192
193# Basic survival curve
194
195# Example invocation: python scripts/main.py \
196 --input clinical_data.csv \
197 --time overall_survival_months \
198 --event death \
199 --group treatment_arm \
200 --output ./results/ \
201 --risk-table
202```
203
204Output includes:
205- Survival curves with 95% confidence bands
206- Median survival: Drug A = 28.4 months (95% CI: 24.1-32.7), Placebo = 18.2 months (95% CI: 15.3-21.1)
207- Log-rank test p-value: 0.0023
208- Hazard ratio: 0.62 (95% CI: 0.45-0.85), p = 0.003
209
210## Risk Assessment
211
212| Risk Indicator | Assessment | Level |
213|----------------|------------|-------|
214| Code Execution | Python/R scripts executed locally | Medium |
215| Network Access | No external API calls | Low |
216| File System Access | Read input files, write output files | Medium |
217| Instruction Tampering | Standard prompt guidelines | Low |
218| Data Exposure | Output files saved to workspace | Low |
219
220## Security Checklist
221
222- [ ] No hardcoded credentials or API keys
223- [ ] No unauthorized file system access (../)
224- [ ] Output does not expose sensitive information
225- [ ] Prompt injection protections in place
226- [ ] Input file paths validated (no ../ traversal)
227- [ ] Output directory restricted to workspace
228- [ ] Script execution in sandboxed environment
229- [ ] Error messages sanitized (no stack traces exposed)
230- [ ] Dependencies audited
231
232## Prerequisites
233
234```text
235
236# Python dependencies
237pip install -r requirements.txt
238```
239
240## Evaluation Criteria
241
242### Success Metrics
243- [ ] Successfully executes main functionality
244- [ ] Output meets quality standards
245- [ ] Handles edge cases gracefully
246- [ ] Performance is acceptable
247
248### Test Cases
2491. **Basic Functionality**: Standard input → Expected output
2502. **Edge Case**: Invalid input → Graceful error handling
2513. **Performance**: Large dataset → Acceptable processing time
252
253## Lifecycle Status
254
255- **Current Stage**: Draft
256- **Next Review Date**: 2026-03-06
257- **Known Issues**: None
258- **Planned Improvements**:
259 - Performance optimization
260 - Additional feature support
261
262## Output Requirements
263
264Every final response should make these items explicit when they are relevant:
265
266- Objective or requested deliverable
267- Inputs used and assumptions introduced
268- Workflow or decision path
269- Core result, recommendation, or artifact
270- Constraints, risks, caveats, or validation needs
271- Unresolved items and next-step checks
272
273## Error Handling
274
275- If required inputs are missing, state exactly which fields are missing and request only the minimum additional information.
276- If the task goes outside the documented scope, stop instead of guessing or silently widening the assignment.
277- If `scripts/main.py` fails, report the failure point, summarize what still can be completed safely, and provide a manual fallback.
278- Do not fabricate files, citations, data, search results, or execution outcomes.
279
280## Input Validation
281
282This skill accepts requests that match the documented purpose of `survival-analysis-km` and include enough context to complete the workflow safely.
283
284Do not continue the workflow when the request is out of scope, missing a critical input, or would require unsupported assumptions. Instead respond:
285
286> `survival-analysis-km` only handles its documented workflow. Please provide the missing required inputs or switch to a more suitable skill.
287
288## Response Template
289
290Use the following fixed structure for non-trivial requests:
291
2921. Objective
2932. Inputs Received
2943. Assumptions
2954. Workflow
2965. Deliverable
2976. Risks and Limits
2987. Next Checks
299
300If the request is simple, you may compress the structure, but still keep assumptions and limits explicit when they affect correctness.
301
302## Inputs to Collect
303
304- Required inputs: the user goal, the primary data or source file, and the requested output format.
305- Optional inputs: output directory, formatting preferences, and validation constraints.
306- If a required input is unavailable, return a short clarification request before continuing.
307
308## Output Contract
309
310- Return a short summary, the main deliverables, and any assumptions that materially affect interpretation.
311- If execution is partial, label what succeeded, what failed, and the next safe recovery step.
312- Keep the final answer within the documented scope of the skill.
313
314## Validation and Safety Rules
315
316- Validate identifiers, file paths, and user-provided parameters before execution.
317- Do not fabricate results, metrics, citations, or downstream conclusions.
318- Use safe fallback behavior when dependencies, credentials, or required inputs are missing.
319- Surface any execution failure with a concise diagnosis and recovery path.