← NGS Analysis WorkbenchCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
changed
Update to NGS Analysis Workbench
Snapshot Sep 30, 2026 · 23:20 UTC · version 0.2.16
Collection source: not recorded for this historical snapshot. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.
Supporting file metadata differs
Newly listed paths: agents/openai.yaml. This compares saved file lists, not package contents; a different collection source can change the list.
Observed in package metadata. These changes alone do not establish a new customer-facing feature.
Supporting files
Before
[]
After
[{"relative_path":"agents/openai.yaml","size_in_bytes":285}]
Compare saved observations
Download comparison JSONFull technical diff · 1 changed fields
changed /included_files
BEFORE
[]
AFTER
[
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 285
}
]Full snapshot data
{
"name": "understand-ngs-data",
"description": "Understand an NGS starting point from raw reads, matrices, metadata, references, prior plans, runs, or results. Use when the user asks what data exists, how files and samples relate, whether inputs are usable, what is missing, or which analyses they could support.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 285
}
],
"skill_md_contents": "---\nname: understand-ngs-data\ndescription: Understand an NGS starting point from raw reads, matrices, metadata, references, prior plans, runs, or results. Use when the user asks what data exists, how files and samples relate, whether inputs are usable, what is missing, or which analyses they could support.\n---\n\n# Understand NGS Data\n\nRead [AnalysisContext](../../references/analysis-context.md). Inspect and relate\navailable material without choosing a workflow, installing software,\ntransforming inputs, or creating an execution plan.\n\n## Inspect\n\nInventory relevant:\n\n- FASTQs and their raw or derived state\n- BCL run folders, sample sheets, index reads, lanes, and demultiplexing outputs\n- DNA alignments, VCF/gVCF files, target intervals, and tumor/normal relationships\n- chromatin alignments, peak sets, signal tracks, targets, and control libraries\n- marker-gene or shotgun inputs, feature/taxonomy tables, and reference databases\n- bulk counts, transcript estimates, matrices, and sample metadata\n- single-cell matrices or objects (`matrix.mtx`, `*.h5`, `*.h5ad`, `*.rds`)\n- library, chemistry, genome, annotation, index, and sample-sheet metadata\n- immutable plans, durable run IDs, result projections, and primary artifacts\n\nRecord identity, role, provenance, observed state, and sample or artifact\nrelationships. Prefer parsers, manifests, and workflow-owned metadata over\nfilenames. Use durable get tools to establish run lifecycle; do not interpret a\nnonterminal run.\n\nLoad only the applicable scientific reference:\n\n- [Basic FASTQ QC](../../references/fastq-qc.md)\n- [Bulk RNA-seq](../../references/bulk-rnaseq.md)\n- [Single-cell RNA-seq](../../references/single-cell-rnaseq.md)\n- [Detailed single-cell guidance](../../references/single-cell-qc-annotation-umap-heuristics.md), only for existing cell-level QC, annotation, or embedding decisions\n- [Demultiplexing](../../references/bcl-demultiplexing.md), for BCLs, index reads, and sample assignment\n- [DNA variants](../../references/dna-variants.md), for germline, somatic, or UMI-panel material\n- [Epigenomics](../../references/epigenomics.md), for ATAC, ChIP, or CUT&RUN material\n- [Microbiome](../../references/microbiome.md), for amplicon or shotgun metagenomic material\n\nLet assay-specific guidance override generic FASTQ advice for protocol-specific\nread roles. State supportable tasks in scientific terms, not engine names. Ask\nonly for missing information that changes sample identity, assay\ninterpretation, method, or endpoint.\n\n## Output: StartingPointAssessment\n\nAdd a `starting_point_assessment` artifact with:\n\n1. known objective\n2. material inventory and relationships\n3. evidence and provenance\n4. supportable tasks and their conditions\n5. missing, conflicting, or unusable inputs\n6. open questions and at most one pending user decision\n7. justified handoff to design, run, or results\n"
}SHA-256: c2c23cb0ec026e7f8a82270c593a102cb3b53c5166d41ba11c06876de18aa05f