shield_lock
JinDaGe
← Back to skills
extension
Category: Productivity & OfficeNo API key required

bakta-genome-annotation

Index entry for an upstream research Skill intended for research work involving bakta genome annotation. Maintained upstream by jaechang-hits; source files are not included in this package.

personAuthor: OpenScientificSkillshubOpenAPI
open_in_newRepositorydownloadDownload package

bakta-genome-annotation — upstream index

This is an index-only record created by OpenScientificSkills. It contains an attributed catalog summary, but does not bundle, mirror, or redistribute the upstream Skill instructions, code, or assets.

What this Skill is for

This indexed Skill is intended for research work involving bakta genome annotation. It helps researchers discover the upstream project that may provide instructions, templates, scripts, or workflow guidance for that task. Exact capabilities, requirements, and behavior must be confirmed in the canonical repository because they can change upstream.

Attributed upstream catalog summary:

Annotate bacterial and archaeal genomes and plasmids with Bakta's Prodigal/HMM/diamond pipeline. Identifies CDS, ncRNA, tRNA, rRNA, tmRNA, sORFs, CRISPR arrays, oriC/oriV/oriT, and gaps against a curated UniRef-derived database. Produces NCBI-compatible GFF3, GenBank, EMBL, JSON, FASTA, TSV, and a circular genome plot. Use Prokka for legacy pipelines or non-bacterial kingdoms; PGAP for NCBI GenBank submission.

Canonical source

  • Upstream author or maintainer: jaechang-hits
  • Repository: https://github.com/jaechang-hits/SciAgent-Skills
  • Upstream Skill path: skills/genomics-bioinformatics/annotation/bakta-genome-annotation/SKILL.md
  • Upstream license status: not verified

The CC0-1.0 value on this ModelScope entry applies only to the newly written index structure and explanatory text. It does not apply to the attributed upstream summary and does not grant any license to the upstream repository.

Before use

Open the canonical repository, review its current license, security posture, dependencies, and instructions, and obtain any permission required by the upstream author. Always treat the upstream repository as the source of truth.