Sub-skill of nextflow-pipelines: 5a. Check genome availability (+2).
Scanned 9/9/2026
Install to Claude Code
npx -y skills add vamseeachanta/workspace-hub --skill 5a-check-genome-availability --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of 5a Check Genome Availability?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vamseeachanta-5a-check-genome-availability-workspace-hub)More formats (shields.io, HTML) on the badges page.
---
name: nextflow-pipelines-5a-check-genome-availability
description: 'Sub-skill of nextflow-pipelines: 5a. Check genome availability (+2).'
version: 1.0.0
category: science
type: reference
scripts_exempt: true
---
# 5a. Check genome availability (+2)
## 5a. Check genome availability
```bash
python scripts/manage_genomes.py check <genome>
# If not installed:
python scripts/manage_genomes.py download <genome>
```
Common genomes: GRCh38 (human), GRCh37 (legacy), GRCm39 (mouse), R64-1-1 (yeast), BDGP6 (fly)
## 5b. Decision points
**DECISION POINT: Confirm with user:**
1. **Genome:** Which reference to use
2. **Pipeline-specific options:**
- **rnaseq:** aligner (star_salmon recommended, hisat2 for low memory)
- **sarek:** tools (haplotypecaller for germline, mutect2 for somatic)
- **atacseq:** read_length (50, 75, 100, or 150)
## 5c. Run pipeline
```bash
nextflow run nf-core/<pipeline> \
-r <version> \
-profile docker \
--input samplesheet.csv \
--outdir results \
--genome <genome> \
-resume
```
*See sub-skills for full details.*
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
Wire a service's OpenTelemetry output to Sematext Cloud. Walks through region, App-type, instrumentation flow (managed OTLP endpoint vs Sematext Agent), and signal selection (traces/metrics/logs), then produces the exact env-var block and points at a runnable reference example in this repo. Invoke when instrumenting a new app for Sematext.
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.