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

62%

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 ./skills/bio/labarchive-integration/SKILL.md

Quality

Content

65%

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

The body is actionable with concrete commands and code, but it is verbose, inlines API-reference material that belongs in the (currently missing) reference files, and omits validation checkpoints for batch/backup workflows.

Suggestions

Add an explicit verification step to the backup and backup-all workflows (e.g. confirm archive integrity and entry count after each notebook) to lift workflow clarity.

Move inline API endpoint formats, supported file types, and integration lists into references/api_reference.md and references/integrations.md so SKILL.md stays a lean overview.

Create the referenced bundle files (references/*, scripts/*) so the signaled navigation actually resolves, and drop the duplicate 'Resources' section that re-lists them.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with actionable code, but it includes padding — a restating 'Overview', a 'Resources' section that re-lists scripts/references already cited inline, and capability lists — that could be tightened; not a 3.	2 / 3
Actionability	Provides copy-paste-ready commands (e.g. 'python3 scripts/notebook_operations.py backup --uid USER_ID --nbid NOTEBOOK_ID --json --no-attachments'), concrete Python wrapper usage, and an explicit API endpoint format — fully executable guidance.	3 / 3
Workflow Clarity	Multi-step workflows (backup-all, data upload, Jupyter integration) are sequenced, but batch/backup operations lack explicit validation checkpoints, capping workflow clarity at 2 per the rubric's batch-operation rule.	2 / 3
Progressive Disclosure	References are signaled one level deep (api_reference.md, authentication_guide.md, integrations.md), but those bundle files do not exist and substantial API-reference content is inlined in SKILL.md rather than split out, matching the 'content that should be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

60%

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 names several concrete actions, but it never mentions the LabArchives brand and lacks an explicit 'Use when...' trigger clause, capping completeness and trigger-term quality.

Suggestions

Add the product name 'LabArchives' so the description matches the natural term users say when they need this skill.

Append an explicit trigger clause such as 'Use when automating LabArchives notebooks, backing up entries, or integrating ELN data with Protocols.io/Jupyter/REDCap'.

Lead with the concrete actions and drop the generic 'Electronic lab notebook API integration' opener to sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'Access notebooks, manage entries/attachments, backup notebooks, integrate with Protocols.io/Jupyter/REDCap' — clearly above the 'names domain and some actions' anchor at 2.	3 / 3
Completeness	Clearly answers 'what' but the only 'when' cue is 'for programmatic ELN workflows', an audience/context clause rather than an explicit 'Use when...' trigger, so it is capped at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Contains relevant natural terms ('Electronic lab notebook', 'ELN', 'notebooks', 'entries/attachments', 'backup notebooks') but omits the brand 'LabArchives' that a user would actually say, leaving common variations uncovered.	2 / 3
Distinctiveness Conflict Risk	Named third-party integrations (Protocols.io/Jupyter/REDCap) narrow the niche, but the generic 'electronic lab notebook' phrasing without the LabArchives brand could overlap with other ELN skills.	2 / 3
	Total	9 / 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
referenced_paths_exist	Referenced path issues: 12 missing	Warning

	Total	14 / 16 Passed

Repository: wu-yc/LabClaw
Path: skills/bio/labarchive-integration/SKILL.md
Commit: df37802

Reviewed: about 2 hours 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.