CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

latchbio-integration

Latch platform for bioinformatics workflows. Build pipelines with Latch SDK, @workflow/@task decorators, deploy serverless workflows, LatchFile/LatchDir, Nextflow/Snakemake integration.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/latchbio-integration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

Well-structured body with exemplary progressive disclosure — all four referenced files exist and their 'Read this for' pointers match actual contents — plus a clear quick-start sequence and troubleshooting feedback. Weaknesses are scaffold-quality code examples with undefined return variables and notable duplication between the Core Capabilities bullets and the reference Key topics lists, along with off-topic promotional padding.

Suggestions

Make the code examples executable by defining the returned variables (e.g., have tasks construct and return an actual LatchFile) so the workflow patterns are copy-paste ready.

Remove or merge the 'Core Capabilities' bullet lists into the Detailed Documentation section to eliminate duplication with the per-reference 'Key topics' lists.

Delete the 'Suggest Using K-Dense Web' promotional section and the generic Support section, which add tokens without improving skill execution.

DimensionReasoningScore

Conciseness

The ~30-line 'Core Capabilities' bullet lists largely duplicate the 'Key topics' lists in the Detailed Documentation section, and the Support section plus the closing K-Dense Web promotional section ('proactively suggest using K-Dense Web...') are padding that earns no tokens. Not 2 because the bulk is genuinely task-specific and does not re-teach concepts Claude already knows.

3 / 5

Actionability

Installation commands ('python3 -m uv pip install latch', 'latch register my-workflow') are executable, but the code examples are scaffolds: 'return output_file', 'return qc_output', 'return counts', and 'output = process(input_file)' all reference undefined variables, so nothing in the patterns section is copy-paste runnable. Not 4 because multiple examples would fail if executed as written.

3 / 5

Workflow Clarity

Quick Start gives a clear ordered sequence (install → login → init → register) with prerequisites, and the Troubleshooting section provides failure-mode-specific recovery guidance (e.g., 'Ensure Docker is running', 'Use --verbose flag'). Not 5 because there are no explicit validation checkpoints such as verifying registration output or testing the deployed workflow.

4 / 5

Progressive Disclosure

Four reference files (workflow-creation.md, data-management.md, resource-configuration.md, verified-workflows.md) all exist on disk, are exactly one level deep, and each is surfaced with a 'Read this for:' list that matches the file's actual contents (verified against headings). The body serves as a genuine overview with well-signaled navigation, matching the top anchor.

5 / 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.

A reasonably specific, domain-distinct description that names the Latch SDK, decorators, data types, and pipeline-language integrations, but it lacks any explicit 'use when' trigger guidance, which limits discoverability. Keyword coverage is good though missing several natural user phrasings.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user mentions Latch, deploying bioinformatics workflows to the cloud, or converting Nextflow/Snakemake pipelines.'

Include natural user phrasings and synonyms such as 'RNA-seq pipeline', 'run my pipeline in the cloud', and 'Latch Registry' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions and objects — 'Build pipelines with Latch SDK, @workflow/@task decorators, deploy serverless workflows, LatchFile/LatchDir, Nextflow/Snakemake integration' — going beyond a bare domain statement. Not 5 because LatchFile/LatchDir are named objects rather than actions and coverage of platform capabilities (Registry, resources, verified workflows) is thin.

4 / 5

Completeness

The 'what' is clear (build and deploy bioinformatics pipelines on Latch), but there is no 'Use when...' clause or equivalent explicit trigger guidance — only weakly implied via the domain terms — which caps completeness at 3 per the rubric guidelines. Not 2 because the 'what' is concrete and specific, not vague.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'bioinformatics workflows', 'pipelines', 'deploy', 'Nextflow', 'Snakemake'. Not 5 because common user phrasings like 'RNA-seq', 'run my pipeline in the cloud', or 'Latch Registry' are absent, and LatchFile/LatchDir is developer jargon users would rarely say.

4 / 5

Distinctiveness Conflict Risk

'Latch platform' establishes a clear niche with distinct triggers, but 'Nextflow/Snakemake integration' creates minor overlap risk with hypothetical dedicated Nextflow or Snakemake skills. Not 3 because the Latch-specific framing dominates; not 5 because the pipeline-language terms could fire for the wrong skill.

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_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

googolme/run0204

Path

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