deepbot
Reduces friction for teams running on Feishu by embedding AI assistance directly into existing workflows without context-switching or additional tools.
DeepBot is a system-level AI assistant built for both personal productivity and enterprise workflows — one-click setup, seamless experience, and native Feishu integration.
- Auto-generate meeting summaries from Feishu chat threads
- Draft responses to common document review requests
- Extract and organize action items from conversations
Reduces friction for teams running on Feishu by embedding AI assistance directly into existing workflows without context-switching or additional tools. Handles routine tasks across personal and enterprise contexts from a single interface.
Teams already invested in Feishu (Lark) who need AI-powered automation for documents, messages, and task management without adding external SaaS dependencies.
https://github.com/kevinluosl/deepbot
By kevinluosl
How to Get It
claude plugins install kevinluosl/deepbot
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me auto-generate meeting summaries from Feishu chat threads
Trust Signals Auto-scanned
Community Pulse Active
Discussed on Hacker News, Reddit
- Am I the only one left who used deepbot and..where did it go? — Reddit · 13 pts
- Deepbots 1.0 release: Reinforcement Learning in Webots — Reddit · 12 pts
- My deepbot gets stuck like this, how to fix it? — Reddit · 3 pts
3 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 2,270 GitHub stars; 1 contributors; last commit 87d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
- Single maintainer. Consider the risk if this person stops maintaining the project.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 2,270 GitHub stars; 1 contributors; last commit 87d ago; license MIT.