Опишете задачата
Към всички skills

labarchive-integration

K-Dense-AI · Разработка

Electronic lab notebook API integration. Access notebooks, manage entries/attachments, backup notebooks, integrate with Protocols.io/Jupyter/REDCap, for programmatic ELN workflows.

Оригинален текст · няма потвърден превод на български
Платформи: ClaudeНиво: НапредналоВ индекса: 04.03.2026 г.Обновен в GitHub: 11.06.2026 г.

Първо прочетете инструкцията.

Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.

Оригинален SKILL.md
GitHub хранилище
Звезди на репото
27 938
Лиценз
Не е посочен. Проверете в репозитория.
Последна проверка на записа
Няма посочена дата

Добавете в своя инструмент.

Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.

npx skills add K-Dense-AI/claude-scientific-skills

Страницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.

Откъс от SKILL.md

Началото на файла на автора, без превод.

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 response 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/api_reference.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:

  • LABARCHIVES_ELN_API_URL — one exact regional ELN API URL ending in /api
  • LABARCHIVES_ACCESS_KEY_ID — LabArchives-issued Access Key ID (akid)
  • LABARCHIVES_ACCESS_PASSWORD — HMAC signing secret
  • LABARCHIVES_USER_ID — optional persistent UID bound to that Access Key ID
  • LABARCHIVES_INVENTORY_LAB_ID — required for lab-scoped Inventory requests; omitted during GET /public/v1/users/me lab discovery

Keep secrets in the process environment or an approved secret manager. Do not put them in YAML, source code, command-line arguments, prompts, logs, notebooks, or committed .env files. The bundled tools never search for .env files.

From this skill directory:

uv run scripts/setup_config.py regions
uv run scripts/setup_config.py check --require-user-id

Целият SKILL.md в GitHub