vault-sync

Routes session results, decisions, and findings into Obsidian research vault files.

1|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/ZK-Theory/TDL --skill vault-sync-zk-theory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vault-sync
Source: https://github.com/ZK-Theory/TDL/tree/main/.agents/skills/vault-sync
Command: npx skills add https://github.com/ZK-Theory/TDL --skill vault-sync-zk-theory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research session outputs like quantitative results, locked decisions, and negative findings often get lost or inconsistently logged. This Skill routes each output type into the correct TDA-Research Obsidian vault file with a standardized format, replacing the manual "repo bridge" task. ## Core Features & Use Cases - Output Routing: Maps six output types (result, decision, negative, pipeline, data, paper) to their correct vault destinations such as Computational-Log.md, CONVENTIONS.md, and permanent notes. - Pre-Write Reconciliation: Greps target pages for existing entries before writing, preventing duplicate logs when parallel sessions write to the same vault page. - Standardized Entry Formats: Provides templates for computational log entries, CONVENTIONS.md decision rules, and permanent notes, plus a ready-to-copy commit message. - Use Case: After finishing an analysis session that produced a validated p-value and locked a parameter, run the sync to append a [RESULT] entry to the Computational Log and a dated rule to CONVENTIONS.md without manually editing vault files. ## Quick Start Ask the assistant to sync this session's results and decisions into the research vault using the vault-sync workflow.

Frequently Asked Questions about vault-sync

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

FAQPage Schema
How do I log research session results to an Obsidian vault?

Run the vault-sync workflow at session close, optionally with a type filter like result, decision, or negative. Each output type is routed to its designated vault file, such as Computational-Log.md for results or a new permanent note for negative findings.

How do I avoid duplicate entries when multiple sessions write to the same vault page?

The skill performs pre-write reconciliation: it greps the target page for an existing entry covering the same task and date, and for daily notes it appends a titled session section instead of overwriting. Back-dated entries are inserted at the correct reverse-chronological anchor.

When should CONVENTIONS.md be updated versus the Computational Log?

CONVENTIONS.md is updated only for locked decisions, appended as a dated rule within the relevant section. Provisional or exploratory findings go only to the Computational Log and must not modify CONVENTIONS.md.

What happens if the vault path is unreachable?

The skill outputs the fully formatted entry text for manual pasting instead of failing. It never fabricates missing numbers, using a [TO FILL] placeholder when data is unavailable.

What are the limitations of this vault sync approach?

It is tied to a specific TDA-Research vault structure with hardcoded paths and folder conventions, so it does not generalize to other vault layouts. It also relies on the operator to accurately classify output types before routing.