taxonomy-helper
Use the optional gimme_taxa workflow to resolve taxon names or parent TaxIDs into descendant TaxIDs or taxon metadata for ncbi-genome-download.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- taxonomy-helper
- license
- Apache 2.0
- metadata
- { "disco-role": "operating" }
- description
- Use the optional gimme_taxa workflow to resolve taxon names or parent TaxIDs into descendant TaxIDs or taxon metadata for ncbi-genome-download.
- disable-model-invocation
- true
02 资源文件 3
- 参考文档references/dependencies-and-troubleshooting.md5.6 KB
- 参考文档references/workflow.md5.3 KB
- 脚本scripts/gimme_taxa.py6.9 KB
03 SKILL.md 正文
Taxonomy helper
gimme_taxa.py is an optional, experimental contributed workflow. It uses
ETE3's NCBITaxa interface and a local NCBI taxonomy database to resolve each
comma-separated positional input (a taxon name, a numeric TaxID, or both) and
then either emit descendants or describe the supplied taxa. It is a separate
preparation step; it is not part of the main download CLI.
Use the bundled helper at scripts/gimme_taxa.py, not
an original source checkout. The helper's parser preserves the public spellings
-v/--verbose, -d/--database, -u/--update, -j/--just-taxids,
-i/--taxon-info, and -o/--outfile.
Choose an output mode
- Download input (
-j/--just-taxids): write one descendant TaxID per line, with no header. This is the only output mode intended for direct use as anncbi-genome-download --taxidsinput file. See../download-and-filter/SKILL.mdfor the consuming download command and its filters. - Default descendant report: write a header followed by tab-separated rows
with
parent_taxid,descendent_taxid, anddescendent_name. This is for inspection, not direct--taxidsconsumption. - Taxon metadata (
-i/--taxon-info): write a header followed by tab-separatedname,taxid,rank, andlineagecolumns for the supplied taxa. If-iand-jare both supplied, the source'staxon-infobranch takes precedence.
The source spelling descendent in the default header is intentional. Do not
silently deduplicate or reorder rows: the helper emits the returned ETE3
sequence once for each supplied parent. The actual names and descendants are
properties of the local taxonomy database and were not live-queried during
verification.
Safety boundary
A lookup can have network and filesystem side effects. Constructing
NCBITaxa may create or download a local taxonomy SQLite database when no
usable database exists. --update (-u) explicitly asks ETE3 to refresh that
database and can take several minutes and require network access. Prefer an
explicit, writable --database path in a controlled workspace, record that
path, and use the same path on later runs. Do not enable --update merely to
produce help or to test parsing.
The helper requires a Python environment in which ETE3 and its expected
runtime dependencies six and numpy are installed. Installation and
database acquisition are deliberately outside the download skill's normal
verification: no live taxonomy database query was run. First run --help,
then make a deliberate decision about dependency installation, database
location, and network access before querying.
For checksums, file existence, and downstream output validation, follow
../output-and-integrity/SKILL.md. Treat the
TaxID file as generated input: inspect its headerless, one-ID-per-line format
before passing it onward.
Minimal handoff pattern
# Set this to the generated skill directory; the commands below are portable.
export SKILL_ROOT="${SKILL_ROOT:?Set SKILL_ROOT to the generated skill directory}"
WORKDIR="$(mktemp -d)"
# Parser-only check; this does not instantiate ETE3 or access the network.
python "$SKILL_ROOT/sub-skills/taxonomy-helper/scripts/gimme_taxa.py" --help
# Deliberate lookup: choose a writable database and output file first.
python "$SKILL_ROOT/sub-skills/taxonomy-helper/scripts/gimme_taxa.py" \
--database "$WORKDIR/taxonomy.sqlite" \
--just-taxids \
--outfile "$WORKDIR/descendant-taxids.txt" \
Escherichia
# Consume only after inspecting the generated file.
ncbi-genome-download --taxids "$WORKDIR/descendant-taxids.txt" bacteria
The lookup command may download/create the database. Add --update only when
refreshing it is intended, and use -v or -vv when diagnostic output is
needed. Keep helper diagnostics on stderr and the data file on --outfile (or
stdout when --outfile is omitted) so shell redirection cannot accidentally
mix status text into the TaxID file.
04 同仓库更多 Skills
passnet-triton-opt
Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block/grid/warp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.
passnet-solve
END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.
passnet-skill
PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under ./pass_dir/, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.
passnet-pattern-fusion
Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()/replacement_args()/replacement_func() files, when a pass "failed to match", or when deciding how to fuse multiple kernels/ops.
passnet-orchestrate
Round/batch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep/revert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.
passnet-feedback
Fast, deterministic feedback for PassNet work: pre-flight pattern/match verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).