[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EEGZKAP1VG0P7ENCH6V68B":3,"skill-same:01M7EEGZKAP1VG0P7ENCH6V68B":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":14,"repositoryHtmlUrl":33,"repositoryHomepageUrl":33,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":35,"install":36,"resources":49},"01M7EEGZKAP1VG0P7ENCH6V68B","bio-microbiome-qiime2-workflow",null,"Operates the QIIME2 framework as the glue for an amplicon analysis - the .qza\u002F.qzv artifact model, semantic types (FeatureTable[Frequency], SampleData[PairedEndSequencesWithQuality], Phylogeny[Rooted], FeatureData[Taxonomy]), embedded provenance plus provenance replay, import (Casava\u002Fmanifest\u002FEMP\u002FBIOM), export, the Metadata object, and the q2cli vs Artifact API interfaces. Covers why a .qza is data-plus-executable-history not a file, why export drops provenance, why a .qzv is terminal, why classifier .qza are version-pinned, and the 2026 distribution\u002Frachis rename. Use when importing reads, choosing a manifest\u002FCasava\u002FEMP\u002FBIOM path, reading or replaying provenance, exporting to BIOM\u002Fphyloseq, fixing semantic-type or Phred or sklearn-version errors, or orchestrating the pipeline. Denoising -> amplicon-processing; classifier\u002FDB -> taxonomy-assignment; diversity metric\u002Fdepth -> diversity-analysis; DA tool -> differential-abundance; PICRUSt2 -> functional-prediction; shotgun moshpit -> metagenomics.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fbiology\u002Fbio-microbiome-qiime2-workflow\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bio-microbiome-qiime2-workflow\ndescription: Operates the QIIME2 framework as the glue for an amplicon analysis - the .qza\u002F.qzv artifact model, semantic types (FeatureTable[Frequency], SampleData[PairedEndSequencesWithQuality], Phylogeny[Rooted], FeatureData[Taxonomy]), embedded provenance plus provenance replay, import (Casava\u002Fmanifest\u002FEMP\u002FBIOM), export, the Metadata object, and the q2cli vs Artifact API interfaces. Covers why a .qza is data-plus-executable-history not a file, why export drops provenance, why a .qzv is terminal, why classifier .qza are version-pinned, and the 2026 distribution\u002Frachis rename. Use when importing reads, choosing a manifest\u002FCasava\u002FEMP\u002FBIOM path, reading or replaying provenance, exporting to BIOM\u002Fphyloseq, fixing semantic-type or Phred or sklearn-version errors, or orchestrating the pipeline. Denoising -> amplicon-processing; classifier\u002FDB -> taxonomy-assignment; diversity metric\u002Fdepth -> diversity-analysis; DA tool -> differential-abundance; PICRUSt2 -> functional-prediction; shotgun moshpit -> metagenomics.\ntool_type: cli\nprimary_tool: QIIME2\nsource: \"https:\u002F\u002Fgithub.com\u002FGPTomics\u002FbioSkills\"\nsource_repository: \"GPTomics\u002FbioSkills\"\nsource_path: \"microbiome\u002Fqiime2-workflow\u002FSKILL.md\"\nlicense: \"MIT\"\nimported_at: \"2026-09-20\"\n---\n\n## Version Compatibility\n\nReference examples tested with: QIIME2 2026.1+ (amplicon distribution; framework now `rachis`), provenance-lib 2024.10+.\n\nBefore using code patterns, verify installed versions match. If versions differ:\n- CLI: `qiime --version`, `qiime info`, then `qiime \u003Cplugin> \u003Caction> --help` to confirm flags\n\nIf code throws ImportError, AttributeError, or TypeError, introspect the installed\npackage and adapt the example to match the actual API rather than retrying.\n\nThe QIIME2 release tag (calendar-versioned `YYYY.RELEASE`, e.g. `2026.1`) defines the plugin API AND the `.qza` artifact format; an sklearn taxonomy classifier `.qza` trained under one release may need retraining under another (the classifier is pinned to its scikit-learn version). The conda env name encodes the release and distribution (`qiime2-amplicon-2026.1`; renamed toward `rachis-qiime2-\u003Crelease>` in 2026.4). Names and the install YAML URL are moving targets - verify the current release and distribution names against the live install page before pinning anything.\n\n# QIIME2 Amplicon Workflow\n\n**\"Run my amplicon study through QIIME2\"** -> Move data through the framework as typed, provenance-carrying artifacts and defer every scientific choice to the owning skill - because a `.qza` is not a file, it is data plus its entire executable history, and that history is the deliverable.\n- CLI: `qiime tools import`, `qiime \u003Cplugin> \u003Caction> --i-* --p-* --m-* --o-*`, `qiime tools peek\u002Fexport`\n\nScope: the artifact\u002Fprovenance\u002Ftype machinery and the import\u002Fexport\u002Fmetadata\u002Finterface mechanics - this is the GLUE skill. Denoising params (trunc\u002Ftrim\u002FmaxEE, DADA2 vs Deblur) -> amplicon-processing. Classifier\u002FDB choice + training -> taxonomy-assignment. Diversity metric\u002Fsampling-depth\u002Frarefaction + PERMANOVA-vs-dispersion -> diversity-analysis. DA tool choice\u002Fconsensus -> differential-abundance. PICRUSt2 -> functional-prediction. Shotgun reads (moshpit distribution, Kraken2\u002FMetaPhlAn\u002FHUMAnN) -> metagenomics. This skill shows each scientific action and routes the decision out; it does not re-teach the method.\n\n## The Single Most Important Modern Insight -- A .qza Is Data Plus Its Executable History, Not a File Format\n\nA `.qza` carries the data AND the complete computational graph that produced it. The semantic-type system plus the embedded provenance ARE the reproducibility guarantee - the whole reason to work inside the framework instead of passing loose BIOM\u002FFASTA\u002FNewick files. The cost is exact and unavoidable: there is no `cat`-ing the data. Three corollaries each common misuse violates:\n\n1. **Working THROUGH the framework keeps the chain; exporting breaks it.** `qiime tools export` writes native data and silently drops the QIIME2 wrapper AND the provenance. Export early and go ad-hoc, and the final figure has no history back to the raw reads - the framework overhead was paid and the deliverable thrown away. Export at the LAST step, or use `qiime2R::qza_to_phyloseq` so the chain survives as far as possible.\n2. **Semantic types are a type system for biology.** `core-metrics-phylogenetic` refuses a `FeatureData[Taxonomy]` where a `FeatureTable[Frequency]` belongs, BEFORE running. A type error is the guard WORKING - fix the upstream action that made the wrong type, do not launder it by re-importing.\n3. **A `.qzv` is terminal and a classifier is version-pinned.** A Visualizer's output can never be another action's input (keep the `.qza` it was made from). An sklearn classifier `.qza` trained under 2024.x raises a version-mismatch under 2026.x - the training version is part of the method.\n\nOrganize the analysis around protecting the provenance chain and the type contract, not around listing flags.\n\n## What Is Inside a .qza\n\nA `.qza` (QIIME Zipped Artifact) and `.qzv` (Visualization) are ZIP archives keyed at top level by a UUID. Every artifact carries four things:\n\n1. **UUID** - identifies THIS computation (provenance references inputs\u002Foutputs by UUID), not just a file.\n2. **Semantic TYPE** - what the data MEANS: `FeatureTable[Frequency]`, `SampleData[PairedEndSequencesWithQuality]`, `Phylogeny[Rooted]`, `FeatureData[Taxonomy]`, `FeatureData[Sequence]`, `DistanceMatrix`, `SampleData[AlphaDiversity]`. Types can carry Properties (`SampleData[AlphaDiversity] % Properties('phylogenetic')`).\n3. **FORMAT** - the on-disk layout the bytes live in (e.g. `BIOMV210DirFmt`, a Newick file). Type is the meaning; format is the bytes.\n4. **PROVENANCE** - in a `provenance\u002F` subtree: for every upstream action the plugin\u002Faction name, every parameter value, input\u002Foutput UUIDs, plugin + framework versions, execution environment, timestamp, and BibTeX citations. The references form a DAG of the whole analysis.\n\n```bash\nqiime tools peek table.qza                    # UUID + Type + Format, without unzipping\nqiime tools validate table.qza --level max    # archive integrity + payload conforms to its format\nqiime tools extract --input-path table.qza --output-path extracted\u002F   # FULL archive incl provenance (read by hand)\nqiime tools export  --input-path table.qza --output-path exported\u002F     # ONLY the native data - DROPS provenance\n```\n\n`qiime tools extract` keeps the QIIME2 structure (data + `provenance\u002F`); `qiime tools export` is the one-way door out. A plain `unzip table.qza` works too (it is a standard ZIP).\n\n## Tool \u002F Interface Taxonomy\n\n| Interface \u002F tool | Role | When |\n|------------------|------|------|\n| q2cli (`qiime ...`) | the command-line interface; `--i-*` inputs, `--p-*` params, `--m-*` metadata, `--o-*`\u002F`--output-dir` outputs | default, most-documented, scriptable; what tutorials\u002Fforum answers use |\n| Artifact API (`from qiime2 import Artifact, Metadata`) | the Python 3 interface; `Artifact.load`\u002F`.save`\u002F`.view`, actions importable as functions returning `Results` | notebooks, embedding QIIME2 in a larger Python pipeline (no temp files) |\n| view.qiime2.org | renders any `.qzv` viz AND the `.qza`\u002F`.qzv` provenance DAG client-side, NO install | sharing results and inspecting provenance without QIIME2 installed |\n| provenance-lib (`qiime tools replay-provenance`) | parses an artifact's provenance DAG and regenerates executable code (Keefe 2023) | recovering the commands that made an artifact; reproducing a shared `.qza` |\n\nNeither q2cli nor the Artifact API is \"more reproducible\" - provenance is identical; pick by host environment. An Action is a Method (Artifacts in -> Artifacts out), a Visualizer (-> exactly one terminal `.qzv`), or a Pipeline (-> many Artifacts and\u002For Visualizations, e.g. `core-metrics-phylogenetic`). The Method\u002FVisualizer distinction is WHY a `.qzv` is a dead end. The legacy `q2studio` desktop GUI is dead (last release 2022.8); the no-CLI answers are Galaxy + view.qiime2.org.\n\n## Decision Tree by Scenario\n\n| Scenario | Recommended | Why |\n|----------|-------------|-----|\n| Demultiplexed per-sample FASTQ, filenames are Casava 1.8 | `--type SampleData[PairedEndSequencesWithQuality] --input-format CasavaOneEightSingleLanePerSampleDirFmt` | sample IDs parsed from filenames; no manifest needed |\n| Demultiplexed FASTQ, arbitrary paths | V2 manifest (`PairedEndFastqManifestPhred33V2`) | TSV of absolute paths; the most general\u002Fexplicit on-ramp |\n| Still multiplexed (one big FASTQ + barcodes) | import `EMPPairedEndSequences`, then `qiime demux emp-paired` | demultiplexing is a QIIME2 step, not the import |\n| A feature table built elsewhere | `--input-format BIOMV210Format --type FeatureTable[Frequency]` | BIOM v2.1 (HDF5); attach metadata separately |\n| Scripting a notebook \u002F larger Python pipeline | Artifact API | returns Artifacts directly, no temp files; same provenance |\n| Need to share a result with no-QIIME2 collaborators | upload `.qzv` to view.qiime2.org | renders viz + provenance client-side |\n| Handed a single `.qza`, need the commands that made it | `qiime tools replay-provenance` | regenerates executable code from the provenance DAG |\n| One-off custom R analysis, fighting the framework | `qiime2R::qza_to_phyloseq` \u002F export, own the provenance loss | the overhead is not worth it; be honest about the exit point |\n| Shotgun \u002F WGS reads | -> metagenomics (moshpit distribution) | different distribution and toolchain; cross-link, do not merge |\n\n## Import\n\n**Goal:** Turn raw demultiplexed reads into a typed, provenance-rooted artifact with the correct Phred offset.\n\n**Approach:** Write a V2 manifest (TSV, absolute paths), declare the semantic type and the format whose name encodes the Phred offset, then immediately summarize to confirm the reads decoded sanely.\n\n```bash\n# manifest.tsv (TAB-separated, V2; absolute paths):\n#   sample-id\u003CTAB>forward-absolute-filepath\u003CTAB>reverse-absolute-filepath\nqiime tools import \\\n    --type 'SampleData[PairedEndSequencesWithQuality]' \\\n    --input-path manifest.tsv \\\n    --input-format PairedEndFastqManifestPhred33V2 \\\n    --output-path demux.qza\n# Phred offset is BAKED INTO the format name: Phred33V2 (modern Illumina) vs Phred64V2 (legacy).\n# V1 was CSV with a `direction` column; V2 is TSV with separate forward\u002Freverse columns - prefer V2.\n\nqiime demux summarize --i-data demux.qza --o-visualization demux.qzv   # per-base quality (drives trunc choices)\n```\n\nFor EMP-multiplexed data: import `--type 'EMPPairedEndSequences'`, then `qiime demux emp-paired --i-seqs emp.qza --m-barcodes-file metadata.tsv --m-barcodes-column barcode-sequence --o-per-sample-sequences demux.qza --o-error-correction-details ec.qza`. The per-base quality plot in `demux.qzv` is read by amplicon-processing to pick truncation - not here.\n\n## The Orchestration Skeleton (each science step DEFERS)\n\nThe pipeline shape, with every method choice routed to its owning skill:\n\n```bash\n# Denoise -> ASV table + rep-seqs.  PARAM CHOICE (trunc\u002Ftrim\u002FmaxEE, DADA2 vs Deblur) -> amplicon-processing\nqiime dada2 denoise-paired --i-demultiplexed-seqs demux.qza \\\n    --p-trunc-len-f 0 --p-trunc-len-r 0 \\\n    --o-table table.qza --o-representative-sequences rep-seqs.qza --o-denoising-stats stats.qza\n\nqiime tools peek table.qza    # confirm Type is FeatureTable[Frequency] before wiring downstream\n\n# Taxonomy.  CLASSIFIER + DB choice and training -> taxonomy-assignment\n# Use a classifier .qza trained for THIS release (data.qiime2.org\u002F\u003Crelease>\u002Fcommon\u002F...); old ones break.\nqiime feature-classifier classify-sklearn \\\n    --i-classifier classifier.qza --i-reads rep-seqs.qza --o-classification taxonomy.qza\n\n# Phylogeny (Pipeline) -> rooted tree for UniFrac\u002FFaith PD\nqiime phylogeny align-to-tree-mafft-fasttree --i-sequences rep-seqs.qza \\\n    --o-alignment aln.qza --o-masked-alignment masked-aln.qza \\\n    --o-tree unrooted-tree.qza --o-rooted-tree rooted-tree.qza\n\n# Diversity (Pipeline).  SAMPLING DEPTH + metric + rarefy-or-not -> diversity-analysis (pick depth from alpha-rarefaction)\nqiime diversity core-metrics-phylogenetic --i-phylogeny rooted-tree.qza --i-table table.qza \\\n    --p-sampling-depth 10000 --m-metadata-file metadata.tsv --output-dir core-metrics\u002F\n# PERMANOVA via diversity beta-group-significance; the location-vs-dispersion (betadisper) confound -> diversity-analysis\n\n# Differential abundance - MODERN q2-composition (NOT add-pseudocount+ancom).  Tool choice\u002Fconsensus -> differential-abundance\nqiime composition ancombc --i-table table.qza --m-metadata-file metadata.tsv \\\n    --p-formula 'group' --o-differentials ancombc.qza\nqiime composition da-barplot --i-data ancombc.qza --o-visualization ancombc-barplot.qzv\n```\n\n`core-metrics-phylogenetic` and `align-to-tree-mafft-fasttree` are Pipelines (one call, a directory of artifacts + Emperor `.qzv`s out). `--p-formula` takes column names from the Metadata; annotate integer ID\u002Fbatch columns `categorical` (below) or they enter the model as continuous covariates.\n\n## Metadata\n\nThe Metadata TSV is the spine - the same `--m-metadata-file` drives demux barcodes, group-significance, taxa barplots, ANCOM-BC grouping, and Emperor coloring. First column header is the ID column (`sample-id`, `id`, `#SampleID`, ...). An optional second row `#q2:types` overrides type inference per column (`categorical` \u002F `numeric`):\n\n```\nsample-id\tsubject\tgroup\n#q2:types\tcategorical\tcategorical\ns1\t101\ttreatment\ns2\t102\tcontrol\n```\n\nWithout the `#q2:types` row, a column of only integers is inferred **numeric** - so a subject\u002Fbatch\u002Ftimepoint ID silently becomes a continuous covariate. Annotate ID-like integer columns `categorical`. Validate the sheet with Keemei (Rideout 2016 *GigaScience* 5:27) before running - a malformed metadata file is a top cause of cryptic action failures. `qiime metadata tabulate --m-input-file metadata.tsv --o-visualization metadata.qzv` renders any metadata (including an artifact viewed as metadata, e.g. taxonomy or denoising stats) as a table.\n\n## Provenance Replay\n\n**Goal:** Recover the executable commands that produced an artifact, from the artifact alone.\n\n**Approach:** Parse the embedded provenance DAG and regenerate a q2cli (or Artifact-API) script plus a citations BibTeX.\n\n```bash\nqiime tools replay-provenance --in-fp core-metrics\u002F --out-fp replay.sh --usage-driver cli\nqiime tools replay-citations  --in-fp core-metrics\u002F --out-fp citations.bib\n# --usage-driver selects cli vs python3\u002Fartifact-api output. Verify flag spelling with\n# `qiime tools replay-provenance --help` on the installed build (the interface is still maturing).\n```\n\nReplay recovers the commands; it is not a guaranteed bit-identical rerun across very different releases (plugin versions are part of the record). The aggregated DAG citations are how a methods section's references come straight from provenance, also via the `.qzv` Citations tab on view.qiime2.org.\n\n## Export (the one-way door)\n\n**Goal:** Hand the data to R\u002FPython when the analysis is no longer expressible in QIIME2 - while losing as little provenance as possible.\n\n**Approach:** Stay in artifacts as long as the work is QIIME2-expressible; export (or read into phyloseq) only at the last step, and keep the upstream `.qza`s so the chain survives up to the exit.\n\n```bash\nqiime tools export --input-path table.qza --output-path exported\u002F      # -> exported\u002Ffeature-table.biom\nbiom convert -i exported\u002Ffeature-table.biom -o feature-table.tsv --to-tsv\n# FeatureData[Sequence] -> dna-sequences.fasta; FeatureData[Taxonomy] -> taxonomy.tsv; Phylogeny[Rooted] -> tree.nwk\n```\n\nExport DROPS the QIIME2 wrapper and the provenance - the exported TSV has no history back to the reads. For R, prefer `qiime2R::qza_to_phyloseq('table.qza', 'taxonomy.qza', 'rooted-tree.qza', 'metadata.tsv')` (Bisanz), which reads artifacts directly and assembles a phyloseq object without manual export. Record where the chain ends.\n\n## Per-Method Failure Modes\n\n### Export-early-loses-provenance\n**Trigger:** `qiime tools export` to TSV at step three, then everything else in a notebook. **Mechanism:** export writes native data only and drops the `provenance\u002F` subtree. **Symptom:** the final figure has no provenance back to the raw reads - the framework overhead bought nothing. **Fix:** export at the LAST step; save upstream `.qza`s; or use `qiime2R::qza_to_phyloseq` so the chain survives to the exit.\n\n### Semantic-type mismatch treated as a bug\n**Trigger:** feeding a `Phylogeny[Unrooted]` or a `FeatureData[Taxonomy]` where a `FeatureTable[Frequency]` is required. **Mechanism:** the type system refuses incompatible inputs at the interface boundary before running. **Symptom:** \"expected an artifact of type ...\" error. **Fix:** this is the guard WORKING; `qiime tools peek` to read the actual Type, then fix the UPSTREAM action that produced the wrong type - do not re-import to coerce it.\n\n### Classifier \u002F artifact version break across releases\n**Trigger:** a `silva-138-99-nb-classifier.qza` from 2024.x used under 2026.x. **Mechanism:** the sklearn naive-Bayes classifier is pinned to its scikit-learn version; provenance replay assumes recorded plugin versions. **Symptom:** scikit-learn version-mismatch warning\u002Ferror, or refusal to load. **Fix:** download\u002Ftrain the classifier for YOUR release (the `data.qiime2.org\u002F\u003Crelease>\u002Fcommon\u002F...` URLs are release-namespaced); retrain or pin the whole env if reusing an old one.\n\n### Manifest Phred \u002F format error on import\n**Trigger:** `Phred64V2` on modern Illumina, V1-vs-V2 manifest confusion, relative paths, or `SampleData[...]` for still-multiplexed EMP data. **Mechanism:** the Phred offset is baked into the format name and is applied without checking. **Symptom:** silently mis-decoded quality scores, or an import that \"works\" but `demux summarize` shows garbage qualities. **Fix:** modern Illumina = Phred33; V2 TSV manifests with absolute paths; `qiime demux summarize` immediately after import; EMP data needs `EMPPairedEndSequences` + `qiime demux`.\n\n### A .qzv treated as data\n**Trigger:** trying to feed a `.qzv` into the next action. **Mechanism:** a Visualizer's output is terminal by the framework's type contract. **Symptom:** the action will not accept it as an input. **Fix:** keep and feed the `.qza` the Visualizer was MADE from; a `.qzv` is for viewing only (browser or view.qiime2.org).\n\n### Metadata numeric cast\n**Trigger:** an integer subject\u002Fbatch\u002Ftimepoint column with no `#q2:types` row. **Mechanism:** inference casts an all-integer column to numeric. **Symptom:** an ID enters a model as a continuous covariate; nonsensical group results. **Fix:** add a `#q2:types` row annotating ID-like columns `categorical`; validate with Keemei.\n\n### Mixing distributions\n**Trigger:** expecting amplicon plugins in `moshpit`, or shotgun assembly in `amplicon`. **Mechanism:** distributions are curated, partially-disjoint plugin sets. **Symptom:** \"plugin not found.\" **Fix:** amplicon\u002Fmarker-gene -> `amplicon` distribution (renamed `qiime2` in 2026.4); shotgun -> `moshpit` (and -> metagenomics); pin both distribution and release.\n\n## Quantitative Thresholds\n\n| Threshold | Source | Rationale |\n|-----------|--------|-----------|\n| `--sampling-depth` (rarefaction depth) | -> diversity-analysis | required by `core-metrics`; pick from `alpha-rarefaction`, not a default - the 10000 in examples is a placeholder |\n| `--p-formula` integer columns annotated `categorical` | use.qiime2.org metadata reference | otherwise inferred numeric and used as a continuous covariate |\n| Phred offset = 33 (modern Illumina) | Illumina format history | Phred64 only for pre-2011 pipelines; wrong choice silently mis-decodes quality |\n| Classifier release-match | Bokulich 2018 *Microbiome* 6:90 | the classifier is pinned to its scikit-learn version; cross-release reuse breaks |\n| denoise \u002F taxonomy \u002F DA tuning | -> the owning sibling skill | this skill owns no scientific thresholds by design |\n\nMost scientific magic numbers live in the five sibling skills, not here - this skill owns the machinery.\n\n## Common Errors\n\n| Error \u002F symptom | Cause | Solution |\n|-----------------|-------|----------|\n| \"The scikit-learn version ... could not be found\" \u002F classifier won't load | classifier `.qza` trained under a different release | use the release-namespaced classifier or retrain under the current release |\n| \"Argument ... is not a subtype of ...\" \u002F type error | wrong semantic type wired into an action | `qiime tools peek`; fix the upstream action, do not re-import |\n| `demux summarize` shows nonsense quality scores | wrong Phred offset in the import format name | re-import with `...Phred33V2`; modern Illumina is Phred33 |\n| Import fails on the manifest | V1\u002FV2 confusion, relative paths, wrong delimiter | V2 TSV, absolute paths, tab-separated header `sample-id` |\n| A `.qzv` rejected as an action input | Visualizations are terminal | feed the `.qza` it was made from |\n| Action treats an ID column as continuous | no `#q2:types` row | annotate the column `categorical`; validate with Keemei |\n| Plugin not found | wrong distribution installed | install the `amplicon` (a.k.a. `qiime2` in 2026.4) distribution |\n\n## References\n\n- Bolyen E, Rideout JR, Dillon MR, Bokulich NA, ..., Caporaso JG. 2019. Reproducible, interactive, scalable and extensible microbiome data science using QIIME 2. *Nat Biotechnol* 37:852-857.\n- Keefe CR, Dillon MR, Gehret E, Herman C, Jewell M, Wood CV, Bolyen E, Caporaso JG. 2023. Facilitating bioinformatics reproducibility with QIIME 2 Provenance Replay. *PLoS Comput Biol* 19(11):e1011676.\n- Lin H, Peddada SD. 2020. Analysis of compositions of microbiomes with bias correction. *Nat Commun* 11:3514.\n- Rideout JR, Chase JH, Bolyen E, Ackermann G, Gonzalez A, Knight R, Caporaso JG. 2016. Keemei: cloud-based validation of tabular bioinformatics file formats in Google Sheets. *GigaScience* 5:27.\n- Bokulich NA, Kaehler BD, Rideout JR, Dillon M, Bolyen E, Knight R, Huttley GA, Caporaso JG. 2018. Optimizing taxonomic classification of marker-gene amplicon sequences with QIIME 2's q2-feature-classifier plugin. *Microbiome* 6:90.\n\n## Related Skills\n\n- amplicon-processing - DADA2 denoising parameters this skill defers (trunc\u002Ftrim\u002FmaxEE, DADA2 vs Deblur)\n- taxonomy-assignment - Classifier and reference-database choice and training behind classify-sklearn\n- diversity-analysis - Sampling depth, diversity metric, rarefaction, and the PERMANOVA-vs-dispersion confound\n- differential-abundance - DA tool choice and consensus behind composition ancombc\n- functional-prediction - PICRUSt2 functional prediction from the feature table\n- metagenomics\u002Fkraken-classification - Shotgun (moshpit distribution) read classification, not amplicon\n- phylogenetics\u002Ftree-io - Phylogenetic tree I\u002FO for UniFrac \u002F Faith PD\n- read-qc\u002Fadapter-trimming - cutadapt primer removal before import\u002Fdenoising\n- workflows\u002Fmicrobiome-pipeline - End-to-end amplicon pipeline\n","## Version Compatibility\n\nReference examples tested with: QIIME2 2026.1+ (amplicon distribution; framework now `rachis`), provenance-lib 2024.10+.\n\nBefore using code patterns, verify installed versions match. If versions differ:\n- CLI: `qiime --version`, `qiime info`, then `qiime \u003Cplugin> \u003Caction> --help` to confirm flags\n\nIf code throws ImportError, AttributeError, or TypeError, introspect the installed\npackage and adapt the example to match the actual API rather than retrying.\n\nThe QIIME2 release tag (calendar-versioned `YYYY.RELEASE`, e.g. `2026.1`) defines the plugin API AND the `.qza` artifact format; an sklearn taxonomy classifier `.qza` trained under one release may need retraining under another (the classifier is pinned to its scikit-learn version). The conda env name encodes the release and distribution (`qiime2-amplicon-2026.1`; renamed toward `rachis-qiime2-\u003Crelease>` in 2026.4). Names and the install YAML URL are moving targets - verify the current release and distribution names against the live install page before pinning anything.\n\n# QIIME2 Amplicon Workflow\n\n**\"Run my amplicon study through QIIME2\"** -> Move data through the framework as typed, provenance-carrying artifacts and defer every scientific choice to the owning skill - because a `.qza` is not a file, it is data plus its entire executable history, and that history is the deliverable.\n- CLI: `qiime tools import`, `qiime \u003Cplugin> \u003Caction> --i-* --p-* --m-* --o-*`, `qiime tools peek\u002Fexport`\n\nScope: the artifact\u002Fprovenance\u002Ftype machinery and the import\u002Fexport\u002Fmetadata\u002Finterface mechanics - this is the GLUE skill. Denoising params (trunc\u002Ftrim\u002FmaxEE, DADA2 vs Deblur) -> amplicon-processing. Classifier\u002FDB choice + training -> taxonomy-assignment. Diversity metric\u002Fsampling-depth\u002Frarefaction + PERMANOVA-vs-dispersion -> diversity-analysis. DA tool choice\u002Fconsensus -> differential-abundance. PICRUSt2 -> functional-prediction. Shotgun reads (moshpit distribution, Kraken2\u002FMetaPhlAn\u002FHUMAnN) -> metagenomics. This skill shows each scientific action and routes the decision out; it does not re-teach the method.\n\n## The Single Most Important Modern Insight -- A .qza Is Data Plus Its Executable History, Not a File Format\n\nA `.qza` carries the data AND the complete computational graph that produced it. The semantic-type system plus the embedded provenance ARE the reproducibility guarantee - the whole reason to work inside the framework instead of passing loose BIOM\u002FFASTA\u002FNewick files. The cost is exact and unavoidable: there is no `cat`-ing the data. Three corollaries each common misuse violates:\n\n1. **Working THROUGH the framework keeps the chain; exporting breaks it.** `qiime tools export` writes native data and silently drops the QIIME2 wrapper AND the provenance. Export early and go ad-hoc, and the final figure has no history back to the raw reads - the framework overhead was paid and the deliverable thrown away. Export at the LAST step, or use `qiime2R::qza_to_phyloseq` so the chain survives as far as possible.\n2. **Semantic types are a type system for biology.** `core-metrics-phylogenetic` refuses a `FeatureData[Taxonomy]` where a `FeatureTable[Frequency]` belongs, BEFORE running. A type error is the guard WORKING - fix the upstream action that made the wrong type, do not launder it by re-importing.\n3. **A `.qzv` is terminal and a classifier is version-pinned.** A Visualizer's output can never be another action's input (keep the `.qza` it was made from). An sklearn classifier `.qza` trained under 2024.x raises a version-mismatch under 2026.x - the training version is part of the method.\n\nOrganize the analysis around protecting the provenance chain and the type contract, not around listing flags.\n\n## What Is Inside a .qza\n\nA `.qza` (QIIME Zipped Artifact) and `.qzv` (Visualization) are ZIP archives keyed at top level by a UUID. Every artifact carries four things:\n\n1. **UUID** - identifies THIS computation (provenance references inputs\u002Foutputs by UUID), not just a file.\n2. **Semantic TYPE** - what the data MEANS: `FeatureTable[Frequency]`, `SampleData[PairedEndSequencesWithQuality]`, `Phylogeny[Rooted]`, `FeatureData[Taxonomy]`, `FeatureData[Sequence]`, `DistanceMatrix`, `SampleData[AlphaDiversity]`. Types can carry Properties (`SampleData[AlphaDiversity] % Properties('phylogenetic')`).\n3. **FORMAT** - the on-disk layout the bytes live in (e.g. `BIOMV210DirFmt`, a Newick file). Type is the meaning; format is the bytes.\n4. **PROVENANCE** - in a `provenance\u002F` subtree: for every upstream action the plugin\u002Faction name, every parameter value, input\u002Foutput UUIDs, plugin + framework versions, execution environment, timestamp, and BibTeX citations. The references form a DAG of the whole analysis.\n\n```bash\nqiime tools peek table.qza                    # UUID + Type + Format, without unzipping\nqiime tools validate table.qza --level max    # archive integrity + payload conforms to its format\nqiime tools extract --input-path table.qza --output-path extracted\u002F   # FULL archive incl provenance (read by hand)\nqiime tools export  --input-path table.qza --output-path exported\u002F     # ONLY the native data - DROPS provenance\n```\n\n`qiime tools extract` keeps the QIIME2 structure (data + `provenance\u002F`); `qiime tools export` is the one-way door out. A plain `unzip table.qza` works too (it is a standard ZIP).\n\n## Tool \u002F Interface Taxonomy\n\n| Interface \u002F tool | Role | When |\n|------------------|------|------|\n| q2cli (`qiime ...`) | the command-line interface; `--i-*` inputs, `--p-*` params, `--m-*` metadata, `--o-*`\u002F`--output-dir` outputs | default, most-documented, scriptable; what tutorials\u002Fforum answers use |\n| Artifact API (`from qiime2 import Artifact, Metadata`) | the Python 3 interface; `Artifact.load`\u002F`.save`\u002F`.view`, actions importable as functions returning `Results` | notebooks, embedding QIIME2 in a larger Python pipeline (no temp files) |\n| view.qiime2.org | renders any `.qzv` viz AND the `.qza`\u002F`.qzv` provenance DAG client-side, NO install | sharing results and inspecting provenance without QIIME2 installed |\n| provenance-lib (`qiime tools replay-provenance`) | parses an artifact's provenance DAG and regenerates executable code (Keefe 2023) | recovering the commands that made an artifact; reproducing a shared `.qza` |\n\nNeither q2cli nor the Artifact API is \"more reproducible\" - provenance is identical; pick by host environment. An Action is a Method (Artifacts in -> Artifacts out), a Visualizer (-> exactly one terminal `.qzv`), or a Pipeline (-> many Artifacts and\u002For Visualizations, e.g. `core-metrics-phylogenetic`). The Method\u002FVisualizer distinction is WHY a `.qzv` is a dead end. The legacy `q2studio` desktop GUI is dead (last release 2022.8); the no-CLI answers are Galaxy + view.qiime2.org.\n\n## Decision Tree by Scenario\n\n| Scenario | Recommended | Why |\n|----------|-------------|-----|\n| Demultiplexed per-sample FASTQ, filenames are Casava 1.8 | `--type SampleData[PairedEndSequencesWithQuality] --input-format CasavaOneEightSingleLanePerSampleDirFmt` | sample IDs parsed from filenames; no manifest needed |\n| Demultiplexed FASTQ, arbitrary paths | V2 manifest (`PairedEndFastqManifestPhred33V2`) | TSV of absolute paths; the most general\u002Fexplicit on-ramp |\n| Still multiplexed (one big FASTQ + barcodes) | import `EMPPairedEndSequences`, then `qiime demux emp-paired` | demultiplexing is a QIIME2 step, not the import |\n| A feature table built elsewhere | `--input-format BIOMV210Format --type FeatureTable[Frequency]` | BIOM v2.1 (HDF5); attach metadata separately |\n| Scripting a notebook \u002F larger Python pipeline | Artifact API | returns Artifacts directly, no temp files; same provenance |\n| Need to share a result with no-QIIME2 collaborators | upload `.qzv` to view.qiime2.org | renders viz + provenance client-side |\n| Handed a single `.qza`, need the commands that made it | `qiime tools replay-provenance` | regenerates executable code from the provenance DAG |\n| One-off custom R analysis, fighting the framework | `qiime2R::qza_to_phyloseq` \u002F export, own the provenance loss | the overhead is not worth it; be honest about the exit point |\n| Shotgun \u002F WGS reads | -> metagenomics (moshpit distribution) | different distribution and toolchain; cross-link, do not merge |\n\n## Import\n\n**Goal:** Turn raw demultiplexed reads into a typed, provenance-rooted artifact with the correct Phred offset.\n\n**Approach:** Write a V2 manifest (TSV, absolute paths), declare the semantic type and the format whose name encodes the Phred offset, then immediately summarize to confirm the reads decoded sanely.\n\n```bash\n# manifest.tsv (TAB-separated, V2; absolute paths):\n#   sample-id\u003CTAB>forward-absolute-filepath\u003CTAB>reverse-absolute-filepath\nqiime tools import \\\n    --type 'SampleData[PairedEndSequencesWithQuality]' \\\n    --input-path manifest.tsv \\\n    --input-format PairedEndFastqManifestPhred33V2 \\\n    --output-path demux.qza\n# Phred offset is BAKED INTO the format name: Phred33V2 (modern Illumina) vs Phred64V2 (legacy).\n# V1 was CSV with a `direction` column; V2 is TSV with separate forward\u002Freverse columns - prefer V2.\n\nqiime demux summarize --i-data demux.qza --o-visualization demux.qzv   # per-base quality (drives trunc choices)\n```\n\nFor EMP-multiplexed data: import `--type 'EMPPairedEndSequences'`, then `qiime demux emp-paired --i-seqs emp.qza --m-barcodes-file metadata.tsv --m-barcodes-column barcode-sequence --o-per-sample-sequences demux.qza --o-error-correction-details ec.qza`. The per-base quality plot in `demux.qzv` is read by amplicon-processing to pick truncation - not here.\n\n## The Orchestration Skeleton (each science step DEFERS)\n\nThe pipeline shape, with every method choice routed to its owning skill:\n\n```bash\n# Denoise -> ASV table + rep-seqs.  PARAM CHOICE (trunc\u002Ftrim\u002FmaxEE, DADA2 vs Deblur) -> amplicon-processing\nqiime dada2 denoise-paired --i-demultiplexed-seqs demux.qza \\\n    --p-trunc-len-f 0 --p-trunc-len-r 0 \\\n    --o-table table.qza --o-representative-sequences rep-seqs.qza --o-denoising-stats stats.qza\n\nqiime tools peek table.qza    # confirm Type is FeatureTable[Frequency] before wiring downstream\n\n# Taxonomy.  CLASSIFIER + DB choice and training -> taxonomy-assignment\n# Use a classifier .qza trained for THIS release (data.qiime2.org\u002F\u003Crelease>\u002Fcommon\u002F...); old ones break.\nqiime feature-classifier classify-sklearn \\\n    --i-classifier classifier.qza --i-reads rep-seqs.qza --o-classification taxonomy.qza\n\n# Phylogeny (Pipeline) -> rooted tree for UniFrac\u002FFaith PD\nqiime phylogeny align-to-tree-mafft-fasttree --i-sequences rep-seqs.qza \\\n    --o-alignment aln.qza --o-masked-alignment masked-aln.qza \\\n    --o-tree unrooted-tree.qza --o-rooted-tree rooted-tree.qza\n\n# Diversity (Pipeline).  SAMPLING DEPTH + metric + rarefy-or-not -> diversity-analysis (pick depth from alpha-rarefaction)\nqiime diversity core-metrics-phylogenetic --i-phylogeny rooted-tree.qza --i-table table.qza \\\n    --p-sampling-depth 10000 --m-metadata-file metadata.tsv --output-dir core-metrics\u002F\n# PERMANOVA via diversity beta-group-significance; the location-vs-dispersion (betadisper) confound -> diversity-analysis\n\n# Differential abundance - MODERN q2-composition (NOT add-pseudocount+ancom).  Tool choice\u002Fconsensus -> differential-abundance\nqiime composition ancombc --i-table table.qza --m-metadata-file metadata.tsv \\\n    --p-formula 'group' --o-differentials ancombc.qza\nqiime composition da-barplot --i-data ancombc.qza --o-visualization ancombc-barplot.qzv\n```\n\n`core-metrics-phylogenetic` and `align-to-tree-mafft-fasttree` are Pipelines (one call, a directory of artifacts + Emperor `.qzv`s out). `--p-formula` takes column names from the Metadata; annotate integer ID\u002Fbatch columns `categorical` (below) or they enter the model as continuous covariates.\n\n## Metadata\n\nThe Metadata TSV is the spine - the same `--m-metadata-file` drives demux barcodes, group-significance, taxa barplots, ANCOM-BC grouping, and Emperor coloring. First column header is the ID column (`sample-id`, `id`, `#SampleID`, ...). An optional second row `#q2:types` overrides type inference per column (`categorical` \u002F `numeric`):\n\n```\nsample-id\tsubject\tgroup\n#q2:types\tcategorical\tcategorical\ns1\t101\ttreatment\ns2\t102\tcontrol\n```\n\nWithout the `#q2:types` row, a column of only integers is inferred **numeric** - so a subject\u002Fbatch\u002Ftimepoint ID silently becomes a continuous covariate. Annotate ID-like integer columns `categorical`. Validate the sheet with Keemei (Rideout 2016 *GigaScience* 5:27) before running - a malformed metadata file is a top cause of cryptic action failures. `qiime metadata tabulate --m-input-file metadata.tsv --o-visualization metadata.qzv` renders any metadata (including an artifact viewed as metadata, e.g. taxonomy or denoising stats) as a table.\n\n## Provenance Replay\n\n**Goal:** Recover the executable commands that produced an artifact, from the artifact alone.\n\n**Approach:** Parse the embedded provenance DAG and regenerate a q2cli (or Artifact-API) script plus a citations BibTeX.\n\n```bash\nqiime tools replay-provenance --in-fp core-metrics\u002F --out-fp replay.sh --usage-driver cli\nqiime tools replay-citations  --in-fp core-metrics\u002F --out-fp citations.bib\n# --usage-driver selects cli vs python3\u002Fartifact-api output. Verify flag spelling with\n# `qiime tools replay-provenance --help` on the installed build (the interface is still maturing).\n```\n\nReplay recovers the commands; it is not a guaranteed bit-identical rerun across very different releases (plugin versions are part of the record). The aggregated DAG citations are how a methods section's references come straight from provenance, also via the `.qzv` Citations tab on view.qiime2.org.\n\n## Export (the one-way door)\n\n**Goal:** Hand the data to R\u002FPython when the analysis is no longer expressible in QIIME2 - while losing as little provenance as possible.\n\n**Approach:** Stay in artifacts as long as the work is QIIME2-expressible; export (or read into phyloseq) only at the last step, and keep the upstream `.qza`s so the chain survives up to the exit.\n\n```bash\nqiime tools export --input-path table.qza --output-path exported\u002F      # -> exported\u002Ffeature-table.biom\nbiom convert -i exported\u002Ffeature-table.biom -o feature-table.tsv --to-tsv\n# FeatureData[Sequence] -> dna-sequences.fasta; FeatureData[Taxonomy] -> taxonomy.tsv; Phylogeny[Rooted] -> tree.nwk\n```\n\nExport DROPS the QIIME2 wrapper and the provenance - the exported TSV has no history back to the reads. For R, prefer `qiime2R::qza_to_phyloseq('table.qza', 'taxonomy.qza', 'rooted-tree.qza', 'metadata.tsv')` (Bisanz), which reads artifacts directly and assembles a phyloseq object without manual export. Record where the chain ends.\n\n## Per-Method Failure Modes\n\n### Export-early-loses-provenance\n**Trigger:** `qiime tools export` to TSV at step three, then everything else in a notebook. **Mechanism:** export writes native data only and drops the `provenance\u002F` subtree. **Symptom:** the final figure has no provenance back to the raw reads - the framework overhead bought nothing. **Fix:** export at the LAST step; save upstream `.qza`s; or use `qiime2R::qza_to_phyloseq` so the chain survives to the exit.\n\n### Semantic-type mismatch treated as a bug\n**Trigger:** feeding a `Phylogeny[Unrooted]` or a `FeatureData[Taxonomy]` where a `FeatureTable[Frequency]` is required. **Mechanism:** the type system refuses incompatible inputs at the interface boundary before running. **Symptom:** \"expected an artifact of type ...\" error. **Fix:** this is the guard WORKING; `qiime tools peek` to read the actual Type, then fix the UPSTREAM action that produced the wrong type - do not re-import to coerce it.\n\n### Classifier \u002F artifact version break across releases\n**Trigger:** a `silva-138-99-nb-classifier.qza` from 2024.x used under 2026.x. **Mechanism:** the sklearn naive-Bayes classifier is pinned to its scikit-learn version; provenance replay assumes recorded plugin versions. **Symptom:** scikit-learn version-mismatch warning\u002Ferror, or refusal to load. **Fix:** download\u002Ftrain the classifier for YOUR release (the `data.qiime2.org\u002F\u003Crelease>\u002Fcommon\u002F...` URLs are release-namespaced); retrain or pin the whole env if reusing an old one.\n\n### Manifest Phred \u002F format error on import\n**Trigger:** `Phred64V2` on modern Illumina, V1-vs-V2 manifest confusion, relative paths, or `SampleData[...]` for still-multiplexed EMP data. **Mechanism:** the Phred offset is baked into the format name and is applied without checking. **Symptom:** silently mis-decoded quality scores, or an import that \"works\" but `demux summarize` shows garbage qualities. **Fix:** modern Illumina = Phred33; V2 TSV manifests with absolute paths; `qiime demux summarize` immediately after import; EMP data needs `EMPPairedEndSequences` + `qiime demux`.\n\n### A .qzv treated as data\n**Trigger:** trying to feed a `.qzv` into the next action. **Mechanism:** a Visualizer's output is terminal by the framework's type contract. **Symptom:** the action will not accept it as an input. **Fix:** keep and feed the `.qza` the Visualizer was MADE from; a `.qzv` is for viewing only (browser or view.qiime2.org).\n\n### Metadata numeric cast\n**Trigger:** an integer subject\u002Fbatch\u002Ftimepoint column with no `#q2:types` row. **Mechanism:** inference casts an all-integer column to numeric. **Symptom:** an ID enters a model as a continuous covariate; nonsensical group results. **Fix:** add a `#q2:types` row annotating ID-like columns `categorical`; validate with Keemei.\n\n### Mixing distributions\n**Trigger:** expecting amplicon plugins in `moshpit`, or shotgun assembly in `amplicon`. **Mechanism:** distributions are curated, partially-disjoint plugin sets. **Symptom:** \"plugin not found.\" **Fix:** amplicon\u002Fmarker-gene -> `amplicon` distribution (renamed `qiime2` in 2026.4); shotgun -> `moshpit` (and -> metagenomics); pin both distribution and release.\n\n## Quantitative Thresholds\n\n| Threshold | Source | Rationale |\n|-----------|--------|-----------|\n| `--sampling-depth` (rarefaction depth) | -> diversity-analysis | required by `core-metrics`; pick from `alpha-rarefaction`, not a default - the 10000 in examples is a placeholder |\n| `--p-formula` integer columns annotated `categorical` | use.qiime2.org metadata reference | otherwise inferred numeric and used as a continuous covariate |\n| Phred offset = 33 (modern Illumina) | Illumina format history | Phred64 only for pre-2011 pipelines; wrong choice silently mis-decodes quality |\n| Classifier release-match | Bokulich 2018 *Microbiome* 6:90 | the classifier is pinned to its scikit-learn version; cross-release reuse breaks |\n| denoise \u002F taxonomy \u002F DA tuning | -> the owning sibling skill | this skill owns no scientific thresholds by design |\n\nMost scientific magic numbers live in the five sibling skills, not here - this skill owns the machinery.\n\n## Common Errors\n\n| Error \u002F symptom | Cause | Solution |\n|-----------------|-------|----------|\n| \"The scikit-learn version ... could not be found\" \u002F classifier won't load | classifier `.qza` trained under a different release | use the release-namespaced classifier or retrain under the current release |\n| \"Argument ... is not a subtype of ...\" \u002F type error | wrong semantic type wired into an action | `qiime tools peek`; fix the upstream action, do not re-import |\n| `demux summarize` shows nonsense quality scores | wrong Phred offset in the import format name | re-import with `...Phred33V2`; modern Illumina is Phred33 |\n| Import fails on the manifest | V1\u002FV2 confusion, relative paths, wrong delimiter | V2 TSV, absolute paths, tab-separated header `sample-id` |\n| A `.qzv` rejected as an action input | Visualizations are terminal | feed the `.qza` it was made from |\n| Action treats an ID column as continuous | no `#q2:types` row | annotate the column `categorical`; validate with Keemei |\n| Plugin not found | wrong distribution installed | install the `amplicon` (a.k.a. `qiime2` in 2026.4) distribution |\n\n## References\n\n- Bolyen E, Rideout JR, Dillon MR, Bokulich NA, ..., Caporaso JG. 2019. Reproducible, interactive, scalable and extensible microbiome data science using QIIME 2. *Nat Biotechnol* 37:852-857.\n- Keefe CR, Dillon MR, Gehret E, Herman C, Jewell M, Wood CV, Bolyen E, Caporaso JG. 2023. Facilitating bioinformatics reproducibility with QIIME 2 Provenance Replay. *PLoS Comput Biol* 19(11):e1011676.\n- Lin H, Peddada SD. 2020. Analysis of compositions of microbiomes with bias correction. *Nat Commun* 11:3514.\n- Rideout JR, Chase JH, Bolyen E, Ackermann G, Gonzalez A, Knight R, Caporaso JG. 2016. Keemei: cloud-based validation of tabular bioinformatics file formats in Google Sheets. *GigaScience* 5:27.\n- Bokulich NA, Kaehler BD, Rideout JR, Dillon M, Bolyen E, Knight R, Huttley GA, Caporaso JG. 2018. Optimizing taxonomic classification of marker-gene amplicon sequences with QIIME 2's q2-feature-classifier plugin. *Microbiome* 6:90.\n\n## Related Skills\n\n- amplicon-processing - DADA2 denoising parameters this skill defers (trunc\u002Ftrim\u002FmaxEE, DADA2 vs Deblur)\n- taxonomy-assignment - Classifier and reference-database choice and training behind classify-sklearn\n- diversity-analysis - Sampling depth, diversity metric, rarefaction, and the PERMANOVA-vs-dispersion confound\n- differential-abundance - DA tool choice and consensus behind composition ancombc\n- functional-prediction - PICRUSt2 functional prediction from the feature table\n- metagenomics\u002Fkraken-classification - Shotgun (moshpit distribution) read classification, not amplicon\n- phylogenetics\u002Ftree-io - Phylogenetic tree I\u002FO for UniFrac \u002F Faith PD\n- read-qc\u002Fadapter-trimming - cutadapt primer removal before import\u002Fdenoising\n- workflows\u002Fmicrobiome-pipeline - End-to-end amplicon pipeline\n",{"name":5,"source":24,"license":15,"tool_type":25,"description":7,"imported_at":26,"source_path":27,"primary_tool":28,"source_repository":29},"https:\u002F\u002Fgithub.com\u002FGPTomics\u002FbioSkills","cli","2026-09-20","microbiome\u002Fqiime2-workflow\u002FSKILL.md","QIIME2","GPTomics\u002FbioSkills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fbiology\u002Fbio-microbiome-qiime2-workflow","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill bio-microbiome-qiime2-workflow",{"tool":42,"command":43},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill bio-microbiome-qiime2-workflow",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill bio-microbiome-qiime2-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fbiology\u002Fbio-microbiome-qiime2-workflow\u002FSKILL.md",true,[50,56],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"examples\u002Fqiime2_16s.sh","SCRIPT","脚本",4991,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fbiology\u002Fbio-microbiome-qiime2-workflow\u002Fexamples\u002Fqiime2_16s.sh",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"usage-guide.md","REFERENCE","参考文档",7567,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fbiology\u002Fbio-microbiome-qiime2-workflow\u002Fusage-guide.md",[63,71,78,85,92,99],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":70},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":70},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":70},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":70},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":70},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":70},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]