lab-notebook
Skill1 starsChanged 40 days agoNo licenceView on GitHub
Keep a wet-lab-style electronic lab notebook for a computational project: timestamped, append-only entries for every experiment, result, finding, decision, issue and note, written to dated daily pages in the project's git repo with a SHA-256 hash chain so edits or deletions are detectable. Mistakes are fixed with CORRECTION entries, never by editing. An auto-generated index groups entries by experiment and lists decisions and open issues. DECISION entries are the canonical record of project decisions and can be exported to audit/DECISIONS.md. Use automatically as work happens: when an experiment is planned or launched, a job finishes, a result is produced, an interpretation is drawn, a decision is made (by the user or agent), a problem or dead end is hit, or the user dictates a note. Also use when asked what was done, when, why a choice was made, or for the history of an experiment.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- chroline/olivertheir own version, first seen Aug 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- chroline/oliver★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- bio-diagramSkill
- claim-gateSkill
- cli-subagentsSkill
- cluster-autoscoutSkill
- cluster-rulesSkill
- codex-offloadSkill
- deslopSkill
- doc-build-gateSkill
- experiment-preflight-singlecellSkill
- experiment-preflightSkill
- fail-loud-pipelinesSkill
- gwas-analysisSkill
- job-watchSkill
- paper-outlineSkill
- phase-delegationSkill
- reproducibleSkill
- rigor-reviewSkill
- run-status-boardSkill
- science-daemon-opsSkill
- session-handoffSkill
- standing-instructionsSkill
- variant-annotationSkill
- variant-callingSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.