lark-markdown

markdown (v1)

CRITICAL, Before starting, you MUST use the Read tool to read ../lark-shared/SKILL.md, which contains information on authentication and permission handling.

Quick Decision

• If the user wants to upload or create a native .md file, use lark-cli markdown +create
• If the user wants to compare historical version differences of a native .md file, or compare a remote Markdown file with a local draft, use lark-cli markdown +diff
• If the user wants to read the content of a .md file in Drive, use lark-cli markdown +fetch
• If the user wants to perform local text replacement or regex replacement on a Markdown file, prioritize using lark-cli markdown +patch
• If the user wants to overwrite the content of a .md file in Drive, use lark-cli markdown +overwrite
• If the user needs to retrieve the historical version number of a Markdown file before comparing, downloading, or rolling back, first use lark-cli drive +version-history from lark-drive
• If the user wants to import a local Markdown file as a new online document (docx), do not use this skill; instead, use lark-cli drive +import --type docx from lark-drive
• If the user wants to perform rename, move, delete, search, permission, or comment operations on a Markdown file within the cloud space (cloud drive/cloud storage), do not stay in this skill; switch to lark-drive

Core Boundaries

• This skill handles Markdown stored as regular files in Drive, not docx documents
• Both --name and local --file filenames must explicitly include the .md extension; the shortcut will throw an error if this is not met
• --content supports:
  • Passing a string directly
  • @file to read content from a local file
  • - to read content from stdin
• The internal semantics of markdown +patch are: download the full Markdown, perform local replacement, and then overwrite the entire file via upload
• markdown +patch is not an atomic server-side patch; it is a local update capability orchestrated by the CLI
• markdown +patch currently only supports a single set of --pattern / --content
• The final content after markdown +patch replacement cannot be empty; if the entire Markdown becomes an empty string after replacement, the CLI will throw an error and will not upload an empty file
• --file only accepts local .md file paths

Shortcuts (Recommended for priority use)

Shortcuts are high-level wrappers for common operations (lark-cli markdown +<verb> [flags]). Use shortcuts whenever available.

References

• lark-shared, Authentication and global parameters
• lark-drive, Drive file management, importing docx, move/delete/search, etc.