instrument-data-to-allotrope

Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full ASM JSON, flattened CSV for easy import, and exportable Python code for data engineers. Common triggers include converting instrument files, standardizing lab data, preparing data for upload to LIMS/ELN systems, or generating parser code for production pipelines.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

88%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, actionable skill body with clear workflow checkpoints and properly split references. Minor conciseness padding and minor duplication of reference content keep it just below top marks.

Suggestions

Trim the 'Example Skill' note and restated tier intros to tighten the token budget.

Move the inline 'Common calculated fields' and 'Supported Instruments' summary tables to their reference files to reduce duplication and rely on the one-level-deep links.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable snippets, tables, and tiered structure, but the example-skill note block and a few restating sentences ('Always try allotropy first') add minor padding.	4 / 5
Actionability	Provides copy-paste-ready code (Quick Start, detection loop, validation, export) and concrete file paths that cover the common cases and reference real bundle files.	5 / 5
Workflow Clarity	Clear multi-step Workflow Overview with an explicit 'When Uncertain' clarification checkpoint, a Pre-Parsing Checklist, and validation feedback loops (--strict/--reference) before delivery.	5 / 5
Progressive Disclosure	Well-signaled one-level-deep references to verified real files (supported_instruments.md, asm_schema_overview.md, field_classification_guide.md, flattening_guide.md), though a few inline tables duplicate reference content.	4 / 5
	Total	18 / 20 Passed

Description

88%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 strong, specific description with clear what/when structure and natural trigger phrasing. Minor overlap risk from generic file extensions and a few missing trigger synonyms.

Suggestions

Add a few more natural trigger synonyms (e.g., 'parse instrument exports', 'instrument data into Allotrope') to broaden trigger coverage.

Tighten the file-type framing to emphasize the Allotrope/ASM destination, reducing overlap with generic file-conversion skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions—convert PDF/CSV/Excel/TXT to ASM JSON or flattened CSV, auto-detect instrument types, and export Python parser code—covering the workflow comprehensively.	5 / 5
Completeness	Explicitly answers both what (convert instrument output to ASM JSON/flattened CSV/exportable Python) and when ('Use this skill when scientists need to standardize instrument data...', plus a 'Common triggers' clause).	5 / 5
Trigger Term Quality	Includes natural triggers like 'standardizing lab data', 'upload to LIMS/ELN systems', and 'parser code for production pipelines' plus file extensions, but a few common natural phrasings are missing.	4 / 5
Distinctiveness Conflict Risk	The Allotrope/ASM/LIMS niche is distinct, though broad file-type triggers (PDF/CSV/Excel/TXT) create minor overlap risk with generic file-conversion skills.	4 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: anthropics/knowledge-work-plugins
Path: bio-research/skills/instrument-data-to-allotrope/SKILL.md
Commit: 8444efc

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