feishu-drive▌
m1heng/clawdbot-feishu · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Feishu cloud storage file management with folder browsing, file operations, and token-based access.
- ›Supports five core actions: list folder contents, get file info, create folders, move files, and delete files
- ›Handles eight file types including documents, spreadsheets, multi-dimensional tables, mind maps, and uploaded files
- ›Requires folder or file tokens extracted from Feishu URLs; bots can only access shared folders, not root directory
- ›Two permission levels available: full access
Feishu Drive Tool
Single tool feishu_drive for cloud storage operations.
Token Extraction
From URL https://xxx.feishu.cn/drive/folder/ABC123 → folder_token = ABC123
Actions
List Folder Contents
{ "action": "list" }
Root directory (no folder_token).
{ "action": "list", "folder_token": "fldcnXXX" }
Returns: files with token, name, type, url, timestamps.
Get File Info
{ "action": "info", "file_token": "ABC123", "type": "docx" }
Searches for the file in the root directory. Note: file must be in root or use list to browse folders first.
type: doc, docx, sheet, bitable, folder, file, mindnote, shortcut
Create Folder
{ "action": "create_folder", "name": "New Folder" }
In parent folder:
{ "action": "create_folder", "name": "New Folder", "folder_token": "fldcnXXX" }
Move File
{ "action": "move", "file_token": "ABC123", "type": "docx", "folder_token": "fldcnXXX" }
Delete File
{ "action": "delete", "file_token": "ABC123", "type": "docx" }
File Types
| Type | Description |
|---|---|
doc |
Old format document |
docx |
New format document |
sheet |
Spreadsheet |
bitable |
Multi-dimensional table |
folder |
Folder |
file |
Uploaded file |
mindnote |
Mind map |
shortcut |
Shortcut |
Configuration
channels:
feishu:
tools:
drive: true # default: true
Permissions
drive:drive- Full access (create, move, delete)drive:drive:readonly- Read only (list, info)
Known Limitations
- Bots have no root folder: Feishu bots use
tenant_access_tokenand don't have their own "My Space". The root folder concept only exists for user accounts. This means:create_folderwithoutfolder_tokenwill fail (400 error)- Bot can only access files/folders that have been shared with it
- Workaround: User must first create a folder manually and share it with the bot, then bot can create subfolders inside it
How to use feishu-drive on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add feishu-drive
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches feishu-drive from GitHub repository m1heng/clawdbot-feishu and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate feishu-drive. Access the skill through slash commands (e.g., /feishu-drive) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★38 reviews- ★★★★★Omar Harris· Dec 12, 2024
feishu-drive has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Diya Brown· Dec 4, 2024
We added feishu-drive from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Jin Lopez· Nov 23, 2024
Solid pick for teams standardizing on skills: feishu-drive is focused, and the summary matches what you get after install.
- ★★★★★Xiao Anderson· Nov 3, 2024
feishu-drive fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Ira Iyer· Oct 22, 2024
We added feishu-drive from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Lucas Anderson· Oct 14, 2024
feishu-drive has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Sakshi Patil· Sep 21, 2024
feishu-drive has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Kwame Desai· Sep 17, 2024
feishu-drive has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Ren Khan· Sep 5, 2024
Keeps context tight: feishu-drive is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Sakura Khan· Aug 24, 2024
feishu-drive is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 38