Install
$ agentstack add skill-astroreality-li-bioinformatics-analysis-preflight-bioinformatics-analysis-preflight ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Bioinformatics Analysis Preflight
Overview
Run a local, deterministic preflight before spending compute or trusting biological results. The skill does not replace workflow-specific skills; it catches the cross-cutting mistakes those workflows often inherit: mismatched sample IDs, broken file paths, confounded metadata, missing alignment indexes, normalized values passed as counts, weak provenance, and privacy-risky cloud assumptions.
Core Workflow
- Inventory inputs. Inspect the project tree and classify FASTQ, BAM/CRAM, VCF, h5ad, count matrix, metadata, sample sheet, and report files. Do not upload genomic or clinical data.
- Run deterministic preflight. Use
scripts/bio_preflight.pywhenever the user has local files or asks "is this ready to analyze?" - Interpret severity. Treat
FAILfindings as blockers,WARNfindings as risks to resolve or disclose, andPASSfindings as evidence, not proof. - Route downstream. After blockers are fixed, hand off to domain skills such as bulk RNA-seq, Scanpy/Seurat, variant annotation, ATAC/ChIP, microbiome, proteomics, or workflow-management skills.
- Preserve provenance. Keep the generated Markdown and JSON reports with the analysis outputs.
Quick Start
python bioinformatics-analysis-preflight/scripts/bio_preflight.py \
--root . \
--metadata metadata.csv \
--counts counts.csv \
--sample-sheet samplesheet.csv \
--condition-column condition \
--batch-column batch \
--output-dir preflight
If the user only provides a project directory, scan it and let the script auto-detect likely inputs:
python bioinformatics-analysis-preflight/scripts/bio_preflight.py \
--root /path/to/project \
--output-dir /path/to/project/preflight
For CI-style use, fail the command when blocking issues are found:
python bioinformatics-analysis-preflight/scripts/bio_preflight.py \
--root . --metadata metadata.csv --counts counts.csv --fail-on fail
What The Script Checks
The script uses only the Python standard library and writes:
analysis-preflight-report.md- human-readable summary and next actions.analysis-preflight.json- machine-readable manifest, inventory, and findings.
It checks:
- sample metadata: duplicate IDs, missing IDs, likely condition/batch columns, weak replication, and batch-condition confounding.
- count matrices: gene/sample orientation clues, duplicate genes, duplicate sample columns, negative values, non-integer values, and metadata/count sample mismatches.
- sample sheets: required sample/path columns, duplicate samples, missing FASTQ/BAM paths, mixed single/paired layout, and strandedness values.
- FASTQ files: common R1/R2 pairing patterns and first-record structure for a limited sample of files.
- BAM/CRAM files: missing
.bai,.csi, or.craisidecar indexes. - VCF files: header presence, sample columns, and contig metadata.
- h5ad files: HDF5 magic-byte sanity check.
Agent Decision Rules
- Run the preflight before launching expensive workflows, changing data, or making biological claims from new user data.
- Ask before installing heavy bioinformatics tools; this skill's script intentionally avoids extra dependencies.
- Do not send genomic, clinical, or unpublished omics data to external services unless the user explicitly approves that specific transfer.
- Do not treat a clean preflight as scientific validation. It only validates readiness and common failure modes.
- If a workflow-specific skill has a stricter preflight, use both: this skill for cross-project audit and the workflow skill for method-specific validation.
Detailed References
references/risk-rubric.md- severity definitions, blocker policy, and how to phrase residual risks.references/modality-checklists.md- domain-specific checks for bulk RNA-seq, single-cell, variants, epigenomics, microbiome, proteomics, and multi-omics.references/report-template.md- recommended structure for the final preflight response to the user.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: AstroReality-Li
- Source: AstroReality-Li/bioinformatics-analysis-preflight
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.