flow-cytometry-gating-strategist
Recommend optimal flow cytometry gating strategies for specific cell types and fluorophores
61
41%
Does it follow best practices?
Impact
99%
1.83xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./scientific-skills/Data analysis/flow-cytometry-gating-strategist/SKILL.mdQuality
Discovery
54%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 identifies a clear, specialized scientific domain with good trigger terms that researchers would naturally use. However, it only describes a single capability and critically lacks any 'Use when...' guidance, making it incomplete for skill selection purposes. The technical specificity prevents conflicts but the missing trigger clause significantly weakens its utility.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about FACS analysis, cell sorting panels, gating hierarchies, or fluorophore selection'
Expand the capability list to include related actions such as 'design compensation matrices, optimize panel configurations, troubleshoot spectral overlap'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (flow cytometry) and a specific action (recommend gating strategies), but only describes one capability. Could list additional concrete actions like 'design compensation matrices' or 'troubleshoot spillover'. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Contains strong natural keywords users would say: 'flow cytometry', 'gating strategies', 'cell types', 'fluorophores'. These are the exact terms researchers use when seeking this type of help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specialized niche - flow cytometry gating is a very specific scientific technique. Unlikely to conflict with other skills due to the technical specificity of the domain. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is heavily padded with boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Prerequisites) that provide no actionable value and consume significant tokens. While it documents a CLI tool interface well, it fails to provide the actual domain expertise needed - how to recommend gating strategies based on cell types and fluorophores. The content reads more like auto-generated documentation than a skill teaching Claude specialized knowledge.
Suggestions
Remove all boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Prerequisites) - these waste tokens and Claude doesn't need them
Add actual domain knowledge: decision rules for matching fluorophores to cell types, compensation considerations, and when to use each gating strategy type
Move reference tables (fluorophores, cell types) to separate files and link to them, keeping only essential quick-reference info inline
Replace the tool documentation approach with actionable guidance Claude can use directly to make recommendations, rather than describing what a hypothetical script outputs
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) that add no value for Claude. The skill explains basic concepts and includes unnecessary metadata that bloats the content significantly. | 1 / 3 |
Actionability | Provides concrete CLI examples and output JSON format, but the actual gating strategy logic is not executable - it describes what the tool outputs rather than providing actionable guidance Claude can use to recommend strategies. The core domain knowledge (how to actually recommend gating strategies) is missing. | 2 / 3 |
Workflow Clarity | Lists gating strategy types and steps but lacks validation checkpoints or feedback loops. The workflow for using the tool is clear, but there's no guidance on verifying recommendations or handling edge cases in the actual gating analysis process. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline including reference tables, boilerplate sections, and detailed parameter lists that could be separated. No clear hierarchy between essential and supplementary information. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- aipoch/medical-research-skills
- Commit
ca9aaa4
- 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.