<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Obsidian on Kevin Sookocheff</title>
    <link>https://sookocheff.com/tags/obsidian/</link>
    <description>Recent content in Obsidian on Kevin Sookocheff</description>
    <generator>Hugo</generator>
    <language>en-ca</language>
    <lastBuildDate>Mon, 17 Aug 2026 02:37:14 +0000</lastBuildDate>
    <atom:link href="https://sookocheff.com/tags/obsidian/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Give your LLM memory with a personal knowledge base</title>
      <link>https://sookocheff.com/post/ai/giving-your-agent-some-memory/</link>
      <pubDate>Mon, 17 Aug 2026 02:37:14 +0000</pubDate>
      <guid>https://sookocheff.com/post/ai/giving-your-agent-some-memory/</guid>
      <description>&lt;p&gt;When working with LLMs I find myself needing to update or correct the
model with information specific to my work environment. The in-house
processes, bespoke systems, and tribal knowledge of how things work for
our organization is just not something that the model has been trained
on. After repeating myself a few too many times, I thought there might be
a better way to give the model access to that knowledge in a scalable way
that allows me to augment the LLMs training data with a personalized
knowledge base specific to me.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
