Skip to content

LabArchives Integration

Guides an agent through LabArchives ELN and Inventory API calls, signing and safe local checks

Stars
55,780
Licence
MIT
Files
8 files

What it does

Once installed, the agent knows how LabArchives electronic lab notebook and inventory APIs work: which regional endpoint to use, how to build the required HMAC-signed requests, and how to check a LabArchives attachment container file for safety. It is told to verify official method pages before writing code and to require human approval before any remote write. The bundled scripts only validate settings, print redacted request plans, and inspect local ZIP files; they do not contact LabArchives themselves.

Great for

  • Developers at institutions that already have LabArchives Enterprise API access and want help writing integration code
  • Lab data managers who need to validate regional endpoint settings or inspect a local LA container file
  • Teams auditing how LabArchives request signing works before reviewing their own code

Skip it if

  • Users without LabArchives Enterprise or Inventory API access, since the credentials and permissions required cannot be obtained from this skill
  • Anyone wanting the agent to directly edit or delete live notebook data without review, because the skill requires approval gates but the agent still performs the remote calls once approved
  • Treating the bundled scripts as a notebook backup tool, since the ZIP inspector only reads attachment container metadata

Try asking

  • “Check my LabArchives environment variables for the correct regional ELN API URL and whether a UID is present”
  • “Generate a redacted dry-run request plan for the entry_info ELN method”
  • “Write a Python function that signs an Inventory API request for GET /public/v1/users/me”
  • “Inspect this local LA container ZIP file for unsafe paths and report its manifest contents”
Step-by-step guide: how to use LabArchives IntegrationInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 8 original files, the MIT licence and an attribution note.

    labarchive-integration.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip labarchive-integration.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip labarchive-integration.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Set LABARCHIVES_* credentials in your process environment or a secret manager; the bundled tools never read .env files, but do not paste secrets into prompts.
  • Always ask the agent for a dry-run plan first and confirm the target region and notebook before approving any write.
  • Check the official LabArchives method page yourself, since the skill notes public documentation is not a versioned SDK reference.

What's inside

  • references/api_reference.md
  • references/authentication_guide.md
  • references/integrations.md
  • references/sources.md
  • scripts/entry_operations.py
  • scripts/notebook_operations.py
  • scripts/setup_config.py
  • SKILL.md

Redistributed unmodified from K-Dense-AI/scientific-agent-skills under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.