<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Knowledge Base on Top AI Skills</title><link>https://topaiskills.com/tags/knowledge-base/</link><description>Recent content in Knowledge Base on Top AI Skills</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 21 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://topaiskills.com/tags/knowledge-base/index.xml" rel="self" type="application/rss+xml"/><item><title>Lark Doc vs Lark Wiki: Which LarkSuite Skill Do You Need?</title><link>https://topaiskills.com/tutorials/comparison/lark-doc-vs-lark-wiki/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/tutorials/comparison/lark-doc-vs-lark-wiki/</guid><description>&lt;h2 id="the-honest-verdict-up-front"&gt;The Honest Verdict Up Front&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Install Lark Doc if your team lives in freeform documents. Install Lark Wiki if your knowledge lives in structured wikis. Install both if you use both.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This is not a competition where one skill is inherently better. They solve different problems with overlapping toolsets, and the right choice depends entirely on how your team organizes information inside Lark. After working through both skills in the larksuite CLI, I can tell you the practical difference comes down to one question: are you searching for a document or navigating a knowledge tree?&lt;/p&gt;</description></item><item><title>Lark Wiki</title><link>https://topaiskills.com/skills/automation/lark-wiki/</link><pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/skills/automation/lark-wiki/</guid><description>&lt;h2 id="what-it-is"&gt;What It Is&lt;/h2&gt;
&lt;p&gt;Lark Wiki is the knowledge base skill from larksuite&amp;rsquo;s CLI ecosystem — it lets your AI coding assistant search wiki pages, fetch content, create new pages, and manage Lark/Feishu wikis without leaving the terminal. Think of it as having a permanent read-write connection to your team&amp;rsquo;s internal documentation, accessible from any prompt.&lt;/p&gt;
&lt;h2 id="whats-actually-different"&gt;What&amp;rsquo;s Actually Different&lt;/h2&gt;
&lt;p&gt;The Lark suite spreads across five separate products — Docs, Wiki, Base, Sheets, and Calendar — each a different skill under the same CLI. Lark Wiki specifically handles the tree-structured knowledge base: search across wikis, read page trees, create new pages with markdown content, and list recent updates. What sets it apart from a generic browser-based wiki approach is that your AI agent can search and retrieve wiki content mid-conversation, then reference it in code or decisions without you tabbing out. Compared to exporting wikis as PDFs or copy-pasting, the feedback loop collapses to zero.&lt;/p&gt;</description></item></channel></rss>