CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

scrna-embedding

Local scVI/scANVI-based single-cell latent embedding and batch-aware integration from raw-count .h5ad or 10x Matrix Market input, with stable integrated AnnData export for downstream latent analysis.

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 ./skills/scrna-embedding/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 is highly actionable with concrete, executable CLI commands and a clear validated workflow sequence, and it appropriately avoids explaining concepts Claude already knows. Its weaknesses are redundancy across three overlapping capability/workflow/methodology sections and a monolithic single-file structure with no progressive disclosure of detailed material into reference files.

Suggestions

Consolidate "Core Capabilities", "Workflow", and "Algorithm / Methodology" into a single sequenced section to eliminate the triple restatement of training, export, and diagnostics content (and fix the duplicated item 5 in Core Capabilities).

Move the Algorithm/Methodology details and per-parameter QC specifics into a reference file (e.g. references/methodology.md) linked one level deep from SKILL.md.

Add a short error-recovery step after input validation (e.g. what message to surface and what to suggest when a processed-like matrix is rejected) to close the workflow feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly efficient with well-chosen tables and commands, but the same material (training, latent export, batch diagnostics) is restated across "Core Capabilities", "Workflow", and "Algorithm / Methodology", and "Core Capabilities" contains a duplicated list number (two items numbered 5). It could be meaningfully tightened without losing information, matching the 3 anchor rather than the 4 anchor's "minor instances".

3 / 5

Actionability

The CLI Reference provides fully executable, copy-paste-ready commands covering the common cases (standard, batch-key, scANVI with labels, 10x directory, demo, runner invocation), and the Output Structure and Demo sections give concrete expected artifacts. This matches the 5 anchor's coverage of common cases with complete commands.

5 / 5

Workflow Clarity

The Workflow section gives a clear Validate → Filter → Train → Project → Generate sequence with an explicit validation checkpoint ("reject processed-like matrices") at the start. It falls short of 5 because there is no error-recovery feedback loop describing what to do when validation fails or training inputs are malformed.

4 / 5

Progressive Disclosure

The single SKILL.md is well-sectioned but monolithic: no bundle files exist (references/, scripts/, assets/ are absent), and sizable content such as the Algorithm/Methodology details and CLI reference is inlined where a one-level-deep reference file would be appropriate. This matches the 3 anchor of content that should be separate being inline, rather than the 4 anchor's "most content appropriately placed".

3 / 5

Total

15

/

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 and technically precise, with strong tool and format keywords that make it highly distinguishable from generic single-cell skills. Its main weakness is the absence of any explicit "when to use this" trigger guidance, which caps completeness, and a few missing natural trigger phrases like "batch correction".

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks for scVI/scANVI embedding, latent space analysis, or batch correction/integration of single-cell data."

Include the natural phrase "batch correction" (the body's own trigger keywords list it) so the description matches how users actually phrase the request.

Consider mentioning the batch-mixing diagnostics output so the description's capability coverage matches the skill's actual feature set.

DimensionReasoningScore

Specificity

The description names concrete tools ("scVI/scANVI-based"), input formats ("raw-count .h5ad or 10x Matrix Market"), and several specific actions ("latent embedding", "batch-aware integration", "integrated AnnData export"). It falls just short of the 5 anchor because capabilities like batch-mixing diagnostics and reproducibility outputs are not mentioned.

4 / 5

Completeness

The "what" is clearly and concretely answered (scVI/scANVI latent embedding and integration from raw-count inputs with integrated export), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good keyword coverage including natural terms and file formats users would say: "scVI", "scANVI", "latent embedding", "h5ad", "10x". A few common natural phrases are missing, notably "batch correction" and "latent space" as literal user phrasings.

4 / 5

Distinctiveness Conflict Risk

The scVI/scANVI model-based framing carves a clear niche distinct from generic single-cell preprocessing skills and includes format-specific triggers (.h5ad, 10x). Minor overlap risk remains with a generic scrna-orchestrator skill covering single-cell analysis, so it does not reach the 5 anchor's minimal conflict risk.

4 / 5

Total

15

/

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

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository

ClawBio/ClawBio

Path

skills/scrna-embedding/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.