labbook

Manage lab notebook entries, registry items, templates, and widgets via the LabBook API.

27|4|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/farnunglab/benchaid --skill labbook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: labbook
Source: https://github.com/farnunglab/benchaid/tree/main/skills/labbook
Command: npx skills add https://github.com/farnunglab/benchaid --skill labbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage lab notebook entries, registry items (plasmids, proteins, templates, widgets, and audit logs) via the LabBook service to ensure consistent documentation and traceable experiments.

Core Features & Use Cases

  • Centralized CLI for creating, listing, updating lab notebook entries, registry items, templates, widgets, and audit logs
  • Provenance and audit trails via agent-id for reproducibility
  • Easy linkage of registry items to entries and templates to widgets across projects

Quick Start

Run the LabBook CLI to list registry items and create a new lab notebook entry.

Frequently Asked Questions about labbook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track lab notebook entries and registry items for wet-lab experiments?

You can track lab notebook entries and registry items by running the LabBook CLI to create, list, and update experiments, plasmids, proteins, and templates across multiple projects. It centralizes laboratory data documentation for consistent traceability.

What is the best way to maintain audit trails for laboratory data reproducibility?

Maintaining audit trails for laboratory data requires tracking provenance via agent-id. The LabBook CLI logs actions across notebook entries and registry items, ensuring experiments remain reproducible and traceable across projects.

Can I link registry items like plasmids and proteins directly to lab notebook entries?

Yes, you can link registry items to lab notebook entries and templates to widgets across projects. The LabBook CLI manages these relationships centrally, ensuring consistent documentation and traceable experiments for wet-lab research.

Do I need an API key to manage lab notebook entries through a command line interface?

Yes, managing lab notebook entries requires environment configuration including an API key and base URL. The Go-based LabBook CLI interfaces with the LabBook API using these credentials to access and modify registry data.

How do I configure the LabBook CLI environment to access registry items and audit logs?

Configuring the LabBook CLI environment involves setting the API key and base URL. Once configured, the Go-based CLI interfaces with the LabBook API to manage notebook entries, registry items, templates, widgets, and audit logs.