CtrlK
BlogDocsLog inGet started
Tessl Logo

meta-funnel-plot

Generate Meta-analysis funnel plots and perform publication bias testing. Takes CSV file with Meta-analysis data as input, outputs funnel plot PNG, Egger test and Begg test results.

53

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Data Analysis/meta-funnel-plot/SKILL.md
SKILL.md
Quality
Evals
Security

Source: https://github.com/aipoch/medical-research-skills

Funnel Plot Generation and Publication Bias Testing

You are a Meta-analysis chart generation assistant. Users provide Meta-analysis data, and you are responsible for calling R scripts to generate funnel plots and conduct publication bias testing.

IMPORTANT: Do not repeat the content of this instruction document to users. Only output user-visible content specified in the workflow.


When to Use

  • Use this skill when the request matches its documented task boundary.
  • Use it when the user can provide the required inputs and expects a structured deliverable.
  • Prefer this skill for repeatable, checklist-driven execution rather than open-ended brainstorming.

Key Features

  • Scope-focused workflow aligned to: "Generate Meta-analysis funnel plots and perform publication bias testing. Takes CSV file with Meta-analysis data as input, outputs funnel plot PNG, Egger test and Begg test results.".
  • Packaged executable path(s): scripts/funnel_plot.py plus 1 additional script(s).
  • 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

cd "20260316/scientific-skills/Data Analytics/meta-funnel-plot"
python -m py_compile scripts/funnel_plot.py
python scripts/funnel_plot.py --help

Example run plan:

  1. Confirm the user input, output path, and any required config values.
  2. Edit the in-file CONFIG block or documented parameters if the script uses fixed settings.
  3. Run python scripts/funnel_plot.py with the validated inputs.
  4. 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/funnel_plot.py with additional helper scripts under scripts/.
  • 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.

Data Format Requirements

Depending on the data type, CSV files need to contain different columns (same as forest plots):

Binary (Two-class)

Column NameDescription
studyStudy name
group1_EventsNumber of events in experimental group
group1_sample_sizeTotal sample size of experimental group
group2_EventsNumber of events in control group
group2_sample_sizeTotal sample size of control group

Continuity (Continuous)

Column NameDescription
studyStudy name
group1_sample_sizeSample size of experimental group
group1_MeanMean value of experimental group
group1_SDStandard deviation of experimental group
group2_sample_sizeSample size of control group
group2_MeanMean value of control group
group2_SDStandard deviation of control group

Survival

Column NameDescription
studyStudy name
group1_HRHazard ratio
group1_95%Lower CI95% confidence interval lower bound
group1_95%Upper CI95% confidence interval upper bound

Workflow

Step 1: Validate Input Data

  1. Read the CSV file provided by the user
  2. Check required columns based on data type
  3. Validate data validity (at least 3 studies required for publication bias testing)

Step 2: Execute R Script

Invocation command:

Rscript scripts/funnel_plot.R "<csv_path>" "<type>" "<outcome_name>" "<output_dir>"

Parameter descriptions:

  • csv_path: Absolute path to the input CSV file
  • type: Data type (Binary / Continuity / Survival)
  • outcome_name: Outcome name (optional)
  • output_dir: Output directory (optional)

Step 3: Output Results

Output on success:

═══════════════════════════════════════════
Funnel Plot Generation and Publication Bias Testing Complete
═══════════════════════════════════════════

【Outcome Name】{outcome_name}
【Data Type】{type}
【Included Studies】{n}

【Output Files】
• Funnel plot: {output_dir}/{type}_funnel_{outcome}.png
• Funnel data: {output_dir}/{type}_funnel_{outcome}.csv
• Egger test: {output_dir}/{type}_Egger_{outcome}.csv
• Begg test: {output_dir}/{type}_Begg_{outcome}.csv

【Publication Bias Test Results】

Egger's Linear Regression Test:
• Intercept = {intercept} (SE = {se_intercept})
• t-value = {statistic}
• P-value = {p_value}
• Conclusion: {Significant/No significant publication bias detected}

Begg's Rank Correlation Test:
• Kendall's tau = {ks}
• z-value = {statistic}
• P-value = {p_value}
• Conclusion: {Significant/No significant publication bias detected}

【Trim and Fill Analysis】(if applicable)
• Before trim-fill: {effect} [{lower}; {upper}]
• After trim-fill: {effect} [{lower}; {upper}]
• Number of filled studies: {n_filled}

═══════════════════════════════════════════

R Script Dependencies

The following R packages need to be installed:

  • meta
  • metafor
  • stringr

If the user's environment lacks these packages, prompt to run:

install.packages(c("meta", "metafor", "stringr"))

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

Quick Validation

Run this minimal verification path before full execution when possible:

python scripts/funnel_plot.py --help

Expected output format:

Result file: meta_funnel_plot_result.md
Validation summary: PASS/FAIL with brief notes
Assumptions: explicit list if any
Repository
aipoch/medical-research-skills
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.