メニュー
Use when an agent must combine taxonomy, accession manifest, specificity, primer QC, and panel reports into a reproducible design release report.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when an agent needs to call the VirusPrimerPro Agent API instead of the GUI, or prepare viral genome inputs for it: request/use API keys, download viral genomes from NCBI, install/run MAFFT, check and repair abnormal sequences, prepare phylogenetic trees/annotations, upload aligned FASTA/tree/GenBank files, poll runs, and fetch artifacts.
Use when an agent needs a stricter or publication-grade phylogeny workflow for PhyloGuide, including tree/MSA validation, FastTree/IQ-TREE planning, and external-tree checks.
Use when an agent must define viral genotype, subtype, clade, lineage, target/background groups, or PhyloGuide groups from cited literature before primer or tNGS panel design.
Use when an agent must split tNGS or multiplex primer pairs into pools while minimizing primer-primer interaction risk and reporting pool overflows.
Use when an agent must evaluate primer candidates for wet-lab constraints such as length, GC, Tm, degeneracy, self-complementarity, pair complementarity, and amplicon size.
Use when an agent must select, filter, deduplicate, and document NCBI/GenBank/reference viral genomes before alignment, primer design, PhyloGuide, or tNGS panel design.
| name | validation-report |
| description | Use when an agent must combine taxonomy, accession manifest, specificity, primer QC, and panel reports into a reproducible design release report. |
Use this as the final release gate before reporting a primer or tNGS panel as ready for review.
python agentskill/scripts/primer_panel_qc.py validation-report \
--taxonomy-report taxonomy_report.json \
--accession-manifest accession_manifest.json \
--primer-qc primer_qc.json \
--specificity-report specificity_report.json \
--panel-json pooled_panel.json \
--output validation_report.md \
--json-output validation_report.json
The report must preserve input paths, statuses, counts, warnings, and release-gate notes. Do not hide failed sections; fix upstream inputs instead.