Skills
96,770 packaged capabilities and playbooks for agents. Install any of them with one command.
Productivity
Operate on Feishu Base: create tables, fields, records, and views; handle statistics, formulas/lookups, forms, dashboards, app mode (BaseApp/AppMode pages and components), Workspace directories, workflows, role permissions, and the template center (Base template categories, lists, and search). Use when encountering Base/multidimensional tables/bitable, BaseApp/AppMode, or /base/ or /app/ links. Do not use lark-apps for BaseApp; route file import/export to lark-drive and authentication/authorization to lark-shared.
Feishu cloud storage (Drive): manage Drive files and folders, including uploads/downloads, folder creation, copying/moving/deleting, viewing metadata, checking permission settings, comments/permissions/subscriptions, titles, versions, Feishu document security labels (secure labels), and local file imports. Use when users need to organize Drive folders, handle cloud storage resource URLs/tokens, identify link types/actual tokens/titles, or import Word/Markdown/Excel/CSV/PPTX/.base as docx/sheet/bitable/slides. Route doubao.com cloud storage URLs/tokens by resource path and token too; do not fall back to WebFetch. Not responsible for: editing document content (use lark-doc), spreadsheet/Base table data operations (use lark-sheets/lark-base), knowledge space node/member management (use lark-wiki), or native Markdown file read/write/patch/diff (use lark-markdown).
Feishu instant messaging: send and receive messages and manage group chats. Send and reply to messages, search chat history, manage group members, upload and download images and files, manage emoji reactions, send urgent notifications in-app/by SMS/by phone, send and handle Interactive Cards, and listen for card button callbacks (card.action.trigger). Use when users need to send messages, view or search chat history, download chat files, view group members, search groups, create group or topic chats, manage marker data, manage Feed pins (add/remove/search pinned conversations), manage tag data, or handle card callbacks.
Feishu Calendar: manage calendar events and meeting rooms. View/search events, create/update events, manage attendees, check availability and recommended time slots, and book meeting rooms. Use when users need to view schedules, create/modify meetings, or check/book meeting rooms. Not responsible for searching past video meeting records (use lark-meeting) or to-do tasks (use lark-task).
Lark Approval: query and handle approval pending/completed/instances, search approvable definitions, view definition details and initiate native approval instances. Use when users need to handle approval tasks, view approval instances, search or initiate approvals. Approval pending items are not Lark tasks; non-approval pending items use lark-task. Not responsible for creating approval definitions; third-party approval definitions do not use native submission.
Lark Wiki: manage knowledge spaces, space members, and document nodes. Create and query knowledge spaces, view and manage space members, manage node hierarchy, organize documents and shortcuts in the knowledge base. Use when users need to find or create documents, browse knowledge space structure, view or manage space members, or move or copy nodes. When users provide a doubao.com /wiki/ URL/token, use this skill directly without falling back to WebFetch due to domain name; routing is based on URL path pattern and token, not domain name. Not responsible for: uploading files to knowledge base nodes (use lark-drive), editing document/sheet/Base content (use lark-doc / lark-sheets / lark-base).
Feishu / Lark contacts: resolve a name/email to an open_id, or look up a name/department/email/contact details/personal status/signature by open_id; also search by keyword for bots/agents visible to the current user. Use when a user mentions a name and wants to message them or schedule something next, or has an open_id and wants specific information. Does not handle department tree traversal, listing employees by department, or organization charts; use the native OpenAPI for these.
Lark Tasks: manage tasks, checklists, and task agents. Create to-do tasks, view and update task status, split subtasks, organize task checklists, assign collaborators, upload task attachments, register or unregister task agents, update task agent homepage data, and write agent task logs. Use when you need to create to-do items, view task lists, track task progress, manage project checklists, assign tasks to others, upload attachment files for tasks, register/unregister task agents, update agent homepage data, or write task logs.
Lark Mail: Use when user mentions drafting emails, writing emails, drafts, sending/replying to/forwarding emails, reviewing emails, viewing emails, searching emails, email folders, email labels, email contacts, listening for new emails, email rules, etc.; use for mail/email intent only. Do not use for docs/sheets/calendar/auth setup/pure contact lookup/IM chat tasks.
Lark Whiteboard: query and edit whiteboards in Lark Cloud Documents. Supports exporting whiteboards as preview images, exporting raw node structures, and updating whiteboard content using multiple formats. Use this skill when users need to view whiteboard content, export whiteboard images, or edit whiteboards. Not responsible for: Lark Cloud Documents content editing (lark-doc), embedded spreadsheets/Base in documents (lark-sheets / lark-base).
Lark/Feishu real-time event listening / subscribing / consuming: stream events as NDJSON via `lark-cli event consume <EventKey>` (covers IM messages/reactions/chat changes, Approval status changes, Task updates, VC meeting started/joined/ended, Minutes generated, Whiteboard updated, etc.). Use for Lark bots, real-time message processing, long-running subscribers, and streaming webhook/push handlers. Supports `--max-events` / `--timeout` bounded runs and a stderr ready-marker contract—designed for AI agents running as subprocesses.
Native OpenAPI exploration for Feishu/Lark: discover native OpenAPI interfaces from official documentation that are not wrapped by CLI. Use when user needs cannot be met by existing lark-* skills or lark-cli registered commands and native Feishu OpenAPI lookup and invocation is required.
Meeting notes organization workflow: Consolidate meeting notes within a specified time range and generate structured reports. Use when users need to organize meeting notes, generate weekly meeting reports, or review meeting content over a period of time.
Lark OKR: manage objectives and key results. View and edit OKR cycles, objectives, key results, alignment relationships, quantified metrics, and progress records. Use when users need to view or create OKRs, manage objectives and key results, or view alignment relationships. Does not handle: to-do task management (lark-task), scheduling/meetings (lark-calendar), performance reviews.
Feishu Markdown: view, create, upload, edit, and compare native Markdown files in Feishu. Use when users need to operate on Feishu Markdown files or compare their remote versions with local drafts. Purely local Markdown file operations do not trigger this skill. Does not handle importing Markdown as Feishu online documents or cloud storage management such as file search, permissions, comments, moving, or deleting.
Use this skill when the user wants to send or fetch files through an Xdrop server from the terminal, asks to automate encrypted Xdrop share-link workflows, provides an Xdrop `/t/:transferId#k=...` link to download and decrypt locally, or needs Xdrop CLI flags such as `--quiet`, `--json`, `--expires-in`, `--output`, or `--api-url`, even if they do not explicitly mention the skill name.
Lark instant messaging: send and receive messages and manage group chats. Send and reply to messages, search chat history, manage group members, upload and download images and files (supports chunked download for large files), manage emoji reactions, send in-app/SMS/phone urgent notifications, send and handle Interactive Cards, listen to card button callbacks (card.action.trigger). Use when you need to send messages, view or search chat history, download files from chats, view group members, search groups, create group chats or topic groups, manage marker data, manage Feed pinning (add/remove/query pinned sessions), manage tag data, and handle card callbacks.
Lark Tasks: manage tasks, checklists, and task agents. Create to-do tasks, view and update task status, split subtasks, organize task checklists, assign collaborators, upload task attachments, register or unregister task agents, update task agent homepage data, and write agent task logs. Use when you need to create to-do items, view task lists, track task progress, manage project checklists, assign tasks to others, upload attachment files for tasks, register/unregister task agents, update agent homepage data, or write task logs.
Lark Calendar: manage calendar schedules and meeting rooms. View/search schedules, create/update schedules, manage attendees, check availability and suggest time slots, book meeting rooms. Use when users need to view schedules, create/modify meetings, and query/book meeting rooms. Not responsible for: querying past video conference records (see lark-vc), to-do tasks (see lark-task).
Lark contacts: resolve names or email addresses to open_id, or look up names, departments, email addresses, contact information, personal status, and signatures by open_id. Use when users mention a person's name for messaging or scheduling follow-ups, or when they have an open_id and want to look up specific information. Does not handle department tree traversal, employee listing by department, or organizational charts; use the native OpenAPI for those needs.
Lark Approval: query and handle approval pending/completed/instances, search approvable definitions, view definition details and initiate native approval instances. Use when users need to handle approval tasks, view approval instances, search or initiate approvals. Approval pending items are not Lark tasks; non-approval pending items use lark-task. Not responsible for creating approval definitions; third-party approval definitions do not use native submission.
Lark OKR: manage objectives and key results. View and edit OKR cycles, objectives, key results, alignment relationships, quantified metrics, and progress records. Use when users need to view or create OKRs, manage objectives and key results, or view alignment relationships. Does not handle: to-do task management (lark-task), scheduling/meetings (lark-calendar), performance reviews.
Lark Markdown: view, create, upload, edit and compare Markdown files. Use when users need to create or edit Markdown files, read, modify, apply partial patches or compare diffs. Does not handle importing Markdown into Lark docs, or cloud space management operations like file search, permissions, comments, moving and deleting.
See what your AI agent is doing, from anywhere. The agent keeps writing — logs, code, generated outputs, screenshots, artifacts. One command turns the folder into a live URL you (or a teammate) open in any browser to watch files evolve, edit in place, or comment — no sync, no zip, no account. Workspaces stay live 24 hours anonymously; one email claim keeps them permanent. Hosted on Cloudflare. Triggers on "show me what the agent is doing", "open the agent's folder", "share this folder", "give me a link", "hand off this workspace", or any ask to make an agent's local file state visible from another device or to another person.
Lark video meetings: query meeting records and artifacts (minutes/transcripts/Miaoji), search/upload/download/edit Miaoji, and have bots join meetings; query ongoing meetings and real-time meeting content (speaking/chat/shared documents), answer questions about meetings, and send in-meeting chat messages/reactions. Look up related information using meeting_id, meeting_no, event_id, note_id, minute_token, vc-node-id, or a Miaoji URL. Use lark-calendar for scheduling, availability, and room management.
Web search and content extraction with Tavily and Exa via inference.sh CLI. Apps: Tavily Search, Tavily Extract, Exa Search, Exa Answer, Exa Extract. Capabilities: AI-powered search, content extraction, direct answers, research. Use for: research, RAG pipelines, fact-checking, content aggregation, agents. Triggers: web search, tavily, exa, search api, content extraction, research, internet search, ai search, search assistant, web scraping, rag, perplexity alternative
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.
Web search and content extraction with Tavily and Exa via inference.sh CLI. Apps: Tavily Search, Tavily Extract, Exa Search, Exa Answer, Exa Extract. Capabilities: AI-powered search, content extraction, direct answers, research. Use for: research, RAG pipelines, fact-checking, content aggregation, agents. Triggers: web search, tavily, exa, search api, content extraction, research, internet search, ai search, search assistant, web scraping, rag, perplexity alternative
Browser automation for AI agents via inference.sh. Navigate web pages, interact with elements using @e refs, take screenshots, record video. Capabilities: web scraping, form filling, clicking, typing, drag-drop, file upload, JavaScript execution. Use for: web automation, data extraction, testing, agent browsing, research. Triggers: browser, web automation, scrape, navigate, click, fill form, screenshot, browse web, playwright, headless browser, web agent, surf internet, record video
Web search and content extraction with Tavily and Exa via inference.sh CLI. Apps: Tavily Search, Tavily Extract, Exa Search, Exa Answer, Exa Extract. Capabilities: AI-powered search, content extraction, direct answers, research. Use for: research, RAG pipelines, fact-checking, content aggregation, agents. Triggers: web search, tavily, exa, search api, content extraction, research, internet search, ai search, search assistant, web scraping, rag, perplexity alternative
This skill provides comprehensive instructions for interacting with the Notion API via REST calls. This skill should be used whenever the user asks to interact with Notion, including reading, creating, updating, or deleting pages, databases, blocks, comments, or any other Notion content. The skill covers authentication, all available endpoints, pagination, error handling, and best practices.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
Web search and content extraction with Tavily and Exa via inference.sh CLI. Apps: Tavily Search, Tavily Extract, Exa Search, Exa Answer, Exa Extract. Capabilities: AI-powered search, content extraction, direct answers, research. Use for: research, RAG pipelines, fact-checking, content aggregation, agents. Triggers: web search, tavily, exa, search api, content extraction, research, internet search, ai search, search assistant, web scraping, rag, perplexity alternative
Web search and content extraction with Tavily and Exa via inference.sh CLI. Apps: Tavily Search, Tavily Extract, Exa Search, Exa Answer, Exa Extract. Capabilities: AI-powered search, content extraction, direct answers, research. Use for: research, RAG pipelines, fact-checking, content aggregation, agents. Triggers: web search, tavily, exa, search api, content extraction, research, internet search, ai search, search assistant, web scraping, rag, perplexity alternative
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.