lark-cli-workflow

Routes Lark and Feishu CLI tasks to domain skills with identity and safety controls.

4.0k|479|Updated Apr 16, 2020
One-click install
npx skills add https://github.com/huangrt01/CS-Notes --skill lark-cli-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lark-cli-workflow
Source: https://github.com/huangrt01/CS-Notes/tree/main/.codex/skills/lark-cli-workflow
Command: npx skills add https://github.com/huangrt01/CS-Notes --skill lark-cli-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Working with Lark/Feishu resources through a CLI involves many object types (docs, wiki, sheets, Base, calendar, IM, mail) with non-interchangeable tokens and different identity requirements, making it easy to call the wrong API, use the wrong identity, or leak sensitive internal data.

Core Features & Use Cases

  • Task Routing: Classifies each request and delegates to the matching lark-* skill (lark-doc, lark-wiki, lark-drive, lark-sheets, lark-base, lark-calendar, lark-im, lark-mail, and more).
  • Token and Identity Handling: Resolves wiki node wrappers to real object tokens and chooses between --as user and --as bot identities deliberately.
  • Safe Read/Write Patterns: Starts with narrow reads, prefers block-level updates over whole-document overwrites, and requires explicit intent for high-risk actions like deletes or permission changes.
  • Use Case: Given a Feishu wiki URL, resolve the underlying document token, fetch the docx content with --api-version v2, and update a specific section without touching comments or permissions.

Quick Start

Use the lark-cli-workflow skill to read this Feishu doc URL and summarize its contents without exposing internal links.

Frequently Asked Questions about lark-cli-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I read a Feishu doc from a Lark URL using the CLI?▼

Resolve the URL first, since wiki URLs often wrap the real object token, then fetch the document with docs +fetch using --api-version v2. Start with an outline or section read before pulling the full document.

Which lark skill should I use for Sheets, Base, or wiki tasks?▼

Use lark-sheets for spreadsheets, lark-base for Bitable records, lark-wiki for wiki hierarchy and members, and lark-doc for document text. The routing skill classifies the object and action, then delegates to the matching domain skill.

When should I use --as user versus --as bot with lark-cli?▼

Use --as user for personal docs, Drive, calendar, mail, IM history, and wiki spaces. Use --as bot only for app-owned resources or when the user explicitly requests an app identity.

Are docx, sheet, bitable, and wiki tokens interchangeable in Lark APIs?▼

No, these token types are not interchangeable. Wiki URLs often point to a node wrapper, so you must resolve the real object token before fetching or updating the underlying document.

What happens when lark-cli returns missing scope errors?▼

Follow the CLI hint and request the minimum needed permissions with auth login --scope. Avoid granting broader scopes than the current task requires.

Can internal Lark links or tokens be written into repository files?▼

No, internal URLs, access tokens, chat IDs, and user IDs must not be committed to tracked files. Store private source notes under .local/ and only record generalized, publicly citable lessons in the repo.