CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

labarchive-integration

Integrates with the official LabArchives ELN REST-like API and Inventory API v1. Supports regional endpoint selection, signed-request construction, user authorization and UID flows, local LA container validation, and verified LabArchives integration workflows.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplarily disciplined integration skill: every command is runnable, security and validation rules are concrete and prominent, and detail is correctly offloaded to real, well-signaled bundle files. The only real weaknesses are a missing error-recovery loop in the remote-write workflow and dated client-version details living in the main body instead of a deprecated/old-patterns section.

DimensionReasoningScore

Conciseness

The body is dense with vendor-specific, non-obvious facts (regional hosts, signing inputs, header names, retry rules) and spends almost no tokens explaining concepts Claude already knows, matching the 'efficient; minor instances of over-explanation' anchor. It is not 5 because dated, time-sensitive details (the August 2022 mcmero commit, community release 1.2.0 of 2026-08-20) sit in the main 'Python Clients' section rather than a dedicated old-patterns/deprecated section, and the closing citation section runs long for the body; it is above 3 because padding is genuinely rare and every section carries operational weight.

4 / 5

Actionability

Guidance is fully executable: copy-paste-ready commands ('uv run scripts/setup_config.py regions', 'uv run scripts/entry_operations.py eln-plan --api-class entries --api-method entry_info'), exact environment-variable names, the complete five-step HMAC-SHA-512 signing recipe, and exact header names for Inventory calls. It matches the anchor for copy-paste-ready commands covering common cases; there is no pseudocode and no underspecified step, so 4's 'minor gaps' does not apply.

5 / 5

Workflow Clarity

The 'Before any remote write' section is a clear five-step numbered sequence with explicit validation checkpoints (verify the official method page first; produce a redacted dry-run plan; require approval; 'Re-read and verify the resulting object; do not infer success from HTTP 200'), and the operational rules add bounded retry/backoff behavior. It is not 5 because there is no explicit error-recovery loop after step 5 (what to do when the verified response does not match the plan), and it is above 3 because validation is explicit and prominent rather than implicit.

4 / 5

Progressive Disclosure

The body is a well-structured overview that keeps operational rules inline and pushes detail to four clearly signaled, one-level-deep references, each linked in context ('Read references/api_reference.md before writing API code') and enumerated with purpose in a References section; all referenced files and the three scripts exist in the bundle with no nested multi-hop references. This matches the anchor for a clear overview with well-signaled one-level-deep references and easy navigation.

5 / 5

Total

18

/

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 highly specific, well-scoped description that comprehensively names the skill's capabilities with no fluff, held back only by a missing explicit 'when to use' clause and unexpanded synonyms like 'electronic lab notebook'. Third-person voice is used correctly and no claims are overstated.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when integrating with or automating LabArchives electronic lab notebooks, inventory management, or its ELN/Inventory APIs.'

Spell out 'electronic lab notebook (ELN)' once so users who say the full phrase instead of the abbreviation still match the description.

Consider mentioning 'notebook entries, attachments, and inventory items' as natural user-facing nouns to broaden trigger-term coverage without adding vagueness.

DimensionReasoningScore

Specificity

The description lists five concrete, distinct actions — "regional endpoint selection, signed-request construction, user authorization and UID flows, local LA container validation, and verified LabArchives integration workflows" — against two named API surfaces ("official LabArchives ELN REST-like API and Inventory API v1"), matching the comprehensive-coverage anchor. It is not below 5 because no capability area named in the body is missing from the description; it is above 4 because coverage is multiple and specific rather than 'several with minor gaps'.

5 / 5

Completeness

The "what" is clear and specific, but there is no "Use when..." clause or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. It is not 2 because the "what" half is concrete and multi-part (not vague), and it cannot be 4 without any 'when' element at all.

3 / 5

Trigger Term Quality

"LabArchives", "ELN", "Inventory API", "UID", and "integration" are natural phrases a user needing this skill would say, giving good keyword coverage. It falls short of the 5 anchor because common synonyms and expansions are missing — "electronic lab notebook" is never spelled out (only the abbreviation ELN), and terms like "notebook" or "API access" are absent — while it is above 3 because the core brand and product terms are all present.

4 / 5

Distinctiveness Conflict Risk

The LabArchives ELN/Inventory niche is highly specific, and the description scopes itself to "the official LabArchives ELN REST-like API and Inventory API v1", giving minimal conflict risk with other skills. It is not 4 because every trigger term is vendor-anchored rather than sharing generic wording with neighboring skills.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

K-Dense-AI/scientific-agent-skills

Path

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.