<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Wiki on Top AI Skills</title><link>https://topaiskills.com/tags/wiki/</link><description>Recent content in Wiki on Top AI Skills</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 20 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://topaiskills.com/tags/wiki/index.xml" rel="self" type="application/rss+xml"/><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>