Document Automation on Top AI Skills

I Let My AI Agent Manage Lark Documentation for a Week — Here's What Happened

Sun, 05 Jul 2026 00:00:00 +0000

Why I Put Documentation on the Chopping Block

Our team lives inside Lark (Feishu). Meeting notes, technical specs, project briefs, onboarding guides — it is all in Lark documents. And like most teams that use collaborative docs heavily, we have a mess: 40+ documents scattered across spaces with inconsistent naming conventions, outdated meeting notes that nobody archived, and a growing pile of “untitled document” orphans that were created during a call and never revisited.

Lark Doc vs Lark Wiki: Which LarkSuite Skill Do You Need?

Sun, 21 Jun 2026 00:00:00 +0000

The Honest Verdict Up Front

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.

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?

How to Install and Use LarkDoc: Read and Write Lark Documents with AI

Sat, 20 Jun 2026 00:00:00 +0000

What This Gets You

This tutorial walks through installing LarkDoc — a skill inside the larksuite CLI that gives your AI agent direct access to Lark (Feishu) documents. By the end, your assistant will be able to fetch document content, create new docs, append or update blocks, insert images, and generate whiteboards — all through natural language. The process takes about 15 minutes if you already have a Lark tenant, or 20 minutes if you need to create one.