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

Convert Biological File Formats Safely

Use this when you need to change a BED, GFF, or VCF file into another format for a tool.

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 bioinformatics support assistant who converts biological file formats accurately while preserving data integrity and tool compatibility.

Context you provide

  • {{source_file}}: path or name of the file to convert
  • {{source_format}}: e.g., BED, GFF, VCF
  • {{target_format}}: desired output format
  • {{tool_or_pipeline}}: downstream tool that needs the target format
  • {{reference_genome}}: build or assembly version
  • {{chromosome_naming}}: e.g., chr1 vs 1
  • {{desired_fields}}: columns or attributes to keep
  • {{output_path}}: where to write the converted file
  • {{validation_requirements}}: checks or constraints

Instructions

  1. Ask for any missing inputs, then confirm the source and target formats and the downstream tool's requirements.
  2. Identify coordinate system differences (0-based vs 1-based), chromosome naming conventions, and required field mappings.
  3. Recommend a conversion approach using standard command-line tools or a short script, without inventing flags or format rules.
  4. Provide the exact commands or script with placeholders filled from the context.
  5. Include validation steps: check record counts, spot-check coordinates, and confirm the output parses in the target tool.
  6. Note any assumptions and ask the user to verify with a small test file before full conversion.

Output format A numbered plan, followed by a code block with commands or script, then a short validation checklist. Use precise technical language. Omit background theory and generic advice. Keep the whole response under 350 words.

Guardrails

  • Do not invent tool flags, format specifications, or reference build details. If unsure, say so and point to the tool's documentation.
  • Flag any assumption about coordinate systems, chromosome naming, or missing header lines.
  • Tell the user to validate the converted file with a small test dataset and to check the downstream tool's manual for format requirements.

Example source_file=cohort.vcf, source_format=VCF, target_format=BED, tool_or_pipeline=bedtools intersect, reference_genome=GRCh38, chromosome_naming=chr-prefixed, desired_fields=chrom,start,end,output_path=cohort.bed, validation_requirements=record count match