ワンクリックで
annotate-bed
Use when you need to annotate BED/GFF/VCF intervals with coverage depth and breadth from multiple feature files.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when you need to annotate BED/GFF/VCF intervals with coverage depth and breadth from multiple feature files.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Use when joint-genotyping one or more germline gVCFs into a cohort VCF with GATK GenotypeGVCFs.
Use when running GATK HaplotypeCaller to emit per-sample germline variant calls or gVCFs from analysis-ready BAM/CRAM inputs.
Use when splitting mixed accession-like text into one lowercase token per line in EDirect-style text pipelines.
Use when converting ACE assembly files into SAM while preserving legacy ACE-specific padded or contig-sequence behavior.
Use when pretty-printing tab-delimited output with left, center, right, or decimal-aware numeric alignment in EDirect text workflows.
Use when masking columns or coordinate ranges in multiple-sequence alignments before downstream HMMER or alignment-processing steps.
SOC 職業分類に基づく
| name | annotate-bed |
| description | Use when you need to annotate BED/GFF/VCF intervals with coverage depth and breadth from multiple feature files. |
| disable-model-invocation | true |
| user-invocable | true |
annotateBed -i intervals.bed -files file1.bed file2.bed ... [options]/home/vimalinx/miniforge3/envs/bio/bin/annotateBedreferences/help.md-s or -S.# 1) Annotate intervals by fractional coverage from two tracks
annotateBed \
-i peaks.bed \
-files promoters.bed enhancers.bed
# 2) Report counts instead of fraction covered
annotateBed \
-i peaks.bed \
-files promoters.bed enhancers.bed \
-counts
# 3) Emit both counts and coverage with readable column names
annotateBed \
-i peaks.bed \
-files promoters.bed enhancers.bed \
-names promoters enhancers \
-both
default), hit count (-counts), or both (-both).-names so the header is interpretable when many annotation tracks are involved.-i and -files are both required.-names should have one label per annotation file if you want a correct header.-counts and -both change the meaning and number of appended columns, so downstream parsers must know which mode you used.-s and -S are mutually exclusive.-h for help; GNU-style --help / --version calls on these wrappers produce noisy errors.