Skip to content
Skills Library
Documents & office · Automation

lark-cli-workflow

/lark-cli-workflow

Coordinate Lark/Feishu CLI tasks from Codex. Use when a request involves Feishu/Lark docs, wiki, Drive files, Sheets, Base, Calendar, Minutes, IM, Mail, Tasks, Contacts, Slides, whiteboards, approvals, attendance, or when a Lark URL/token must be read, edited, summarized, routed, or turned into a real work artifact.

Repository
cs-notes ↗
Licence
MIT
Last repository change
26.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Coordinate Lark/Feishu CLI tasks from Codex. Use when a request involves Feishu/Lark docs, wiki, Drive files, Sheets, Base, Calendar, Minutes, IM, Mail, Tasks, Contacts, Slides, whiteboards, approvals, attendance, or when a Lark URL/token must be read, edited, summarized, routed, or turned into a real work artifact.

Original author description

Coordinate Lark/Feishu CLI tasks from Codex. Use when a request involves Feishu/Lark docs, wiki, Drive files, Sheets, Base, Calendar, Minutes, IM, Mail, Tasks, Contacts, Slides, whiteboards, approvals, attendance, or when a Lark URL/token must be read, edited, summarized, routed, or turned into a real work artifact.

How it works

  1. Default Route
  2. Read Pattern
  3. Write Pattern
  4. Repo Safety
  5. Completion Check
Original SKILL.md headings · 57 lines, 572 words
SKILL.md preview
---
name: lark-cli-workflow
description: Coordinate Lark/Feishu CLI tasks from Codex. Use when a request involves Feishu/Lark docs, wiki, Drive files, Sheets, Base, Calendar, Minutes, IM, Mail, Tasks, Contacts, Slides, whiteboards, approvals, attendance, or when a Lark URL/token must be read, edited, summarized, routed, or turned into a real work artifact.
---

# Lark CLI Workflow

This is a thin routing skill. Prefer the official `lark-*` skills and `lark-cli` shortcuts for domain details; use this skill to choose the right path, identity, safety level, and final artifact shape.

## Default Route

1. Classify the object and action.
   - Docs / Wiki text: `lark-doc`, with `docs +fetch --api-version v2`.
   - Wiki hierarchy / members: `lark-wiki`.
   - Drive files, file permissions, comments, import/export: `lark-drive`.
   - Sheets: `lark-sheets`.
   - Base / Bitable: `lark-base`.
   - Calendar / meeting-room scheduling: `lark-calendar`.
   - Past meetings and transcripts: `lark-vc` or `lark-minutes`.
   - IM messages, groups, files in chats: `lark-im`.
   - Mail: `lark-mail`.
   - Contacts / people resolution: `lark-contact`.
   - Tasks, OKR, approval, attendance, slides, whiteboard: use the matching `lark-*` skill.
2. For any Lark URL or opaque token, inspect or unwrap it before acting.
   - Wiki URLs often point to a node wrapper; resolve the real object token before document fetch/update.
   - Do not assume a docx token, sheet token, bitable token, wiki node token, and drive file token are interchangeable.
3. Pick identity deliberately.
   - Use `--as user` for personal docs, Drive, calendar, mail, IM history, wiki spaces, and most user-owned resources.
   - Use `--as bot` only for app-owned resources or when the user explicitly wants an app identity.
   - If a command returns missing scopes, follow the CLI hint and request the minimum needed `auth login --scope ...`.

## Read Pattern

- Start narrow: outline, keyword, section, or metadata before full document fetch.
- For Docx v2, always pass `--api-version v2`.
- Use JSON output when the result will feed another command.
- If a document contains embedded sheets, bitables, synced blocks, media, or whiteboards, extract the referenced token and switch to the matching skill instead of summarizing the tag itself.
- Treat internal links, auth URLs, media URLs, access tokens, user IDs, and chat IDs as private unless the user explicitly asks for them in chat.

## Write Pattern

- Prefer real work artifacts: create or update the Lark doc, Base record, Sheet range, task, calendar event, email draft, or IM message instead of only producing copy-paste text.
- Before writing, identify the intended object, block/range/record, and command.
- Prefer block-level or section-level updates over whole-document overwrite.
- Preserve comments, highlights, citations, permissions, reviewer-visible formatting, and document structure unless the user asks to replace them.
- High-risk actions need explicit intent or a dry run first: delete, overwrite, permission change, bulk send, group membership change, task closeout, or external sharing.

## Repo Safety

- Do not write internal Lark URLs, temporary media/auth URLs, access tokens, chat IDs, internal people/team details, or non-public implementation details into tracked repository files.
- If an internal source has reusable public lessons, write only the generalized lesson and cite public/open sources when available, such as the Lark CLI public repository: https://github.com/larksuite/cli
- Put private source notes, exact internal links, and sensitive judgments under `.local/` when a local record is useful.
- For CS-Notes tasks, update `AGENTS.md`, `.trae/`, `.codex/skills/`, or `Notes/` only when the result improves the durable workflow; avoid demo-only files.

## Completion Check

- Say which Lark object was read or changed, using a safe title or type when links are sensitive.
- Report identity used (`user` or `bot`) when it matters.
- Mention missing permissions, unread embedded resources, or skipped high-risk actions.
- If `lark-cli` suggests an update, finish the current task first, then tell the user the update is available.

Versions

The database has no other skills named lark-cli-workflow.

Database snapshot: 13.11.2026 · package version cc264f4289ab (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 85lark
    Lark/Feishu CLI router: match intent, then Read the Entry file under lark-*/ (e.g. lark-doc/lark-doc.md). Covers docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, note, event via…
  • 90lark-cli
    Use lark-cli for 飞书/Feishu/Lark/Larksuite operations (messages, mail, docs, Sheets/Base/多维表格, calendar/日程, tasks), including cross-service identity and permissions. Not merely because text contains a Feishu/Lark URL, or when the user selected another available interface.
  • 90openakita/skills@feishu-cli
    Feishu/Lark CLI - official open-source CLI tool from Feishu for AI Agents. Provides 200+ commands across 12 business domains: IM, Docs, Sheets, Base (Bitable), Calendar, Video Meeting, Mail, Tasks, Wiki, Drive, Contacts, Search. Supports both user identity and bot identity…
  • 100feishu
    Read and write Feishu (飞书) docs, sheets, Base (bitable), Drive files, calendar events, tasks, wiki, and IM messages via the Feishu Open Platform REST API. Use when the user mentions 飞书 / Feishu / Lark, a Feishu document or sheet link, their Feishu calendar, or wants to send a Feishu message.
  • 95lark-cli
    Lark/Feishu workspace operations through the `lark-cli` tool — calendar and meeting rooms, docs, sheets, Base (多维表格), wiki, drive, mail, IM messages, tasks, OKR, approvals, minutes, video conferences, whiteboards, slides, contacts, attendance, and real-time events. Use whenever…
  • 95lark-cli
    Use when the user wants to configure or log in to Lark/Feishu, check identity, or manage permissions; read, query, search, send, reply to, or forward IM messages and chat history, download chat files, or manage group chats; list, view, search, create, or edit cloud docs/files,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.