file-insight

To save chat insights to a personal knowledge vault, you promote substantive syntheses like comparisons or research findings into standalone markdown files with wikilinks, updating your vault index and ingestion log to prevent valuable analyses from disappearing into chat history.

Wikilink-based indexing for logging research notes works by writing a new markdown file containing aggressive wikilinks, then appending a one-line entry to `index.md` and adding a provenance record to `log.md` to maintain navigation and session history.

The best way to organize decision rationales and architecture analysis in a markdown vault is routing the promoted note to an appropriate folder, such as references, projects history, or ideas, based on the content shape and confirming the output is valuable before filing.

Yes, you can avoid saving duplicate or noisy chat transcripts because the promotion process only applies to substantive outputs the user explicitly confirms as valuable, filtering out unneeded conversational filler.

You need a folder structure with categories like references, ideas, projects history, people, or life-admin areas so the skill can automatically route your markdown files to the correct destination based on their content shape.