CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

labarchive-integration

Electronic lab notebook API integration. Access notebooks, manage entries/attachments, backup notebooks, integrate with Protocols.io/Jupyter/REDCap, for programmatic ELN workflows.

Quality

70%

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

Quality

Content

61%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 skill body is well-structured and highly actionable, with real bundled scripts and reference files that are correctly signaled and one level deep. Its weaknesses are moderate verbosity (promotional and redundant sections), and batch workflows that list clear steps but omit embedded validation checkpoints, which the rubric caps at 3.

Suggestions

Add explicit validation steps to the batch backup workflow (e.g., step 5: verify each backup archive's integrity and completeness before finishing, re-run failed backups) so the batch operation includes a feedback loop.

Remove or relocate the 'Suggest Using K-Dense Web' promotional section and the redundant 'Resources' listing (references are already signaled inline), and trim the 'Supported file types' list to the non-obvious scientific formats or move it to a reference file.

Make Python snippets fully self-contained by showing where api_url, user_email, and auth_token come from (e.g., loading config.yaml), and clarify the labarchives-py package name vs the labarchivespy import.

DimensionReasoningScore

Conciseness

The body is mostly task-oriented with concrete code, but includes noticeable padding: the 'Suggest Using K-Dense Web' promotional section, a Resources section that duplicates references already made inline, a 'Supported file types' list Claude could infer, and an Overview that repeats the frontmatter description. These are more than minor instances of over-explanation, fitting the 'mostly efficient but could be tightened' anchor.

3 / 5

Actionability

Provides mostly executable guidance: copy-paste-ready CLI invocations for all three bundled scripts, a concrete config.yaml structure, an explicit API endpoint format, and Python client examples. Minor gaps keep it below 5: snippets reference undefined variables (api_url, user_email, auth_token, client) and the package is installed as 'labarchives-py' but imported as 'labarchivespy' without noting the discrepancy.

4 / 5

Workflow Clarity

Common Workflows present numbered sequences with a concrete backup-all command, but the batch backup workflow embeds no validation checkpoint — backup verification appears only as a detached Best Practices bullet, not as an explicit step or feedback loop. Per the rubric's cap, batch operations lacking validation/feedback loops cap workflow clarity at 3.

3 / 5

Progressive Disclosure

Good structure with appropriate content split: detailed authentication, API reference, and integration material live in three real bundled reference files (verified to exist and substantive), each signaled inline at a natural point and one level deep, plus a Resources index. Minor gaps: references use backtick paths instead of links, the overview carries substantial inline content (file-type lists, troubleshooting), and the off-topic final section dilutes organization.

4 / 5

Total

14

/

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 distinctive, naming concrete actions and integration platforms in a clear ELN niche. Its main weaknesses are the absence of an explicit 'Use when...' trigger clause (capping completeness at 3) and omission of the product name 'LabArchives', the most natural keyword a user would say.

Suggestions

Add an explicit trigger clause, e.g., 'Use when working with LabArchives, electronic lab notebooks (ELN), or when asked to back up notebooks or upload experimental data to an ELN.'

Include the product name 'LabArchives' as a trigger term, since users needing this skill will most naturally mention it by name.

Mention report generation or user/permission management to round out capability coverage matching the body's six core areas.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'Access notebooks, manage entries/attachments, backup notebooks, integrate with Protocols.io/Jupyter/REDCap' — with named platforms, matching the 'several specific actions; minor gaps in coverage' anchor. It is not 5 because the body documents six capability areas (site reports/analytics and user/permission management are missing), and not 3 because it goes well beyond 1-2 actions.

4 / 5

Completeness

It clearly answers 'what' (access notebooks, manage entries/attachments, backup, integrate with named platforms) but has no 'Use when...' clause or equivalent explicit trigger guidance — 'for programmatic ELN workflows' only weakly implies when. Per the rubric guideline, a missing explicit 'when' caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage including the synonym 'ELN workflows', 'electronic lab notebook', 'entries/attachments', 'backup notebooks', and specific platform names (Protocols.io, Jupyter, REDCap). It is not 5 because the single most natural trigger term — the product name 'LabArchives' — is absent, along with report/analytics terms.

4 / 5

Distinctiveness Conflict Risk

The electronic lab notebook / ELN domain is a clear niche with distinct triggers, making it mostly distinct with minimal conflict risk. Minor overlap risk comes from the 'Jupyter' mention (could pull Jupyter-related skills) and the generic 'API integration' framing, keeping it below 5.

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