BotCurrent↗
← Back to examples

Community recipe · Tool workflows

Triage experimental screen hits from supplied guide counts

Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.

The problem

Experimental guide-count results need transparent aggregation and annotation before a researcher can prioritize follow-up work.

Agent job

Validate the supplied count table, aggregate gene depletion and combine annotations into a ranked report.

Expected output

A traceable experimental-hit triage report.

Where this framing comes from
  • Core problem: Editorial purpose framing
  • Agent job: Editorial purpose framing
  • Expected output: Editorial purpose framing
  • Relevant job roles: Editorial purpose framing
  • Benefit type: Editorial purpose framing
Editorial framing and outcome limits

Describes the task’s purpose and intended output; measured benefit, safe unsupervised operation and successful delivery are not established by this framing.

Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.

Case-specific decision guidance · untested

Case-specific decision guidance and first checks are original proposals. The linked source supports the attributed task; this added guidance has not been executed.

Read the attributed source evidence and original caveats below ↓

Why use this

  1. A researcher reviewing an experimental screen may need to aggregate guide-level observations without losing sample labels, annotation provenance or the distinction between exploratory ranking and biological confirmation. A polished ranking can hide input mismatches or incomplete annotations.

  2. This job could prepare a transparent triage-analysis specification and evidence checklist. Keeping aggregation choices and missing data visible helps qualified researchers decide which later results deserve follow-up, without expanding into experimental design or clinical interpretation.

Why an agent / simpler alternative

Useful judgment

Reconcile supplied count/annotation manifests, identify aggregation ambiguities and organize traceability for expert review.

Simpler alternative

Use an established analysis pipeline when the assay and data structure match its documented assumptions.

Unsuitable when

The workflow would design guides, fetch unapproved annotations or claim therapeutic/clinical actionability.

Proposed inputs

  1. Name

    Guide-count manifest

    Owner

    Authorized researcher

    Minimum scope

    Supplied identifiers, sample labels and count provenance

    Quality check

    Check duplicate guides, missing values and group alignment

  2. Name

    Approved analysis/annotations

    Owner

    Domain lead

    Minimum scope

    Provided gene mappings, metadata and aggregation choices

    Quality check

    Record annotation versions and unresolved mappings

Access and setup — proposed or unknown

Proposed minimum
  1. Review synthetic placeholder counts and metadata schemas; no analysis execution, biological design or external annotation retrieval.

Compatibility unknowns
  1. Current data support, aggregation implementation, scientific adequacy and runtime compatibility are unknown.

External actions requiring approval
  1. Sensitive-data access, computation, output overwrites and sharing research results requires approved scope.

Expected deliverable and review checks

Proposed artifact

Triage-plan candidate with input exceptions, aggregation traceability and expert-review requirements for any future ranking.

Critical checks
  1. Preserve guide-to-gene mappings; distinguish missing counts from zero; retain annotations by provenance; do not equate rank with validated effect.

Missing output evidence

This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.

Failure signals and proposed responses

  1. Signal

    One guide maps ambiguously to a gene

    Why it matters

    Aggregation may attribute evidence incorrectly

    Proposed response

    Hold the mapping for researcher resolution.

  2. Signal

    Sample labels are reversed

    Why it matters

    The intended comparison changes meaning

    Proposed response

    Verify labels against the supplied design before any calculation.

Effort and cost — unknown

Setup work
  1. Define input contracts and permitted analysis boundaries.

Ongoing review
  1. Researchers review actual analysis evidence and decide on follow-up independently.

Unknowns
  1. Assay quality, mapping validity, statistical suitability and analysis costs are unknown.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Invent placeholder guides G-A/G-B with an ambiguous mapping and swapped sample labels; prepare a preflight report only.

Acceptance checks
  1. Flag both issues; rank no real targets; design no experiment and claim no biological validation.

Stop conditions
  1. Stop if provenance, mapping or scientific authority is unresolved.

Limits

  1. A triage plan cannot establish experimental hits, biological mechanisms or clinical relevance.

Tasks: Research & discovery

Useful for: Researcher

Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.
OpenClawIndependent testing: No

Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.

Original source

https://github.com/ClawBio/ClawBio/blob/main/skills/crispr-screen-triage/SKILL.md ↗

Attributed to: Mrinal Joshi / ClawBio

Community recipe
Original action type
tool_action
What the source supports
The recipe validates a guide-count table, aggregates depletion by gene and combines supplied annotations into a ranked research triage report with traceable outputs.
Source outcome limits
This community recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Evidence attribution caveat
This community recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Source approval description
Not specified. The scope excludes guide design, annotation fetching and clinical actionability.
Named tools
OpenClaw; ClawBio; Python standard library
Model or version
Unknown
Publication date
Unknown
Source last checked
2026-10-14
Demonstrated in Canada
Unknown
Canadian availability
Unknown
Proposed Canadian adaptation
Proposed: begin with public or institution-approved research data in a Canadian-controlled workspace; obtain the institution’s privacy and research-governance review before using identifiable samples. No Canadian deployment was demonstrated.
Recommended approval boundaries
A domain expert should approve inputs, parameters and compute budget, inspect outputs, and authorize any sharing or scientific publication; do not use as an autonomous clinical decision system.