CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

facs-gating-viz-style

Use facs gating viz style for data analysis workflows that need structured execution, explicit assumptions, and clear output boundaries.

Quality

51%

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/facs-gating-viz-style/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 body contains a genuinely usable core (parameters, commands, validation check, error handling) but is buried under template boilerplate and duplicated sections with broken cross-references. Trimming to the skill-specific content would substantially improve it.

Suggestions

Remove the duplicated stub sections ('See ## X above') and consolidate the two Usage/Features/Prerequisites occurrences into single sections.

Delete the generic Security Checklist, Risk Assessment, Lifecycle, and Evaluation Criteria template filler, or reduce them to the few lines that are specific to this plotting skill.

Replace the non-portable 'cd "20260318/scientific-skills/..."' path with a path relative to the skill bundle, and drop the 'in-file CONFIG block' instruction since the script uses CLI arguments instead.

DimensionReasoningScore

Conciseness

The ~190-line body is heavily padded: the description is repeated verbatim in 'When to Use', stub sections say 'See `## Features` above for related details', the same sections (Usage, Features, Prerequisites) appear twice, and generic Risk Assessment / Security Checklist / Lifecycle / Evaluation templates add little skill-specific value.

2 / 5

Actionability

Concrete executable commands are provided (py_compile check, --help, full usage example, parameters table with defaults), but the hardcoded 'cd "20260318/scientific-skills/..."' path is non-portable and 'Edit the in-file CONFIG block' does not match the actual script.

4 / 5

Workflow Clarity

A numbered 5-step workflow plus a 4-step run plan with an explicit pre-execution validation checkpoint (py_compile) and a documented error-handling fallback; not 5 because several steps remain abstract and there is no validate-fix-retry loop.

4 / 5

Progressive Disclosure

The bundle reference (scripts/main.py) is real and one level deep, but in-file navigation is broken and duplicative — 'Key Features' points to '## Features above' when that section appears below, and duplicated section content that should be consolidated or split is inlined.

3 / 5

Total

13

/

20

Passed

Description

25%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 generic template text that fails to convey the skill's actual purpose (beautifying flow cytometry gating plots for publication). It would rarely trigger correctly and conflicts with any data-analysis skill.

Suggestions

State concrete capabilities in third person, e.g. 'Beautifies flow cytometry gating plots with contour, density, and dot styles for publication-ready figures.'

Add natural trigger phrases: 'Use when working with FACS data, flow cytometry gating plots, FCS files, or preparing publication figures.'

Remove the abstract buzzwords ('structured execution, explicit assumptions, clear output boundaries') that apply to any data-analysis workflow and cause overlap with other skills.

DimensionReasoningScore

Specificity

The description names the domain only via the skill name ('facs gating viz style') and offers no concrete actions — phrases like 'structured execution, explicit assumptions, and clear output boundaries' are pure abstraction with no mention of plots, gating figures, or output types.

2 / 5

Completeness

The 'what' is circular (restates the skill name instead of a capability) and the 'when' ('data analysis workflows that need structured execution') is vague, so neither what nor when is concretely answered.

2 / 5

Trigger Term Quality

Natural user phrasing such as 'flow cytometry', 'FACS', 'gating plot', 'FCS file', or 'publication figure' is entirely absent; the only trigger language is the generic 'data analysis workflows'.

2 / 5

Distinctiveness Conflict Risk

The operative trigger language ('data analysis workflows that need structured execution, explicit assumptions, and clear output boundaries') would match nearly any structured data-analysis skill, giving high overlap risk; only the embedded skill name distinguishes it.

2 / 5

Total

8

/

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/facs-gating-viz-style/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.