Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
k-dense-ai avatar

Pacsomatic

  • 524 installs
  • 32.7k repo stars
  • Updated August 3, 2026
  • k-dense-ai/scientific-agent-skills

pacsomatic is a scientific agent skill that runs nf-core/pacsomatic matched tumor-normal workflows from BAM inputs for developers and bioinformaticians who need reproducible somatic mutation detection on HPC clusters.

About

pacsomatic (version 1.0) in k-dense-ai/scientific-agent-skills is an operator toolkit for nf-core/pacsomatic matched tumor-normal analysis from BAM files. A single helper entrypoint, scripts/run_pacsomatic.py, validates patient and sample identifiers, checks BAM and reference paths, writes pacsomatic-compliant samplesheets (patient,sample,status,bam,pbi), generates params YAML and launch scripts, and supports dry-run validation or live execution locally or on schedulers. Supported executors include LSF, Slurm, PBS, and SGE with resource flags for CPUs, memory, walltime, and queue. Developers reach for pacsomatic when preparing somatic mutation runs, fixing samplesheet errors, submitting Slurm jobs, or triaging .nextflow.log failures without hand-assembling nextflow run commands. The skill enforces routing through the helper script and returns command paths, validation status, and scheduler job IDs per its agent response contract.

  • Somatic variant calling
  • Cancer genomics
  • VCF processing
  • Mutation filtering
  • Sequencing QC

Pacsomatic by the numbers

  • 524 all-time installs (skills.sh)
  • +39 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #440 of 2,064 Data Science & ML skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/k-dense-ai/scientific-agent-skills --skill pacsomatic

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs524
repo stars32.7k
Last updatedAugust 3, 2026
Repositoryk-dense-ai/scientific-agent-skills

How do you run nf-core pacsomatic on HPC?

Detect and interpret somatic mutations from sequencing data using PAC somatic workflows for cancer genomics studies and clinical research agents.

Who is it for?

Bioinformatics engineers running matched tumor-normal somatic mutation pipelines on Nextflow with Singularity profiles and cluster schedulers.

Skip if: Researchers needing deep variant biological interpretation without pipeline execution or teams without BAM inputs and reference genomes.

When should I use this skill?

User asks to run pacsomatic, prepare samplesheets, dry-run nf-core/pacsomatic, submit to Slurm/LSF, or debug pacsomatic launch failures.

What you get

Validated samplesheet CSV, params YAML, reproducible launch script, and optional scheduler job ID from nf-core/pacsomatic execution.

  • Pacsomatic samplesheet CSV
  • Params YAML and launch script
  • Dry-run validation report or scheduler job ID

By the numbers

  • Primary helper entrypoint is scripts/run_pacsomatic.py
  • Supports 4 cluster schedulers: LSF, Slurm, PBS, and SGE
  • Skill metadata version 1.0 targeting nf-core/pacsomatic upstream pipeline

Files

SKILL.mdMarkdownGitHub ↗

pacsomatic

Overview

This skill provides a reproducible execution workflow for nf-core/pacsomatic, centered on a single helper entrypoint that handles validation, artifact generation, and optional execution.

Primary entrypoint:

  • scripts/run_pacsomatic.py

The helper script:

  • validates required identifiers, files, reference mode, and runtime prerequisites
  • writes a pacsomatic-compatible samplesheet (patient,sample,status,bam,pbi)
  • generates a params YAML and launch script for reproducible reruns
  • supports dry-run validation and run/submit execution paths

Use this skill as the default path for pacsomatic operations. Do not bypass it with manually assembled nextflow run nf-core/pacsomatic commands unless the user explicitly asks for manual command construction.

When to Use This Skill

Invoke this skill when the user asks to:

  • run matched tumor-normal analysis from BAM files
  • generate or fix pacsomatic samplesheet and launch artifacts
  • execute locally or submit to schedulers (LSF/Slurm/PBS/SGE)
  • perform dry-run validation before execution
  • troubleshoot launch failures or summarize run outputs

Do not use this skill for:

  • deep biological interpretation beyond run-level sanity checks
  • editing pipeline internals unless explicitly requested

Typical trigger phrases:

  • "run nf-core/pacsomatic for this tumor-normal pair"
  • "prepare pacsomatic samplesheet and launch script"
  • "do a dry run first and tell me what is missing"
  • "submit pacsomatic to slurm/lsf and return the job id"
  • "why did pacsomatic submission fail"

Routing and Execution Rules

1. Always collect required run inputs first. 2. Always route through scripts/run_pacsomatic.py for validation and artifact generation. 3. Default to --dry-run when the user asks for checks/validation only. 4. Use --run only when the user asks to execute/submit. 5. For scheduler modes, include executor-specific resource arguments and return detected job ID when available. 6. If execution fails, report first failure point and next triage target (.nextflow.log, pipeline_info, failing task logs).

Inputs Required

Required:

  • tumor BAM path
  • normal BAM path
  • patient ID
  • tumor sample ID
  • normal sample ID
  • output directory
  • exactly one reference mode: --fasta or --genome

Optional:

  • profile, resources, scheduler account/queue
  • pipeline version (-r)
  • params file, resume/report/dag flags
  • --dry-run and/or --run

Workflow

1. Validate identity and input constraints. 2. Validate required local paths (BAM, optional PBI, optional FASTA). 3. Resolve runtime and dependency checks. 4. Build samplesheet and generated params YAML. 5. Generate launch script for selected executor. 6. If --dry-run and not --run, stop after artifact generation. 7. If --run, execute locally or submit to scheduler. 8. Return command/script path, validation status, and job ID (if detected).

Agent Response Contract

Every response after invocation should include:

  • exact command used or generated script path
  • confirmation that validation checks ran
  • run type (dry-run vs run)
  • scheduler job ID when available
  • one concrete next step for validation/triage

Quick Start

Dry run:

python scripts/run_pacsomatic.py \
  --tumor-bam /path/to/tumor.bam \
  --normal-bam /path/to/normal.bam \
  --patient-id P001 \
  --tumor-sample-id P001_T \
  --normal-sample-id P001_N \
  --outdir /path/to/output \
  --genome GRCh38 \
  --profile singularity,sanger \
  --dry-run

Scheduler execution example (Slurm):

python scripts/run_pacsomatic.py \
  --tumor-bam /path/to/tumor.bam \
  --normal-bam /path/to/normal.bam \
  --patient-id P001 \
  --tumor-sample-id P001_T \
  --normal-sample-id P001_N \
  --outdir /path/to/output \
  --genome GRCh38 \
  --profile singularity,sanger \
  --executor slurm \
  --queue compute \
  --project my_account \
  --cpus 16 \
  --memory-gb 64 \
  --walltime 48:00 \
  --run

Configuration

Use config.yaml as the baseline for profile/executor/runtime defaults. Override at invocation time when user requirements differ.

Testing

Run unit tests from skill root:

python -m unittest discover -s tests -v

References

  • references/agent-playbook.md
  • references/config-and-output.md
  • references/pacsomatic_guide.md
  • scripts/run_pacsomatic.py

Related skills

How it compares

Pick pacsomatic for matched tumor-normal BAM workflows; pick generic Nextflow skills when the pipeline is not nf-core/pacsomatic.

FAQ

What inputs does pacsomatic require?

pacsomatic requires tumor and normal BAM paths, patient and sample IDs, an output directory, and exactly one reference mode via --fasta or --genome such as GRCh38 before generating samplesheets and launch artifacts.

Which schedulers does pacsomatic support?

pacsomatic supports local execution plus LSF, Slurm, PBS, and SGE submission through run_pacsomatic.py --executor flags with queue, account, CPU, memory, and walltime parameters.

Data Science & MLpipelinesanalytics

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.