CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

crispr-screen-analyzer

Process CRISPR screening data to identify essential genes and hit candidates. Performs quality control, statistical analysis (RRA), and hit calling for pooled CRISPR screens including viability screens and drug resistance/sensitivity studies.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Data Analysis/crispr-screen-analyzer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

45%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill's core analysis guidance is genuinely actionable, with code examples that match the packaged script's API and CLI exactly, and the complete workflow includes real validation checkpoints. However, the body is massively over-inflated with template boilerplate, triplicated troubleshooting, and textbook CRISPR biology, while an existing reference file goes unmentioned — the monolithic structure wastes context and buries the useful content.

Suggestions

Cut the template boilerplate sections ("When to Use", "Key Features", "Dependencies", "Example Usage", "Implementation Details", "Output Requirements", "Input Validation", "Response Template", etc.) that restate the description or generic process rules, keeping the body to the API examples, parameter table, and complete workflow.

Move the "Common Patterns", "Common Pitfalls", "Troubleshooting", and "Quality Checklist" sections into one-level-deep files under references/ and link them clearly, replacing the false "(No reference files currently available for this skill)" claim with a link to the existing references/runtime_checklist.md.

Fix the broken executable guidance: remove the bogus "cd 20260318/scientific-skills/..." path, and correct the "Step 1: Run QC" CLI example so it reflects what scripts/main.py actually outputs when run without --control/--treatment.

DimensionReasoningScore

Conciseness

The ~1,180-line body is severely verbose and heavily padded: template boilerplate ("When to Use", "Key Features", "Implementation Details", "Workflow") restates the description verbatim multiple times; troubleshooting content is triplicated ("Common Issues and Solutions" in four capability sections, plus a global "Troubleshooting" and "Common Pitfalls" section); and it extensively explains CRISPR screen biology Claude already knows (MOI, T0/T14 design, synthetic lethality, DepMap). This matches anchor 1; it exceeds anchor 2's "several unnecessary explanations" because the padding is pervasive throughout, not limited to a few sections.

1 / 5

Actionability

The Python examples call the real API in scripts/main.py exactly (qc_metrics(), calculate_lfc(control, treatment), rra_analysis(lfc, fdr_threshold), identify_hits(results, fdr_threshold, lfc_threshold)) and the CLI examples match the script's argparse flags, so guidance is mostly executable and copy-paste ready. Not 5 due to minor gaps: the bogus "cd 20260318/scientific-skills/..." path, and the "Step 1: Run QC" command claims a qc_results output the script never writes when run without --control/--treatment.

4 / 5

Workflow Clarity

The "Complete Workflow Example" provides a concrete QC → LFC → RRA → hit-calling sequence with a real validation checkpoint (qc_pass = all(gini < 0.4 ...) with a warning) plus a pre-run py_compile check and phase-by-phase Quality Checklists, matching anchor 4. Not 5 because the QC gate only warns and proceeds rather than stopping (no validate → fix → re-validate feedback loop), and the generic "Workflow" section is filler rather than a domain sequence.

4 / 5

Progressive Disclosure

Hundreds of lines of patterns, pitfalls, checklists, and troubleshooting that clearly belong in separate reference files are inlined into a monolithic SKILL.md, matching anchor 2. Not 3 because the one existing reference (references/runtime_checklist.md) is not merely poorly signaled but actively denied ("(No reference files currently available for this skill)") and never linked, leaving no functioning reference navigation at all.

2 / 5

Total

11

/

20

Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, in third person, and rich in natural domain trigger terms, with a well-defined niche in pooled CRISPR screen analysis. Its main weakness is the absence of any explicit "Use when..." trigger clause, which caps completeness and limits when-guidance to weak implication via scope phrasing.

Suggestions

Append an explicit trigger clause, e.g. "Use when analyzing pooled CRISPR screen count matrices, sgRNA dropout screens, or when the user mentions CRISPR screens, essential genes, or drug resistance/sensitivity hits."

Mention the log fold change calculation and gene-level aggregation steps so the "what" covers the script's full capability set.

Add common user synonyms such as "sgRNA" and "dropout screen" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

"Performs quality control, statistical analysis (RRA), and hit calling" plus "identify essential genes and hit candidates" lists several specific concrete actions with a named method, matching anchor 4. Not 5 because capabilities documented in the body (log fold change calculation, gene-level aggregation, multi-replicate support) are unmentioned, leaving minor coverage gaps.

4 / 5

Completeness

The "what" is clear ("Process CRISPR screening data to identify essential genes and hit candidates..."), but there is no "Use when..." clause or equivalent explicit trigger guidance; "for pooled CRISPR screens including viability screens..." is scope description, only weakly implying when. Per the rubric guideline this caps completeness at 3; it does not reach anchor 4 because no explicit when-clause exists at all.

3 / 5

Trigger Term Quality

Good coverage of natural phrases users would say: "CRISPR screening", "essential genes", "hit calling", "pooled CRISPR screens", "viability screens", "drug resistance/sensitivity". Not 5 because common variations such as "sgRNA", "dropout screen", and tool names like "MAGeCK" are absent.

4 / 5

Distinctiveness Conflict Risk

The core niche (statistical analysis and hit calling on pooled screen count data) is clearly distinct from related skills like crispr-grna-designer or fastqc-report-interpreter, matching anchor 4 ("mostly distinct; minor overlap risk with closely related skills"). Not 5 because the "quality control" mention creates some overlap with sequencing-QC skills like alignment-quality-checker.

4 / 5

Total

15

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1188 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Data Analysis/crispr-screen-analyzer/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.