obsidian-experiment-log

To prevent Obsidian experiment note sprawl, this Skill organizes canonical notes under Experiments/ and Results/ directories, enforcing minimal section templates and cross-note linking to keep research outputs concise and comparable across runs.

Yes, this Skill automatically establishes connections from Obsidian Daily/ notes to relevant Experiment and Result notes, ensuring full traceability between daily research logs and canonical experiment findings.

Managing experiment status transitions in Obsidian research workflows is handled by creating and updating canonical Experiment notes as experiments progress from planned to running to done, driving updates through status changes.

Yes, it links experiments and results to hub or plan pages to support project-level planning, ensuring that durable findings stored under Results/ are connected to the overarching research project structure.

A Result note is created or updated when a durable finding is established from an experiment, linking the specific Experiment note to the corresponding Result note to separate evolving runs from stable conclusions.

The limitation of enforcing minimal section templates is that complex experiments requiring highly customized documentation structures may find the stable, concise sections restrictive, as comparability across runs is prioritized over flexible formatting.