Agent skill

crispr-screen-triage

Deterministic CRISPR screen hit ranking from local guide-level count tables

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

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

Facts
Files in the skill folder: 4
SKILL.md size: 7 KB
Bundled scripts: yes
Version: 0.1.0
Declared author: ClawBio
Path: skills/clawbio/crispr-screen-triage/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

# CRISPR Screen Triage You are **CRISPR Screen Triage**, a specialised ClawBio agent for ranking gene-level CRISPR screen hits from supplied guide counts and annotations. ## Trigger **Fire this skill when the user says any of:** - "triage CRISPR screen hits" - "rank guide-level CRISPR counts" - "rank depleted CRISPR genes" - "score genes from a knockout screen" - "which CRISPR hits should I follow up" **Do NOT fire when:** - The user asks for variant interpretation. - The user asks for single-cell clustering. - The user asks for clinical actionability. ## Why This Exists - **Without it**: Users sort fold changes manually and ignore follow-up feasibility. - **With it**: Depletion, essentiality, and druggability are combined deterministically. - **Why ClawBio**: The score is transparent, local, and reproducible. ## Core Capabilities 1. **Count validation**: Requires guide ID, gene, control count, treatment count, essentiality, and druggability. 2. **Guide aggregation**: Computes guide-level log2 fold change and aggregates by gene using the median. 3. **Local triage**: Computes a fixed gene triage score from depletion plus user-supplied essentiality and druggability. 4. **Report pack*

What's inside
Steps it walks through
  1. Trigger
  2. Why This Exists
  3. Core Capabilities
  4. Scope
  5. Input Formats
  6. Workflow
  7. CLI Reference
  8. Demo
  9. Algorithm / Methodology
  10. Example Queries
  11. Example Output
  12. Output Structure
  13. Dependencies
  14. Gotchas
Ships with 3 files
  • crispr_screen_triage.py
  • demo_screen_counts.csv
  • tests/test_crispr_screen_triage.py
Commands it runs
python skills/crispr-screen-triage/crispr_screen_triage.py --input counts.csv --output /tmp/crispr
python skills/crispr-screen-triage/crispr_screen_triage.py --demo --output /tmp/crispr
python clawbio.py run crispr-triage --demo
More from awesome-bio-agent-skills
All skills →
report-templatePublication-quality PDF report generation using Typst templates. Produces professional scientific…Code Review & Qualitysec-reportSEC (size-exclusion chromatography) analysis with peak detection, oligomer classification, and…Code Review & Qualitybio-atac-seq-consensus-peaksetBuild a differential-ready consensus peakset from per-replicate ATAC-seq peaks using iterative…Otherbio-toolsBiology research tools reference. Always available inside agent containers.AI & Agentsbio-remote-homologyDetect distant homologs using profile and structure-aware methods that go beyond standard BLAST.…Otherbio-variant-callingCall SNPs and indels from aligned reads using bcftools mpileup and call. Use when detecting…Other
About this skill
What does the crispr-screen-triage skill do?

Deterministic CRISPR screen hit ranking from local guide-level count tables

How do I install it?

Run `npx skills add BioTender-max/awesome-bio-agent-skills --skill crispr-screen-triage --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
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.