<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: sopkits</title>
    <description>The latest articles on DEV Community by sopkits (@sopkits).</description>
    <link>https://dev.to/sopkits</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4160788%2F90ee1353-b76c-430b-a4af-3c9a6fd8716b.png</url>
      <title>DEV Community: sopkits</title>
      <link>https://dev.to/sopkits</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sopkits"/>
    <language>en</language>
    <item>
      <title>Your AI chatbot isn't hallucinating. It's reading your outdated docs.</title>
      <dc:creator>sopkits</dc:creator>
      <pubDate>Sun, 04 Oct 2026 03:47:00 +0000</pubDate>
      <link>https://dev.to/sopkits/your-ai-chatbot-isnt-hallucinating-its-reading-your-outdated-docs-eno</link>
      <guid>https://dev.to/sopkits/your-ai-chatbot-isnt-hallucinating-its-reading-your-outdated-docs-eno</guid>
      <description>&lt;p&gt;When a support chatbot gives a wrong answer, the first instinct is to blame the model. But when I looked at how these failures are described in support and operations communities, a different pattern kept showing up: the model was faithfully repeating the documents it was given. The documents were the problem.&lt;/p&gt;

&lt;p&gt;Typical examples:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Two FAQ pages with different refund windows (7 days vs 14 days)&lt;/li&gt;
&lt;li&gt;Two different support email addresses, both "official"&lt;/li&gt;
&lt;li&gt;A policy last reviewed two years ago&lt;/li&gt;
&lt;li&gt;An answer that literally says "TBD" - and still gets retrieved&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A chatbot can't resolve a contradiction. It picks whichever page it finds first, so the answer becomes a coin flip. New employees fail in exactly the same way.&lt;/p&gt;

&lt;h2&gt;
  
  
  A small, free Claude skill for this
&lt;/h2&gt;

&lt;p&gt;I built a Claude skill called &lt;strong&gt;Knowledge Freshness Audit&lt;/strong&gt;. You attach your SOPs, policies, FAQs, or help articles, and it returns a prioritised fix list:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Contradictions&lt;/strong&gt; - the same topic with different facts, quoted side by side with file names. Listed first, because they're the most dangerous.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Outdated or undated&lt;/strong&gt; documents&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Duplicates&lt;/strong&gt; - with a recommendation on which one to keep&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No owner / unfinished&lt;/strong&gt; documents (drafts, TBD answers, empty sections)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Gaps&lt;/strong&gt; - obvious questions no document answers&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Two design decisions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;It never decides which fact is correct.&lt;/strong&gt; If one page says 7 days and another says 14, the skill flags it and asks. Only the business knows its current rule; an AI guessing here would just create a third version of the truth.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It keeps personal data out of the report.&lt;/strong&gt; It refers to files and lines instead of copying customer names, phone numbers, or account details.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test run
&lt;/h2&gt;

&lt;p&gt;I tested it on four small documents with planted problems: two contradictions (refund window and support email), three undated files, one duplicate, three files with no owner, one "TBD" answer, and one unanswered question. The skill found all of them. The test documents and the full report are in the repo's &lt;code&gt;example/&lt;/code&gt; folder, so you can check the output yourself.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;It's free and MIT-licensed:&lt;br&gt;
&lt;a href="https://github.com/sopkits/knowledge-freshness-audit" rel="noopener noreferrer"&gt;https://github.com/sopkits/knowledge-freshness-audit&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Install the &lt;code&gt;.skill&lt;/code&gt; file in Claude (requires a plan that supports Skills), attach your docs, and say: &lt;em&gt;"Audit these help docs - our chatbot keeps giving wrong answers."&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;I'd love feedback - especially on problems it misses.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;This article was written with AI assistance and reviewed by me before publishing.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>claude</category>
      <category>documentation</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
