Lark on Top AI Skills

I Let AI Handle My Team's Approval Workflow for a Week — Here's What Happened

Fri, 17 Jul 2026 00:00:00 +0000

I handed my AI agent control over our team’s approval workflow for five days. Expense reports, leave requests, purchase orders — all processed through an AI skill. Here is what went right, what broke, and whether I would do it again.

Why I Decided to Try This

Our team runs on Lark. I manage a group of fifteen engineers, a couple of product managers, and a rotating cast of interns. Every week brings a steady stream of approval requests. Leave applications, hardware purchase requests, conference travel approvals, expense reports from team lunches — the kind of administrative overhead that is simple but constant.

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.

AI Workflow Automation Skills Compared: Microsoft Foundry vs Azure AI vs Lark Tools

Wed, 01 Jul 2026 00:00:00 +0000

The Short Version

Install Microsoft Foundry if your team is all-in on Azure and you need to orchestrate multi-step AI workflows that touch Azure services. Install Azure AI if you want a general-purpose AI assistant that integrates with your codebase and Azure resources. Install Lark Doc if your team lives in Lark and needs AI-powered document workflows. Install Lark Base if you need AI-driven database management inside Lark.

These four skills occupy different corners of the workflow automation space, but they share a common DNA: each lets you describe a process in natural language and have an AI agent execute it across one or more tools. The question is which ecosystem you’re already in and what kind of automation you need most.

Lark Base

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

What It Is

A skill inside the larksuite CLI that gives your AI agent structured access to Lark Base — the spreadsheet-database hybrid in Lark’s productivity suite. Your assistant can query records, create and update rows, list tables, and search across bases, all through natural language instead of clicking through the web UI or writing raw API calls.

What’s Actually Different

Most database queries from an AI agent require either a SQL connection string in your environment or a custom API wrapper that breaks every time the schema changes. Lark Base uses the same shared authentication as the other 25 skills in the larksuite CLI — the same login that reads documents, manages wikis, and creates calendar events also handles Base operations. Compared to setting up a direct database connection, you get row-level access control through Lark’s permission model, schema-aware queries that respect field types, and no credential sprawl across your tooling.

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.

Lark Wiki

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

What It Is

Lark Wiki is the knowledge base skill from larksuite’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’s internal documentation, accessible from any prompt.

What’s Actually Different

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.

LarkDoc

Mon, 15 Jun 2026 00:00:00 +0000

What It Is

A skill inside the larksuite CLI that gives your AI agent direct access to Lark (Feishu) documents. Your assistant can fetch document content, create new docs, append or update blocks, insert images, and generate whiteboards — all through natural language commands instead of clicking through the web UI.

What’s Actually Different

Most document automation tools require custom API wrappers or Zapier-style integrations that break on the first auth refresh. This skill is part of a purpose-built CLI with 200+ commands and 26 agent skills, all sharing a single authentication session. The same login that lets your agent read a document also lets it create Base records, manage calendar events, and send chat messages. Compared to building bespoke API calls, you get a tested, maintained integration that stays in sync with Lark’s platform updates.