Prepare sequence workflows
Read sample manifests, verify file pairs and checksums, record genome and annotation versions, and plan quality control before processing.
Codex Skills for Bioinformatics give Codex structured instructions for checking sequence data, assembling reproducible pipelines, using biological databases, tracking samples, validating outputs, and documenting computational analyses. Download the skills and configure them for your organism, assay, references, and computing environment.
task: process RNA-seq cohort
inspect:
- sample sheet
- reference build
- quality metrics
verify: provenance + outputs + reportBioinformatics depends on more than tool syntax. Sample identity, assay design, reference versions, read quality, strandedness, parameters, annotations, statistical models, and biological interpretation all affect the result.
These skills help Codex build computational biology workflows that preserve provenance, expose assumptions, check intermediate files, and keep scientific conclusions separate from raw software output.
Read sample manifests, verify file pairs and checksums, record genome and annotation versions, and plan quality control before processing.
Create scripts or workflow definitions with declared inputs, environments, resources, checkpoints, logs, and resumable outputs.
Prepare sequence searches, parse identifiers, retrieve authorized records, preserve database versions, and avoid mixing incompatible references.
Collect quality metrics, test expected sample relationships, flag anomalies, summarize methods, and generate tables or figures with traceable inputs.
The process begins with experimental design and sample metadata. Analysis only advances when inputs and stage-specific quality checks make sense.
Record organism, assay, sample groups, replicates, covariates, controls, expected contrasts, and limits on interpretation.
Choose the genome build, transcriptome or database release, annotation source, tool versions, containers, and parameters.
Run quality control, trimming when justified, alignment or quantification, counting, normalization, and stage-specific validation.
Inspect diagnostics, confirm sample identity and design, report uncertainty, preserve intermediate summaries, and verify important findings independently.
Sequence similarity, gene expression, and variant analysis require different tools, checks, and interpretations.
Prepare BLAST-style searches, select suitable databases, parse matches, evaluate coverage and significance, and retain record identifiers.
Track reads from FASTQ quality checks through quantification, exploratory analysis, differential expression, annotation, and reporting.
Organize alignment, recalibration, calling, filtering, annotation, validation, and careful separation of technical and clinical meaning.
Build reproducible jobs with Snakemake, Nextflow, containers, cluster profiles, checksums, logs, and declared software versions.
The instructions can support small exploratory analyses or formal pipelines, provided the scientific design and approved tools are supplied.
These skills are for users who want Codex to respect scientific context while helping with scripts, pipelines, checks, and records.
Develop, review, debug, document, and maintain data pipelines with explicit inputs, versions, metrics, and outputs.
Turn an experimental design into a computational plan and keep sample metadata connected to the analysis.
Standardize intake checks, processing stages, quality reports, delivery files, and reproducibility records across projects.
Learn why each step exists while building scripts that can be rerun and inspected.
The skills do not replace experimental design, bioinformatics expertise, clinical interpretation, genetic counseling, laboratory validation, ethics approval, or controlled handling of genomic data.
Install the skills with your pipeline repository and provide the biological and computational context before running any workflow.
Keep SKILL.md with included workflow guidance, quality checklists, reporting notes, and supporting files.
Use project scope for assay-specific references and rules, or personal scope for a general computational biology process.
Add the organism, assay, groups, replicates, controls, covariates, reference build, annotation release, and intended contrasts.
Specify approved tools, versions, containers, scheduler, compute limits, storage rules, expected file formats, and protected-data controls.
Ask Codex to inspect manifests, filenames, checksums, pairs, metadata, references, and planned outputs before processing.
Answers about pipelines, sequence databases, RNA-seq, reproducibility, and scientific review.
They can guide and automate analysis using tools available in your environment. The correct workflow depends on the assay, platform, organism, experimental design, and quality requirements.
They can prepare command-line searches, database selection, result parsing, and provenance checks. Database access, licensing, versions, and biological interpretation remain environment-specific.
Yes, when the required data, software, references, metadata, and compute are available. The workflow includes quality checks and requires expert review of the design and results.
Not by default. Clinical use requires validated pipelines, controlled environments, regulatory procedures, qualified interpretation, and confirmatory evidence.
They emphasize versioned references, fixed environments, declared parameters, sample manifests, checksums, logs, stage outputs, and a generated methods record.
Versioned references. Checked stages. Reproducible pipelines. Conclusions that respect the experiment.