CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

flow-cytometry-analysis

Complete flow cytometry analysis pipeline. FCS file handling, compensation, manual/automated gating, immunophenotyping, CFSE proliferation analysis, cell cycle analysis (Dean-Jett-Fox), and apoptosis assays. Extends flowio with analytical workflows. For raw FCS parsing only use flowio.

Quality

75%

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 ./backend/cli/skills/biology/flow-cytometry-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

A dense, highly actionable reference: complete executable implementations for all eight capabilities, three end-to-end workflows, and useful troubleshooting/best-practices sections with a clear gating sequence. Its major structural flaw is that it never mentions the four bundled CLI scripts that duplicate and extend the inlined code, leaving the skill's most detailed materials undiscoverable and the body a monolith of inlined implementations.

Suggestions

Reference the bundled scripts from the body, e.g. a 'CLI Tools' section: gate_fcs.py for batch gating, immunophenotype.py for panel analysis, cfse_proliferation.py and cell_cycle.py for those assays, with their usage examples.

Move the full function implementations out of SKILL.md into the scripts (or a references/ file) and keep a concise Quick Start plus per-capability entry points, so the body becomes an overview with one-level-deep references.

Fix minor executability gaps: use `matplotlib.colors.LogNorm()`, pass channel indices/variables explicitly in the apoptosis example instead of hardcoded values, and make each workflow self-contained or clearly note its prerequisites.

DimensionReasoningScore

Conciseness

The body is dense with executable code and light on prose padding, assuming Claude's competence (no explanations of what flow cytometry or the libraries are). Minor over-explanation remains: the Overview paragraph restates the frontmatter description nearly verbatim, and the 'When to Use' bullet list partially duplicates it. Matches 'efficient; minor instances that could be trimmed'.

4 / 5

Actionability

Concrete, executable functions cover every capability (compensation parsing/application, rect/polygon/GMM gating, immunophenotyping, CFSE, Dean-Jett-Fox fitting, Annexin V quadrants, plotting) plus three end-to-end workflows and an install command. Minor gaps keep it below fully copy-paste ready: snippets rely on variables defined in earlier sections (e.g. `singlet_gate`, `channel_names`), the apoptosis example hardcodes `annexin_idx=3`, and `plt.matplotlib.colors.LogNorm()` is a nonstandard path (should be `matplotlib.colors.LogNorm`).

4 / 5

Workflow Clarity

Multi-step processes are clearly sequenced: Best Practices prescribes 'debris exclusion first, then singlets, then viability, then markers', the gating code prints event counts after each step (feedback), and Troubleshooting gives concrete recovery fixes for failure modes; the cell-cycle fit even has a try/except error return. Minor validation gaps: the three Workflow examples lack explicit verification checkpoints (e.g. checking event counts or peak quality before proceeding), though Best Practices covers quality checks. Analysis is read-only, so the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

The bundle contains four substantial standalone CLI tools in scripts/ (gate_fcs.py, immunophenotype.py, cfse_proliferation.py, cell_cycle.py; ~68 KB, 28 functions) that duplicate and extend the inlined code, yet SKILL.md never references them anywhere — zero referenced paths against a populated bundle. The body inlines ~500 lines of implementations that clearly belong in (and already exist as) separate files, matching the level-2 anchor 'content that clearly belongs in separate files is inlined'. Not level 3 because references aren't merely unclear — they are entirely absent and the duplication is total; not level 1 because the body itself is well-sectioned and internally navigable.

2 / 5

Total

14

/

20

Passed

Description

75%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.

A specific, comprehensive, third-person description of what the skill does, with strong domain keywords and an explicit boundary against the raw-parsing skill (flowio). Its one structural weakness is the absence of any 'Use when...' trigger clause, which leaves routing guidance implicit.

Suggestions

Add an explicit trigger clause, e.g. "Use when analyzing flow cytometry data, building gating strategies, quantifying proliferation, or interpreting immunophenotyping panels."

Include additional natural synonyms users would say: ".fcs" files, "Annexin V/PI", "FACS", and "fluorescence channels".

Keep the flowio boundary sentence, but pair it with the positive trigger so the description says both when to use this skill and when not to.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions with comprehensive coverage: "FCS file handling, compensation, manual/automated gating, immunophenotyping, CFSE proliferation analysis, cell cycle analysis (Dean-Jett-Fox), and apoptosis assays." Even names the specific algorithm (Dean-Jett-Fox), so it exceeds the 'minor gaps in coverage' level 4 anchor.

5 / 5

Completeness

The 'what' is clearly and comprehensively stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance; the closest phrase, "For raw FCS parsing only use flowio", routes to a different skill rather than stating when to use this one. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good keyword coverage of natural terms ("flow cytometry", "FCS", "gating", "immunophenotyping", "CFSE", "cell cycle", "apoptosis") but a few natural terms and synonyms are missing (".fcs" file extension, "Annexin V/PI", "FACS", "fluorescence"). Matches the 'good coverage, a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche (flow cytometry analytical pipelines) with an explicit boundary against the sibling skill: "Extends flowio with analytical workflows. For raw FCS parsing only use flowio." Minimal conflict risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository

synthetic-sciences/openscience

Path

backend/cli/skills/biology/flow-cytometry-analysis/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.