Workflow for ribosome profiling, P-site aware preprocessing, periodicity checks, ORF detection, and translation efficiency analysis.
npx skills add https://github.com/BioTender-max/awesome-bio-agent-skills --skill ribo-seq
Reference examples assume recent stable releases of the preferred tools, especially ribo-seq and the other tools listed below.
Before using code or command patterns, verify installed versions match the environment:
python -c "import <module>; print(<module>.__version__)"<tool> --versionWorkflow for ribosome profiling, P-site aware preprocessing, periodicity checks, ORF detection, and translation efficiency analysis.
references/technical_reference.md when you need deeper tool-selection rules, environment adaptation notes, or extra validation guidance.SKILL.md as the main execution path and load the reference file only when the task or failure mode needs the extra detail.Preferred starting point: ribo-seq
Inputs: ribo-seq reads, optional matched RNA-seq, transcript annotation
Outputs: periodicity metrics, ORF candidates, translation efficiency summaries
Establish read-length distributions and P-site offsets before counting footprints.
Confirm expected triplet periodicity and frame enrichment.
Compute footprint abundance at transcript or ORF level and compare with matched RNA when available.
Report canonical or novel ORFs with explicit evidence criteria.
Save periodicity plots, TE tables, and prioritized translated features.
results/ for final tables and serialized objectsfigures/ for plots and static visual exportsqc/ for checks that justify downstream interpretationperiodicity metricsORF candidatestranslation efficiency summariesBulk RNA ExpressionRNA QuantificationDifferential ExpressionAlternative SplicingGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Use when implementing any feature or bugfix, before writing implementation code
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Take biotender-max/ribo-seq from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.