CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lamindb

This skill is applicable when using LaminDB. LaminDB is an open-source data framework for biology that makes data queryable, traceable, reproducible, and FAIR-compliant. It is suitable for managing biological datasets (scRNA-seq, spatial transcriptomics, flow cytometry, etc.), tracking computational workflows, curating and validating data with biological ontologies, building data lakes, or ensuring data lineage and reproducibility in biological research. It covers data management, annotation, ontologies (genes, cell types, diseases, tissues), schema validation, integration with workflow managers (Nextflow, Snakemake) and MLOps platforms (W&B, MLflow), and deployment strategies.

Quality

67%

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

Quality

Content

46%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 has a genuinely good progressive-disclosure architecture with six real, well-signaled reference files and substantive API coverage, but it is undermined by heavy auto-generated boilerplate, duplicated trigger sections, code examples with undefined variables, and missing validation/error-recovery checkpoints. The first quarter of the file is padding that adds no actionable value.

Suggestions

Delete the boilerplate sections: the duplicated description in 'When to Use' and 'Key Features', the fake 'Example Usage' directory listing, the 'Implementation Details' section that points to '## Overview above', and the trailing K-Dense Web advertisement — keep a single concise 'When to Use' section.

Make the four use-case examples self-contained and executable: define the 'schema' variable in Use Case 1, initialize 'data_files'/'tissues'/'conditions' in Use Case 2, replace the undefined 'train_model' call with a real estimator (e.g., sklearn) in Use Case 3, and label Use Case 4 explicitly as a Nextflow template.

Add explicit validation checkpoints with error-recovery loops to the curation and data-registration workflows (e.g., 'run curator.validate(); if it fails, standardize with .cat.standardize() and re-validate before save_artifact()').

DimensionReasoningScore

Conciseness

The first ~50 lines are auto-generated boilerplate: the frontmatter description is repeated verbatim (lowercased) in 'When to Use' and again word-for-word in 'Key Features' ('Scope-focused workflow aligned to: This skill is applicable when using LaminDB...'), followed by filler like the fake directory listing in 'Example Usage', an 'Implementation Details' section that just says 'See ## Overview above for related details', and an unrelated K-Dense Web advertisement at the end. There are also two overlapping 'When to Use' sections. Not 1 because the core capability sections and code examples do carry real, non-redundant information; firmly at 2 because several padded sections teach nothing Claude doesn't already know.

2 / 5

Actionability

Concrete guidance exists — install commands ('uv pip install lamindb', 'lamin login', 'lamin init --storage ...'), API calls ('ln.track()', 'bt.CellType.import_source()', 'curator.validate()', 'ln.Artifact.filter(key__startswith="scrna/", ...)') — but the use-case examples are not executable as written: undefined 'schema' in Use Case 1, undefined 'data_files', 'tissues', 'conditions' in Use Case 2, undefined 'train_model' in Use Case 3, and Nextflow template pseudocode ('${batch_id}') in Use Case 4. Not 4 because multiple examples fail as copy-paste code due to undefined variables; not 2 because there is substantial specific, correct API usage beyond high-level hints.

3 / 5

Workflow Clarity

The 'Getting Started Checklist' provides a reasonable six-step learning sequence and 'Key Principles' gives ordering guidance ('Validate early', 'Query metadata first'), and curator.validate() appears in Use Case 1. But no workflow includes error-recovery checkpoints — there is no 'if validation fails, fix and re-run' loop, and the curation section lists validation steps without any failure handling — so checkpoints are implicit at best. Not 4 because validation/feedback loops for the curation and pipeline workflows are absent; not 2 because sequences are present and reasonably defined.

3 / 5

Progressive Disclosure

Structure is good: six one-level-deep reference files (core-concepts.md, data-management.md, annotation-validation.md, ontologies.md, integrations.md, setup-deployment.md) all exist and each capability section clearly signals its reference ('Reference: references/... - Read this document for...'), plus a consolidated 'Reference Files' index. Not 5 because SKILL.md itself runs ~430 lines with each capability summarized inline before pointing to its reference, and the boilerplate front sections ('Example Usage', 'Implementation Details', duplicated 'When to Use') add navigational noise; not 3 because references are clearly signaled, shallow, and well-indexed.

4 / 5

Total

12

/

20

Passed

Description

75%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 solid third-person description that clearly conveys both what LaminDB does and when the skill applies, with good domain-specific trigger vocabulary. Its weaknesses are moderately abstract action verbs, a self-referential trigger clause, and a few missing natural synonyms (AnnData, Bionty, single-cell).

DimensionReasoningScore

Specificity

Lists several specific actions — 'managing biological datasets (scRNA-seq, spatial transcriptomics, flow cytometry, etc.)', 'tracking computational workflows', 'curating and validating data with biological ontologies', 'schema validation, integration with workflow managers (Nextflow, Snakemake) and MLOps platforms (W&B, MLflow)' — written in third person. Not 5 because the actions are capability-level abstractions ('managing', 'covers') rather than fully concrete operations, leaving minor gaps; not 3 because coverage goes well beyond 1-2 actions and spans the framework's scope.

4 / 5

Completeness

Both parts are present: a clear 'what' ('an open-source data framework for biology that makes data queryable, traceable, reproducible, and FAIR-compliant') and an explicit 'when' ('This skill is applicable when using LaminDB... It is suitable for managing biological datasets...'). Not 5 because the 'when' clause is somewhat self-referential ('when using LaminDB') rather than concrete user-side trigger phrases like 'Use when the user mentions single-cell data or .h5ad files'; not 3 because the trigger guidance is explicit, not merely implied.

4 / 5

Trigger Term Quality

Good coverage of natural domain terms a user would say: 'scRNA-seq', 'spatial transcriptomics', 'flow cytometry', 'data lakes', 'biological ontologies', 'Nextflow', 'Snakemake', 'W&B', 'MLflow', 'FAIR', 'data lineage'. Not 5 because a few natural synonyms and file extensions users commonly mention are missing (e.g., 'single-cell', 'AnnData', '.h5ad', 'Bionty', 'cite-seq'); not 3 because coverage includes many variations across modalities and tooling rather than just a few keywords.

4 / 5

Distinctiveness Conflict Risk

The biology anchor throughout ('biological datasets', 'biological ontologies', 'biological research', 'scRNA-seq') plus the named framework give it a clear niche with minimal wrong-skill triggering. Not 5 because broader phrases like 'building data lakes', 'data management', and 'deployment strategies' create minor overlap risk with generic data-engineering and MLOps skills.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

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