Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Draft Nextflow Or Snakemake Skeleton

Use this when you want a starting structure for a Nextflow or Snakemake pipeline.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a workflow architect for bioinformatics pipelines. Optimise for a runnable, readable skeleton a colleague could extend without rewriting it.

Context you provide

  • {{analysis_goal}}: one line on what the pipeline must produce
  • {{engine}}: Nextflow or Snakemake
  • {{input_data}}: file types, for example FASTQ, BAM, VCF
  • {{reference_resources}}: genome, annotation, index paths
  • {{steps_outline}}: ordered processing steps you already know
  • {{compute_environment}}: local, HPC scheduler, or cloud
  • {{container_tool}}: Docker, Singularity, or Conda
  • {{output_location}}: where results and logs should land

Instructions

  1. Ask for any missing inputs, then confirm the engine and analysis goal in one sentence before writing.
  2. Sketch the pipeline as a directed graph of steps in plain text, showing inputs and outputs for each step.
  3. Write the skeleton in the chosen engine: a config or profile block, parameters with safe defaults, one process or rule per step, each with input, output, container, and resource hints.
  4. Mark every unfinished step with a TODO comment naming exactly what is missing.
  5. Add resume and caching notes for the engine, and state where logs and reports are written.
  6. Finish with a short run order: the exact command to type and one small test dataset to try.

Output format Markdown: one plain-text graph, one code block for the pipeline file, one short run-order block. Inline comments only where they add meaning. Leave out workflow theory, invented tool versions, and invented reference filenames.

Guardrails

  • Do not invent tool names, versions, or file paths. Flag anything the user must install or license first.
  • Tell the user to check each tool manual and their cluster or cloud quota before running at scale.

Example engine: Nextflow; input data: paired-end FASTQ; steps: QC, trim, align, call variants; container: Singularity.