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

72%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable commands and code, and uses well-signaled one-level-deep references to real bundled materials. It is somewhat verbose in its overview/background and lacks explicit validation checkpoints in its batch and destructive workflows.

Suggestions

Add explicit validation/verification checkpoints to batch and destructive workflows (e.g., verify backup integrity before marking complete, retry on failure) so workflow_clarity can reach 3.

Trim the Overview background ('LabArchives is an electronic lab notebook platform...') and avoid restating the description to improve token efficiency.

Consolidate the duplicated resource listing between the inline capability sections and the final Resources section, or cross-reference once to reduce repetition.

Dimension	Reasoning	Score
Conciseness	Content is mostly efficient with concrete commands and code, but the Overview restates the description and includes light background ('LabArchives is an electronic lab notebook platform...') that Claude already knows, so it could be tightened.	2 / 3
Actionability	Provides copy-paste-ready bash commands with flags, executable Python snippets, and explicit API endpoint formats, matching the level-3 anchor for fully executable guidance.	3 / 3
Workflow Clarity	Multi-step workflows (backup, upload, integration) are sequenced, but batch/destructive operations like 'backup-all' lack explicit validation checkpoints and feedback loops, which the rubric caps at 2.	2 / 3
Progressive Disclosure	SKILL.md is a clear overview that signals one-level-deep references to real bundled files (api_reference.md, authentication_guide.md, integrations.md) and scripts, all summarized in a Resources section, with no nested reference chains.	3 / 3
	Total	10 / 12 Passed

Description

67%Weight 40%Scale 1-3

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 well-differentiated with concrete actions and named integrations, but it lacks an explicit 'Use when...' trigger clause and omits the product name users would naturally say, leaving 'when to use' only implied.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working with LabArchives or electronic lab notebooks, backing up notebooks, or integrating ELN data with Protocols.io, Jupyter, or REDCap.'

Include the product name 'LabArchives' and the natural term 'lab notebook' so the description matches user phrasing and aids discovery.

Keep the concrete action list but ensure the 'when' is stated as plainly as the 'what' rather than implied by 'for programmatic ELN workflows'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Access notebooks, manage entries/attachments, backup notebooks, integrate with Protocols.io/Jupyter/REDCap') rather than vague language, matching the level-3 anchor.	3 / 3
Completeness	Clearly states what the skill does, but the 'when' is only implied via 'for programmatic ELN workflows' with no explicit 'Use when...' clause, which per the rubric caps completeness at 2.	2 / 3
Trigger Term Quality	Covers relevant natural terms ('electronic lab notebook', 'ELN', 'notebooks', 'entries/attachments') and named integrations, but omits the product name users would say ('LabArchives', 'lab notebook') and lacks common phrasing variations.	2 / 3
Distinctiveness Conflict Risk	The ELN/LabArchives niche plus named third-party integrations (Protocols.io, Jupyter, REDCap) create a clear, distinctive trigger unlikely to collide with other skills.	3 / 3
	Total	10 / 12 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: dc00e07

Reviewed: 8 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.