CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lamindb

This skill should be used when working with LaminDB, an open-source data framework for biology that makes data queryable, traceable, reproducible, and FAIR. Use when managing biological datasets (scRNA-seq, spatial, flow cytometry, etc.), tracking computational workflows, curating and validating data with biological ontologies, building data lakehouses, or ensuring data lineage and reproducibility in biological research. Covers data management, annotation, ontologies (genes, cell types, diseases, tissues), schema validation, integrations with workflow managers (Nextflow, Snakemake) and MLOps platforms (W&B, MLflow), and deployment strategies.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/lamindb/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.

A well-structured overview for a large framework skill: excellent progressive disclosure with six real, one-level-deep reference files, and mostly actionable code examples. The main weaknesses are notable redundancy (references listed three times, Overview/When-to-Use duplicating the description, an unrelated promotional section) and workflow examples that lack validation checkpoints in batch operations.

Suggestions

Consolidate the three separate reference listings (per-section Reference: lines, Getting Started Checklist, and the Reference Files section) into a single navigation section to cut ~60-80 redundant lines.

Add an explicit validation checkpoint and error-recovery step to the batch registration loop in Use Case 2 (e.g. curator.validate() before save_artifact, with a fix-and-retry path), matching the validation already shown in Use Case 1.

Define or stub the free variables in the code examples (schema in Use Case 1, data_files/tissues/conditions in Use Case 2, train_model in Use Case 3) so the snippets are copy-paste runnable, and remove the unrelated K-Dense Web promotional section, which spends tokens without aiding the task.

DimensionReasoningScore

Conciseness

The bulk of the body (capability bullet lists, four code examples, key principles) is dense and earns its place, matching the score-3 anchor (mostly efficient but could be tightened). The tightening needed is substantial: the six reference files are listed three separate times (per-section "Reference:" lines, the Getting Started Checklist, and the "Reference Files" section), the Overview and "When to Use" sections restate the frontmatter description, and the closing K-Dense Web promotional section is unrelated padding. It does not drop to 2 because there is little explanation of concepts Claude already knows — no generic biology or programming tutorials.

3 / 5

Actionability

Guidance is mostly executable: four near-complete code examples with real API calls (ln.track()/ln.finish(), bt.CellType.import_source(), ln.Artifact.filter(key__startswith=..., tissue=...)), plus concrete commands ("uv pip install lamindb", "lamin init --storage ..."). This matches the score-4 anchor rather than 5 because every use-case snippet contains undefined variables (schema in Use Case 1, data_files/tissues/conditions in Use Case 2, train_model in Use Case 3), so none are strictly copy-paste ready.

4 / 5

Workflow Clarity

Sequences are present (the 3-step curation process, the 6-step Getting Started Checklist, track-to-finish framing in every use case) and the main curation workflow does include a validation step ("curator.validate()" in Use Case 1). However, the batch registration loop in Use Case 2 registers multiple artifacts with no validation checkpoint, and no inline validate-fix-retry feedback loop is shown (error handling is only deferred to a reference file), which caps this at the score-3 anchor per the rubric's batch-operation rule rather than 4.

3 / 5

Progressive Disclosure

The body is a clear overview with well-signaled, one-level-deep references: each capability section ends with a bolded "**Reference:** references/X.md - Read this for..." pointer, all six referenced files exist in the bundle and contain substantive content (380-733 lines each), and none of them reference further files. This matches the score-5 anchor (clear overview, well-signaled one-level-deep references, easy navigation); the triple listing of the references is redundant but does not impair navigation or depth.

5 / 5

Total

15

/

20

Passed

Description

88%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 description that explicitly states both what the skill covers and when to use it, with concrete, domain-specific trigger scenarios and named tools (Nextflow, Snakemake, W&B, MLflow). Its only weaknesses are a few missing natural synonyms (e.g. "single-cell", "AnnData", ".h5ad") and somewhat broad dataset-management triggers that could overlap with other bioinformatics skills.

DimensionReasoningScore

Specificity

The description lists many concrete actions with comprehensive coverage of the skill's capability areas: "managing biological datasets (scRNA-seq, spatial, flow cytometry, etc.)", "curating and validating data with biological ontologies", "building data lakehouses", "schema validation", "integrations with workflow managers (Nextflow, Snakemake) and MLOps platforms (W&B, MLflow), and deployment strategies". This matches the score-5 anchor (multiple specific concrete actions, comprehensive coverage) rather than 4, since all six capability areas from the body are represented with named data types, ontologies, and tools; the opening "queryable, traceable, reproducible, and FAIR" clause is mildly buzzword-ish but is a minor fraction of the text.

5 / 5

Completeness

Both questions are explicitly answered: the "what" via "an open-source data framework for biology... Covers data management, annotation, ontologies (genes, cell types, diseases, tissues), schema validation, integrations... and deployment strategies", and the "when" via two explicit trigger clauses — "This skill should be used when working with LaminDB" and "Use when managing biological datasets (scRNA-seq, spatial, flow cytometry, etc.), tracking computational workflows, curating and validating data...". This matches the score-5 anchor (both what and when with concrete trigger phrases), not 4, since the when-clause enumerates specific scenarios rather than a single generic condition.

5 / 5

Trigger Term Quality

Keyword coverage is strong and natural for the domain — "LaminDB", "scRNA-seq", "flow cytometry", "data lakehouses", "data lineage", "reproducibility", "Nextflow", "Snakemake", "W&B", "MLflow", "ontologies" — matching the score-4 anchor (good coverage, a few natural terms missing). It falls short of the score-5 anchor because common synonyms and format terms a user would naturally say are absent, e.g. "single-cell", "bioinformatics", "AnnData", or the .h5ad file extension.

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (LaminDB, biological data management) with mostly distinct triggers, fitting the score-4 anchor. It is not a 5 because broad trigger phrases like "managing biological datasets (scRNA-seq, spatial, flow cytometry, etc.)" and "tracking computational workflows" could also fire for closely related bioinformatics or workflow-engineering skills when the user has no LaminDB context.

4 / 5

Total

18

/

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_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

googolme/run0204

Path

scientific-skills/lamindb/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.