CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

flowio

Parse Flow Cytometry Standard (FCS) files v2.0–3.1 and extract events/metadata for preprocessing workflows (e.g., when you need NumPy arrays, channel info, or CSV/DataFrame export from cytometry files).

Quality

74%

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/flowio/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 content's greatest strength is actionability: a complete, executable end-to-end example with robust error handling. Weaknesses are redundancy across the 'Key Features', 'When to Use', and 'Implementation Details' sections, no output validation after batch write operations, and a bundled api_reference.md that is never referenced from the body.

Suggestions

Add a clearly signaled link to the bundled reference, e.g. an '## API reference' section with 'See [api_reference.md](references/api_reference.md) for all methods and constructor options', and move overlapping API detail out of the body.

Add a validation checkpoint after writing files, e.g. re-open 'filtered.fcs' with FlowData and verify event_count matches the filtered array before proceeding.

Remove the 'Key Features' section (or fold it into 'When to Use') to eliminate the redundancy with 'Implementation Details' and trim token cost.

DimensionReasoningScore

Conciseness

The body is mostly efficient (library-specific details like PnG/PnE transforms and offset flags earn their place), but the 'Key Features' bullet list substantially duplicates 'When to Use' and 'Implementation Details', and the example carries decorative print statements. This fits the 3-anchor ('mostly efficient but includes some unnecessary explanation or could be tightened') better than 4, where over-explanation would be only minor.

3 / 5

Actionability

The example is fully executable and copy-paste ready: complete imports, a 'read_fcs_safely' helper with fallback flags for offset and parsing errors, DataFrame/CSV export, percentile-based filtering with 'create_fcs', and a metadata-only read. It covers the common cases (multi-dataset, malformed files, writing) with real code, matching the 5-anchor.

5 / 5

Workflow Clarity

A clear parse -> convert -> filter -> write sequence exists with error-recovery excepts for 'MultipleDataSetsError' and offset errors, but writing FCS/CSV outputs is a batch operation with no validation or verification of the written result, which the rubric caps at 3. It exceeds the 2-anchor because the sequence and error-handling feedback paths are concrete and explicit.

3 / 5

Progressive Disclosure

The bundle provides 'references/api_reference.md' (371 lines of API documentation), but the SKILL.md body never mentions or links it, and 'Implementation Details' inlines API-level content that overlaps with that reference. This matches the 3-anchor ('references present but not clearly signaled; content that should be separate is inline'); not 2 because section structure is good and nothing is deeply nested.

3 / 5

Total

14

/

20

Passed

Description

73%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 strong, specific description for a narrow domain: concrete actions, explicit (if parenthetical) trigger guidance, and negligible conflict risk. The main deductions are the second-person 'when you need' phrasing (which the rubric penalizes) and missing natural terms like the '.fcs' extension and the write-capability triggers.

Suggestions

Rewrite the trigger clause in third person, e.g. 'Use when the user needs NumPy arrays, channel info, or CSV/DataFrame export from cytometry files' to avoid the second-person voice penalty.

Add missing natural trigger terms such as '.fcs' and 'flow cytometry data', and mention FCS writing/multi-dataset handling so the 'what' covers the skill's full capability set.

DimensionReasoningScore

Specificity

The description names the domain and several concrete actions ('Parse Flow Cytometry Standard (FCS) files v2.0-3.1 and extract events/metadata', 'NumPy arrays, channel info, or CSV/DataFrame export'), which fits the 4-anchor, but the second-person clause 'when you need NumPy arrays...' incurs the rubric's explicit third-person-voice penalty of -1. It also omits capabilities the body documents (writing FCS files, multi-dataset handling), so it is not comprehensive.

3 / 5

Completeness

Both what ('Parse... FCS files v2.0-3.1 and extract events/metadata') and when ('when you need NumPy arrays, channel info, or CSV/DataFrame export from cytometry files') are explicitly present with concrete trigger phrases, but the when-clause is hedged as a parenthetical '(e.g., ...)' rather than a standalone 'Use when...' trigger. It sits between the 4-anchor ('when' could be more explicit) and the 5-anchor (fully explicit trigger phrasing), closer to 4.

4 / 5

Trigger Term Quality

Natural terms users would say are present ('FCS files', 'cytometry files', 'NumPy arrays', 'CSV/DataFrame export'), giving good keyword coverage, but common variations like the '.fcs' file extension and 'flow cytometry data' are missing. Not the 5-anchor because synonym/extension coverage is incomplete; not 3 because several genuinely natural trigger phrases appear.

4 / 5

Distinctiveness Conflict Risk

Flow cytometry FCS parsing is a clear niche with distinct triggers ('FCS files', 'cytometry files'); no other plausible skill overlaps with these terms, matching the 5-anchor for minimal conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Data Analysis/flowio/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.