smithery/openclaw

feishu-drive

Feishu cloud-storage and comment workflows. Activate when the user mentions cloud space, folders, Drive files, or document comments.

Installation

$ npx skills add smithery/openclaw --skill feishu-drive

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/openclaw · top by installs.

npx skills add smithery/openclaw

Browse all from smithery/openclaw

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,498 B
  • docs SUMMARY.md 114 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Feishu Drive

Use the single feishu_drive tool and its current action schema.

From https://example.feishu.cn/drive/folder/ABC123, use ABC123 as folder_token.

Files and folders

  • Start from a folder shared with the bot. Bot credentials normally have no usable personal root folder.
  • For paginated folder listings, keep the same foldertoken and pass the returned pagetoken until no continuation token remains.
  • Use info with the exact file token and type returned by Drive or wiki discovery.
  • Resolve the exact source and destination before moving or deleting. Confirm destructive deletes when the user's intent or target is unclear.
  • Create subfolders inside a shared folder; creating at the account root normally fails for bots.

Comments

  • Use listcomments, then listcommentreplies with the exact commentid to inspect a discussion.
  • Use addcomment for a document-level comment. Include blockid only when the user wants a comment on one known Docx block.
  • Use reply_comment for an existing comment thread.
  • Preserve the file type and pagination fields returned by the tool. The schema is authoritative for which file types each comment action accepts.

Only expose or forward file and comment contents needed for the user's request; shared Drive data may be private.