CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

labarchive-integration

Converts LabArchives notebook data, entry metadata, and authorized ELN exports into manuscript-ready academic writing outputs such as Methods sections, data-availability statements, reproducibility appendices, experiment timelines, and submission support notes. Optional bundled scripts can be used to collect or validate source notebook data before writing.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/labarchive-integration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, mostly lean instructional skill with a clear validated workflow, explicit refusal and recovery contracts, and concrete per-output requirements. Its main weaknesses are duplicated deliverable listings and, more importantly, three sizable bundled reference documents that are completely unlinked from SKILL.md.

Suggestions

Add pointer lines in the body (e.g., under 'Script Usage Notes' or 'Authorized Input Sources') referencing references/api_reference.md, references/authentication_guide.md, and references/integrations.md so the bundled reference material is discoverable.

Merge the 'Primary Writing Outputs' section with the 'Writing Output Contract' section to eliminate the duplicated enumeration of the five deliverables.

Include one worked example of a script invocation with real arguments (beyond '--help') and a brief filled-in template excerpt to make the writing outputs concrete.

DimensionReasoningScore

Conciseness

The body is list-based and lean, assuming Claude's competence (no explanation of what an ELN or Methods section is), but the five deliverables are enumerated twice ('Primary Writing Outputs' then 'Writing Output Contract') and the opening framing ('Its goal is not just API access, but turning authorized ELN material into manuscript-ready writing deliverables') is padded.

4 / 5

Actionability

Concrete script commands ('python scripts/setup_config.py', '--help', 'Use --dry-run where available before live execution'), an exact refusal template, and a named template asset ('assets/writing_outputs_template.md') give mostly executable guidance; minor gaps are the absence of a real-argument script invocation and any worked example of a writing output.

4 / 5

Workflow Clarity

The five-step workflow has explicit validation checkpoints (step 1 authorization/sufficiency gate with a stop-and-refuse path, step 5 safety pass), feedback loops for error recovery (refusal contract and the 'If a script path fails' recovery instructions), and a completion checklist, matching the top anchor.

5 / 5

Progressive Disclosure

SKILL.md appropriately points to the three bundled scripts and the template asset, but the three substantial files in references/ (api_reference.md, authentication_guide.md, integrations.md) are never mentioned anywhere in the body, so those references are present but not clearly signaled.

3 / 5

Total

16

/

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 specific, distinctive description with comprehensive output coverage in proper third-person voice. Its one real weakness is the missing 'when to use' trigger clause, which caps completeness and leaves invocation conditions implicit.

Suggestions

Append an explicit trigger clause, e.g., 'Use when the user has authorized LabArchives or ELN content and needs manuscript-ready writing outputs such as Methods sections or data availability statements.'

Include the spelled-out synonym 'electronic lab notebook (ELN)' and common user phrases like 'manuscript' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

'Converts LabArchives notebook data, entry metadata, and authorized ELN exports into manuscript-ready academic writing outputs such as Methods sections, data-availability statements, reproducibility appendices, experiment timelines, and submission support notes' lists multiple specific concrete actions with comprehensive output coverage, in third-person voice, matching the top anchor.

5 / 5

Completeness

The 'what' is explicit and concrete, but there is no 'Use when...' clause or equivalent trigger guidance; the nearest phrase ('Optional bundled scripts can be used to collect or validate source notebook data before writing') describes a capability, not when to invoke the skill, so completeness is capped at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage ('LabArchives', 'notebook data', 'ELN exports', 'Methods sections', 'data-availability statements', 'reproducibility appendices', 'experiment timelines'), but the spelled-out synonym 'electronic lab notebook' and common user phrases like 'manuscript' or 'protocols' are missing.

4 / 5

Distinctiveness Conflict Risk

The LabArchives-ELN-to-manuscript-writing niche is distinct with specific trigger terms ('LabArchives', 'Methods sections', 'reproducibility appendix'), creating minimal overlap risk with other skills.

5 / 5

Total

17

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Academic Writing/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.