Agent skill · Data & Analytics

flow-bio

Flow.bio API bridge — authenticate, browse pipelines/samples/projects, search, upload data, launch pipeline executions, and check run status on any Flow instance.

BioTender-maxgithub.com/BioTender-maxGitHub ↗
claude-codeships scriptsNOASSERTION
Install
npx skills add BioTender-max/awesome-bio-agent-skills --skill flow-bio --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 5
SKILL.md size: 9 KB
Bundled scripts: yes
Version: 0.1.0
Declared author: ClawBio Contributors
Path: skills/clawbio/flow-bio/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 135
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Flow Bio Bridge **ClawBio's gateway to the Flow.bio platform — browse, search, upload, and launch bioinformatics pipelines on Flow from the command line.** ## Why This Exists Flow.bio is a bioinformatics platform hosting curated Nextflow pipelines with managed compute, sample tracking, and collaborative project management. But interacting with Flow requires navigating the web UI or writing custom API scripts. Flow Bio Bridge makes the platform **agent-accessible**: authenticate once, then list pipelines, upload samples, launch executions, and poll for results — all from the CLI or via the ClawBio orchestrator. - **Without it**: Users must switch between web UI and local analysis, manually track execution IDs, and write one-off upload scripts - **With it**: A single CLI covers discovery, upload, execution, and status checking across any Flow instance - **Why ClawBio**: Chain Flow pipeline outputs with local ClawBio skills (e.g. Flow RNA-seq → ClawBio diffviz) ## Core Capabilities 1. **Authentication** — Login via username/password, existing JWT token, or environment variables 2. **Pipeline discovery** — List and inspect available Nextflow pipelines with versions and parameter sche

What's inside
Steps it walks through
  1. Why This Exists
  2. Core Capabilities
  3. Input Formats
  4. Workflow
  5. CLI Reference
  6. Demo
  7. Algorithm / Methodology
  8. Example Queries
  9. Output Structure
  10. Dependencies
  11. Safety
  12. Integration with Bio Orchestrator
  13. Citations
Ships with 4 files
  • data/demo_cache.json
  • flow_bio.py
  • tests/__init__.py
  • tests/test_flow_bio.py
Commands it runs
Login (stores token for subsequent calls)
python skills/flow-bio/flow_bio.py --login --username USER --password PASS
python skills/flow-bio/flow_bio.py --login --token TOKEN
Discovery
python skills/flow-bio/flow_bio.py --pipelines
python skills/flow-bio/flow_bio.py --samples
python skills/flow-bio/flow_bio.py --projects
python skills/flow-bio/flow_bio.py --organisms
python skills/flow-bio/flow_bio.py --sample-types
python skills/flow-bio/flow_bio.py --executions
More from awesome-bio-agent-skills
All skills →
About this skill
What does the flow-bio skill do?

Flow.bio API bridge — authenticate, browse pipelines/samples/projects, search, upload data, launch pipeline executions, and check run status on any Flow instance.

How do I install it?

Run `npx skills add BioTender-max/awesome-bio-agent-skills --skill flow-bio --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From BioTender-max/awesome-bio-agent-skills, a repository with 135 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going