Source: https://github.com/aipoch/medical-research-skills
When to Use
Use this skill when:
- The user provides a sensitivity analysis table (Leave-One-Out) and wants a textual description.
- The user needs to format the "Results" section for a meta-analysis paper regarding sensitivity checks.
- The user specifies a target language (Chinese or English) for the output.
Key Features
- Scope-focused workflow aligned to: Generates the "Results" section for meta-analysis sensitivity analysis based on statistical tables and titles. Use when the user wants to describe sensitivity analysis results or format sensitivity tables for a meta-analysis paper.
- Packaged executable path(s):
scripts/validate_skill.py.
- Structured execution path designed to keep outputs consistent and reviewable.
Dependencies
Python: 3.10+. Repository baseline for current packaged skills.
Third-party packages: not explicitly version-pinned in this skill package. Add pinned versions if this skill needs stricter environment control.
Example Usage
See ## Usage above for related details.
cd "20260316/scientific-skills/Academic Writing/meta-results-sensitivity-analysis"
python -m py_compile scripts/validate_skill.py
python scripts/validate_skill.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/validate_skill.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/validate_skill.py.
- 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.
Validation Shortcut
Run this minimal command first to verify the supported execution path:
python scripts/validate_skill.py --help
Meta Sensitivity Analysis Generator
This skill generates a descriptive "Results" section for meta-analysis sensitivity analysis. It processes statistical tables (Leave-One-Out method), generates a textual description using an LLM, and formats the output with proper table citations and legends.
Workflow
- Generate Description: The LLM describes the sensitivity analysis table based on the meta-analysis title and outcome name.
- Format Output: A script inserts the table citation (e.g.,
(Table 5)) and formats the table with a standard legend.
Usage
Input Parameters
title (optional): Title of the meta-analysis.
sensitivity_table (optional): The raw statistical table data.
language (required): Output language (Chinese or English).
outcome_name (optional): Name of the outcome indicator.
Example
from scripts.format_result import format_sensitivity_result
# 1. LLM generates the description (simulated)
# description = llm.generate(prompt="Describe the sensitivity table...", context=inputs)
# 2. Script formats the final result
# final_output = format_sensitivity_result(
# text=description,
# table_data=inputs['sensitivity_table'],
# language=inputs['language']
# )
Quality Rules
- Language: Output must be strictly in the user-specified language.
- Formatting: Remove any JSON formatting from LLM output.
- Citation: Must insert table citation (Table 5) before the last punctuation of the description.
When Not to Use
- Do not use this skill when the required source data, identifiers, files, or credentials are missing.
- Do not use this skill when the user asks for fabricated results, unsupported claims, or out-of-scope conclusions.
- Do not use this skill when a simpler direct answer is more appropriate than the documented workflow.
Required Inputs
- A clearly specified task goal aligned with the documented scope.
- All required files, identifiers, parameters, or environment variables before execution.
- Any domain constraints, formatting requirements, and expected output destination if applicable.
Output Contract
- Return a structured deliverable that is directly usable without reformatting.
- If a file is produced, prefer a deterministic output name such as
meta_results_sensitivity_analysis_result.md unless the skill documentation defines a better convention.
- Include a short validation summary describing what was checked, what assumptions were made, and any remaining limitations.
Validation and Safety Rules
- Validate required inputs before execution and stop early when mandatory fields or files are missing.
- Do not fabricate measurements, references, findings, or conclusions that are not supported by the provided source material.
- Emit a clear warning when credentials, privacy constraints, safety boundaries, or unsupported requests affect the result.
- Keep the output safe, reproducible, and within the documented scope at all times.
Failure Handling
- If validation fails, explain the exact missing field, file, or parameter and show the minimum fix required.
- If an external dependency or script fails, surface the command path, likely cause, and the next recovery step.
- If partial output is returned, label it clearly and identify which checks could not be completed.
Input Validation
This skill accepts requests that match the documented purpose of meta-results-sensitivity-analysis 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:
meta-results-sensitivity-analysis only handles its documented workflow. Please provide the missing required inputs or switch to a more suitable skill.
Quick Validation
Run this minimal verification path before full execution when possible:
No local script validation step is required for this skill.
Expected output format:
Result file: meta_results_sensitivity_analysis_result.md
Validation summary: PASS/FAIL with brief notes
Assumptions: explicit list if any
Deterministic Output Rules
- Use the same section order for every supported request of this skill.
- Keep output field names stable and do not rename documented keys across examples.
- If a value is unavailable, emit an explicit placeholder instead of omitting the field.
Completion Checklist
- Confirm all required inputs were present and valid.
- Confirm the supported execution path completed without unresolved errors.
- Confirm the final deliverable matches the documented format exactly.
- Confirm assumptions, limitations, and warnings are surfaced explicitly.
1---2name: meta-results-sensitivity-analysis3description: Generates the "Results" section for meta-analysis sensitivity analysis based on statistical tables and titles. Use when the user wants to describe sensitivity analysis results or format sensitivity tables for a meta-analysis paper.4license: MIT5---6> **Source**: [https://github.com/aipoch/medical-research-skills](https://github.com/aipoch/medical-research-skills)
7
8## When to Use
9
10Use this skill when:
111. The user provides a sensitivity analysis table (Leave-One-Out) and wants a textual description.
122. The user needs to format the "Results" section for a meta-analysis paper regarding sensitivity checks.
133. The user specifies a target language (Chinese or English) for the output.
14
15## Key Features
16
17- Scope-focused workflow aligned to: Generates the "Results" section for meta-analysis sensitivity analysis based on statistical tables and titles. Use when the user wants to describe sensitivity analysis results or format sensitivity tables for a meta-analysis paper.
18- Packaged executable path(s): `scripts/validate_skill.py`.
19- Structured execution path designed to keep outputs consistent and reviewable.
20
21## Dependencies
22
23- `Python`: `3.10+`. Repository baseline for current packaged skills.
24- `Third-party packages`: `not explicitly version-pinned in this skill package`. Add pinned versions if this skill needs stricter environment control.
25
26## Example Usage
27
28See `## Usage` above for related details.
29
30```bash
31cd "20260316/scientific-skills/Academic Writing/meta-results-sensitivity-analysis"
32python -m py_compile scripts/validate_skill.py
33python scripts/validate_skill.py --help
34```
35
36Example run plan:
371. Confirm the user input, output path, and any required config values.
382. Edit the in-file `CONFIG` block or documented parameters if the script uses fixed settings.
393. Run `python scripts/validate_skill.py` with the validated inputs.
404. Review the generated output and return the final artifact with any assumptions called out.
41
42## Implementation Details
43
44See `## Workflow` above for related details.
45
46- Execution model: validate the request, choose the packaged workflow, and produce a bounded deliverable.
47- Input controls: confirm the source files, scope limits, output format, and acceptance criteria before running any script.
48- Primary implementation surface: `scripts/validate_skill.py`.
49- Parameters to clarify first: input path, output path, scope filters, thresholds, and any domain-specific constraints.
50- Output discipline: keep results reproducible, identify assumptions explicitly, and avoid undocumented side effects.
51
52## Validation Shortcut
53
54Run this minimal command first to verify the supported execution path:
55
56```bash
57python scripts/validate_skill.py --help
58```
59
60# Meta Sensitivity Analysis Generator
61
62This skill generates a descriptive "Results" section for meta-analysis sensitivity analysis. It processes statistical tables (Leave-One-Out method), generates a textual description using an LLM, and formats the output with proper table citations and legends.
63
64## Workflow
65
661. **Generate Description**: The LLM describes the sensitivity analysis table based on the meta-analysis title and outcome name.
672. **Format Output**: A script inserts the table citation (e.g., `(Table 5)`) and formats the table with a standard legend.
68
69## Usage
70
71### Input Parameters
72
73* `title` (optional): Title of the meta-analysis.
74* `sensitivity_table` (optional): The raw statistical table data.
75* `language` (required): Output language (`Chinese` or `English`).
76* `outcome_name` (optional): Name of the outcome indicator.
77
78### Example
79
80```python
81from scripts.format_result import format_sensitivity_result
82
83# 1. LLM generates the description (simulated)
84
85# description = llm.generate(prompt="Describe the sensitivity table...", context=inputs)
86
87# 2. Script formats the final result
88
89# final_output = format_sensitivity_result(
90
91# text=description,
92
93# table_data=inputs['sensitivity_table'],
94
95# language=inputs['language']
96
97# )
98```
99
100## Quality Rules
101
1021. **Language**: Output must be strictly in the user-specified language.
1032. **Formatting**: Remove any JSON formatting from LLM output.
1043. **Citation**: Must insert table citation (Table 5) before the last punctuation of the description.
105
106## When Not to Use
107
108- Do not use this skill when the required source data, identifiers, files, or credentials are missing.
109- Do not use this skill when the user asks for fabricated results, unsupported claims, or out-of-scope conclusions.
110- Do not use this skill when a simpler direct answer is more appropriate than the documented workflow.
111
112## Required Inputs
113
114- A clearly specified task goal aligned with the documented scope.
115- All required files, identifiers, parameters, or environment variables before execution.
116- Any domain constraints, formatting requirements, and expected output destination if applicable.
117
118## Output Contract
119
120- Return a structured deliverable that is directly usable without reformatting.
121- If a file is produced, prefer a deterministic output name such as `meta_results_sensitivity_analysis_result.md` unless the skill documentation defines a better convention.
122- Include a short validation summary describing what was checked, what assumptions were made, and any remaining limitations.
123
124## Validation and Safety Rules
125
126- Validate required inputs before execution and stop early when mandatory fields or files are missing.
127- Do not fabricate measurements, references, findings, or conclusions that are not supported by the provided source material.
128- Emit a clear warning when credentials, privacy constraints, safety boundaries, or unsupported requests affect the result.
129- Keep the output safe, reproducible, and within the documented scope at all times.
130
131## Failure Handling
132
133- If validation fails, explain the exact missing field, file, or parameter and show the minimum fix required.
134- If an external dependency or script fails, surface the command path, likely cause, and the next recovery step.
135- If partial output is returned, label it clearly and identify which checks could not be completed.
136
137
138## Input Validation
139
140This skill accepts requests that match the documented purpose of `meta-results-sensitivity-analysis` and include enough context to complete the workflow safely.
141
142Do not continue the workflow when the request is out of scope, missing a critical input, or would require unsupported assumptions. Instead respond:
143
144> `meta-results-sensitivity-analysis` only handles its documented workflow. Please provide the missing required inputs or switch to a more suitable skill.
145
146## Quick Validation
147
148Run this minimal verification path before full execution when possible:
149
150```text
151No local script validation step is required for this skill.
152```
153
154Expected output format:
155
156```text
157Result file: meta_results_sensitivity_analysis_result.md
158Validation summary: PASS/FAIL with brief notes
159Assumptions: explicit list if any
160```
161
162## Deterministic Output Rules
163
164- Use the same section order for every supported request of this skill.
165- Keep output field names stable and do not rename documented keys across examples.
166- If a value is unavailable, emit an explicit placeholder instead of omitting the field.
167
168## Completion Checklist
169
170- Confirm all required inputs were present and valid.
171- Confirm the supported execution path completed without unresolved errors.
172- Confirm the final deliverable matches the documented format exactly.
173- Confirm assumptions, limitations, and warnings are surfaced explicitly.