feishu-cli-storage

Original🇨🇳 Chinese
Translated

Unified entry for Feishu Cloud Space, covering enhanced Drive upload/download and asynchronous import/export, basic file/media operations, wiki knowledge base node and space management, document comments, collaborators and public permissions. This Skill must be used when users mention cloud disk files, folders, large file chunking or resumable upload/download, asynchronous tasks, directory mirroring, knowledge bases, wiki, materials, comments, sharing permissions, collaborators, public links, sharing passwords, transfer of ownership or permission applications. Wiki falls under this Skill only when managing spaces, node structures or members; it is explicitly prohibited to use it to read or summarize Wiki/document content—use feishu-cli-docs for content. For meeting recordings, Minutes and verbatim transcripts, use feishu-cli-meetings; use feishu-cli-platform for search.

3installs
Added on

NPX Install

npx skill4agent add riba2534/feishu-cli feishu-cli-storage

SKILL.md Content (Chinese)

View Translation Comparison →

Feishu Cloud Space

After loading the workflow, resolve the relative paths of
references/
,
scripts/
,
templates/
,
examples/
according to the directory where this
workflow.md
is located; use the resolved actual path when executing scripts, do not rely on the current shell directory.

Routing

IntentFile to Read
Large files, resumable upload/download, asynchronous import/export, mirroring, Drive search
references/workflows/drive/workflow.md
Basic file CRUD, versions, metadata, material upload/download
references/workflows/file-media/workflow.md
Wiki spaces, nodes, members, recursive export
references/workflows/wiki/workflow.md
Comments, replies, resolve and unresolve
references/workflows/comment/workflow.md
Collaborators, public permissions, passwords, transfer of ownership
references/workflows/perm/workflow.md

Execution Rules

  1. Prioritize file/media for basic file operations; use drive when chunking, resume, mirroring or asynchronous tasks are required.
  2. High-risk operations such as deletion, movement, overwriting, transfer of ownership and deletion of knowledge spaces require confirming the target first and using the confirmation parameters provided by the command.
  3. Comments usually require a User Token; the perm command group only uses App identity (no user-token parameter), only
    drive apply-permission
    requires a User Token. Follow the workflow and actual help documentation.
  4. Wiki node tokens cannot be mixed with regular document/file tokens.