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

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./backend/cli/skills/other/labarchive-integration/SKILL.md

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.

The body is well-structured with strong progressive disclosure to real bundle files and mostly executable examples, but suffers from section redundancy and missing inline validation checkpoints in its batch/destructive workflows.

Suggestions

Add explicit validation checkpoints into the backup-all and upload workflows (e.g., verify backup integrity and attachment completeness before proceeding to the next notebook).

Collapse redundant capability listings across Overview, When to Use, and Core Capabilities into a single concise section to reduce token overhead.

Dimension	Reasoning	Score
Conciseness	Content is mostly efficient and information-dense, but the Overview, When to Use, and Core Capabilities sections restate overlapping capabilities and could be tightened to remove redundancy.	3 / 5
Actionability	Provides mostly executable guidance with real bash commands (flags included) and Python wrapper code examples, with only minor gaps in covering all common cases.	4 / 5
Workflow Clarity	Numbered multi-step workflows are present (backup, upload, integration), but the batch/destructive 'backup-all' workflow lacks inline validation checkpoints, capping workflow clarity at 3 per the destructive/batch guidance.	3 / 5
Progressive Disclosure	Clear overview structure with well-signaled one-level-deep references to real bundle files (scripts/.py, references/.md), all of which exist, plus a Resources section enumerating them for easy navigation.	5 / 5
	Total	15 / 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.

The description is specific and distinctive with strong trigger terms, but lacks an explicit 'Use when...' trigger clause, leaving the 'when to use' guidance only weakly implied and capping completeness.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when automating LabArchives notebook operations, backing up ELN data, or integrating with Protocols.io, Jupyter, or REDCap').

Include the product name 'LabArchives' directly in the description to strengthen distinctiveness and trigger matching.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Access notebooks, manage entries/attachments, backup notebooks, integrate with Protocols.io/Jupyter/REDCap') with comprehensive coverage of the skill's capabilities, matching the anchor for multiple specific concrete actions.	5 / 5
Completeness	The 'what' is clearly stated via concrete actions, but the 'when' is only weakly implied by 'for programmatic ELN workflows' with no explicit 'Use when...' trigger clause, so completeness is capped at 3 per the guidelines.	3 / 5
Trigger Term Quality	Good natural keyword coverage ('electronic lab notebook', 'notebooks', 'ELN', 'backup', named tools Protocols.io/Jupyter/REDCap) that users would actually say, though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	A clear niche (electronic lab notebook API integration) with distinct triggers and named third-party platforms gives minimal conflict risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: synthetic-sciences/openscience
Path: backend/cli/skills/other/labarchive-integration/SKILL.md
Commit: a820c2f

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.