Agent skill · software engineering · k-dense-ai
labarchive-integration
Securely integrate with the official LabArchives ELN REST-like API and Inventory API v1. Use for regional endpoint selection, signed-request construction, user authorization and UID flows, local LA container validation, and verified LabArchives integration workflows.
Why this skill is useful
Adds executable scripts for validating LabArchives API configurations and managing user credentials that aren't in public documentation.
What it needs
Requires python, uv installed locally. Requires labarchives account access. About 6k tokens when loaded. Last updated 2026-08-03. 32,849 stars on the source repository.
What this skill does
LabArchives Integration Use LabArchives APIs only from current, official method pages. The public documentation is a shared notebook, not a versioned SDK reference, so verify the specific page immediately before implementing a remote operation. Choose the Correct Surface Do not combine these interfaces: Legacy ELN API: notebook trees, entries, attachments, users, searches, exports, and site-license functions. It uses regional api.labarchives.com hosts, /api/<class>/<method> paths, XML for many responses, and signed query parameters. Inventory API v1: inventory, item types, orders, storage locations, and vendors. It documents relative /public/v1/... paths, JSON schemas, and signed X-LabArchives- request headers. Product integrations: Jupyter, REDCap, Protocols.io, GraphPad Prism, SnapGene, Geneious, and others are product-specific UI or file workflows. They are not evidence of a general LabArchives OAuth 2.0 API. Read references/apireference.md before writing API code and references/integrations.md before automating an advertised integration. Access and Credentials LabArchives ELN developer API access is an Enterprise capability. The current Inventory FAQ limits Inventory API access to Enterprise and Enterprise Plus licensees and requires an Inventory account with API permission. Contact the institution's LabArchives team or LabArchives support for access and the development documentation supplied with it. The environment names below are conventions of this skill, not vendor-defined standards: LABARCHIVESELNAPIURL — one exact regional ELN API URL ending in /api LABARCHIVESACCESSKEYID — LabArchives-issued Access Key ID (akid) LABARCHIVESACCESSPASSWORD — HMAC signing secret LABARCHIVESUSERID — optional persistent UID bound to that Access Key ID LABARCHIVESINVENTORYLABID — required for Inventory requests Keep secrets in the process environment or an approved secret manager. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills k-dense-ai/labarchive-integration