Skip to content
Skills Library
Science & research · Automation

launch-workflow

/launch-workflow

Launch Nextflow pipeline executions on cloud and HPC clusters via Seqera Platform. Use when the user wants to run/launch/submit a pipeline on a cloud or cluster compute environment, configure a compute environment, push pipeline changes to GitHub before launching, or sign in to Seqera Platform.

Licence
Apache-2.0
Last repository change
13.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 13.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Launch Nextflow pipeline executions on cloud and HPC clusters via Seqera Platform. Use when the user wants to run/launch/submit a pipeline on a cloud or cluster compute environment, configure a compute environment, push pipeline changes to GitHub before launching, or sign in to Seqera Platform.

Original author description

Launch Nextflow pipeline executions on cloud and HPC clusters via Seqera Platform. Use when the user wants to run/launch/submit a pipeline on a cloud or cluster compute environment, configure a compute environment, push pipeline changes to GitHub before launching, or sign in to Seqera Platform.

How it works

  1. Main Flow
  2. Step 1: Authenticate with Seqera Platform
  3. Step 2: Configure the Compute Environment
  4. Step 3: Ensure the Pipeline Is in a Remote Git Repository
  5. Step 4: Upload Local Changes
  6. Step 5: Launch the Pipeline
  7. Step 6: Monitor the Execution
  8. Critical Rules
Original SKILL.md headings · 144 lines, 785 words
SKILL.md preview
---
name: launch-workflow
description: Launch Nextflow pipeline executions on cloud and HPC clusters via Seqera Platform. Use when the user wants to run/launch/submit a pipeline on a cloud or cluster compute environment, configure a compute environment, push pipeline changes to GitHub before launching, or sign in to Seqera Platform.
allowed-tools: Bash, Read, Glob, mcp__seqera__search_seqera_api, mcp__seqera__call_seqera_api
---

# Launch Pipeline on Seqera Platform

Launch Nextflow pipeline executions on cloud (AWS, Google Cloud, Azure) and HPC clusters (Slurm, LSF, etc.) through Seqera Platform. Seqera Platform manages the target compute environment, executes the pipeline from a remote Git repository, and provides monitoring.

**Requires Nextflow 26.04 or later** (for the `nextflow auth` and `nextflow launch` commands).

## Main Flow

1. **Configure the compute environment** — select a Seqera Platform compute environment for the target cloud or cluster.
2. **Ensure the pipeline is in a remote Git repository** — Seqera Platform launches pipelines from GitHub (or a compatible Git host such as GitLab or Bitbucket). If the local pipeline is not yet hosted, assist the user in setting up the repository.
3. **Upload local changes** — push any uncommitted local changes to the remote so the launched run reflects the user's current code.
4. **Launch with `nextflow launch`** — submit the pipeline by passing the Git repository URL and the expected parameters.

## Step 1: Authenticate with Seqera Platform

Check whether the user is already authenticated:

```bash
nextflow auth status
```

If not authenticated, sign in:

```bash
nextflow auth login
```

This opens a browser for authentication. Wait for the user to complete the login flow before proceeding.

## Step 2: Configure the Compute Environment

List available compute environments using the Seqera API:

```
call_seqera_api(
  service: "platform",
  api_name: "platform_list_compute_envs",
  parameters: {}
)
```

Selecting the compute environment:

1. Present the available compute environments to the user (name, platform type, region/cluster).
2. If multiple environments are available, ask the user which one to use.
3. If only one is available, propose it and ask for confirmation.
4. Confirm the selected compute environment with the user before launching.

## Step 3: Ensure the Pipeline Is in a Remote Git Repository

Seqera Platform launches pipelines from a remote Git URL — it cannot launch directly from a local path. Verify the pipeline directory is a Git repository connected to a remote on GitHub (or a compatible host like GitLab or Bitbucket).

Check the current state:

```bash
git remote -v
git status
```

**If the pipeline is not yet a Git repository or has no remote**, assist the user in setting it up:

1. Initialize the repository if needed:
   ```bash
   git init
   git add .
   git commit -m "Initial pipeline commit"
   ```
2. Help the user create a remote repository (e.g., on GitHub via `gh repo create`) or ask for an existing remote URL.
3. Add the remote and push:
   ```bash
   git remote add origin <repo-url>
   git push -u origin main
   ```

## Step 4: Upload Local Changes

Before launching, push any local changes so the remote reflects the code that should run:

```bash
git status
git add <files>
git commit -m "<message>"
git push
```

If the working tree is clean and the local branch is in sync with the remote, skip this step.

## Step 5: Launch the Pipeline

Use `nextflow launch` with the Git repository URL and parameters:

```bash
nextflow launch <git-repo-url> \
  -r <revision> \
  --input <input> \
  --outdir <outdir> \
  [additional --params...]
```

### Examples

**Launch a pipeline from GitHub:**
```bash
nextflow launch https://github.com/org/pipeline \
  -r main \
  --input samplesheet.csv \
  --outdir s3://bucket/results
```

**Launch an nf-core pipeline:**
```bash
nextflow launch https://github.com/nf-core/rnaseq \
  -r 3.14.0 \
  --input samplesheet.csv \
  --outdir s3://bucket/results \
  --genome GRCh38
```

### Key options

| Option | Description |
|--------|-------------|
| `-r <revision>` | Pipeline version, branch, or tag |
| `--input` | Input samplesheet or data |
| `--outdir` | Output directory (cloud storage when running on cloud CEs) |
| `-params-file params.yml` | Parameters file |
| `-resume` | Resume a previous execution |

## Step 6: Monitor the Execution

`nextflow launch` returns a run URL on Seqera Platform. Present this URL to the user so they can monitor progress in the Platform UI.

## Critical Rules

1. **AUTHENTICATE first** — check `nextflow auth status` before attempting to launch.
2. **CONFIRM the compute environment** — always show the user the selected CE before launching.
3. **REQUIRE a remote Git repository** — the pipeline must be hosted on GitHub or a compatible Git host. If not, help the user set it up before launching.
4. **PUSH local changes first** — the launched run uses the remote code, so local edits must be committed and pushed.
5. **PASS the Git repository URL** to `nextflow launch`, not a local path.
6. **PIN the revision** — always use `-r` to target a specific branch, tag, or commit for reproducibility.
7. **USE cloud storage for `--outdir`** when the target CE runs on a cloud platform (s3://, gs://, az://).
8. **PRESENT the run URL** returned by `nextflow launch` so the user can monitor the run.

Versions

The database has no other skills named launch-workflow.

Database snapshot: 13.11.2026 · package version 8d206cd8cb90 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100nextflow
    Builds, runs, and debugs Nextflow DSL2 pipelines and nf-core workflows. Use for Nextflow, nf-core, .nf files, nextflow.config, processes/channels/operators, samplesheets, nf-test, modules/subworkflows, container and executor configuration, HPC/SLURM or cloud deployment, and…
  • 100nextflow
    Build, run, and debug Nextflow data pipelines and nf-core workflows end to end. Use whenever the user mentions Nextflow, nf-core, .nf files, nextflow.config, DSL2, processes/channels/operators, samplesheets, or wants to run a community pipeline (e.g. nf-core/rnaseq,…
  • 95pipeline-guide
    Access ENCODE uniform analysis pipelines, generate user-specific Nextflow/WDL pipelines, manage compute resources, and integrate with cloud platforms. Use when the user wants to understand ENCODE pipelines, run pipelines on their own data, generate custom Nextflow workflows from…
  • 100create-workflow
    INVOKE THIS SKILL IMMEDIATELY when user asks to: write/create/build a Nextflow pipeline or workflow, create any bioinformatics pipeline (RNA-seq, DNA-seq, variant calling, ChIP-seq, etc.), or compose/chain Nextflow modules (process or workflow modules) from the Nextflow…
  • 100nf-core-institutional-profile
    Write, test, or fix an institutional Nextflow config profile (nf-core/configs style) for an HPC cluster: file structure, executor/scheduler settings, container and module setup, documentation, and testing. Use when configuring pipelines for a specific compute environment.
  • 100run-module
    Run Nextflow Registry modules natively using `nextflow module` commands. Use when running, listing, or getting info about Nextflow modules, including process modules (a single tool) and workflow modules (subworkflows that chain several modules).

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.