Feishu Cloud Docs

Problem

After an LLM generates a report, summary, API note, or review record, teams often still need to copy the text into a Feishu cloud document, set collaborator permissions, and notify the right people. That handoff is easy to interrupt, and the result can remain in chat instead of becoming a shared workspace artifact. This skill targets the workflow of generated content, Feishu document creation, permission granting, and link delivery.

How It Works

The skill assumes a Feishu open-platform app with credentials such as app_id and app_secret, plus permissions for documents, drive, permission management, and bot messaging, including docs:doc, drive:file, drive:permission, and im:message:send_as_bot. When invoked, it normalizes the target content as plain text or Markdown, creates a Feishu cloud document through the API, attempts to grant the recipient full_access, edit, or view permission, and then sends the document link as a plain-text Feishu message. Recipient resolution can use a Feishu email address, Open ID, or User ID, and the permission path may fall back to owner transfer, link-based access, or collaborator permissions where allowed.

Boundaries

This is useful for archiving generated work and coordinating follow-up editing, but it does not create, audit, or publish the Feishu app. Documents created by the app belong to the app and are stored in the app cloud space. If automatic permission granting fails, the recipient may need to set the share link to editable within the organization manually. The message is a plain link, not a card, and the supported content is mainly plain text and basic Markdown.