Skills
96,981 packaged capabilities and playbooks for agents. Install any of them with one command.
Productivity
Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.
When you want to capture into, compile, query, lint, or connect your personal Second Brain. Wraps the Karpathy LLM Wiki schema (Obsidian or any markdown vault) — raw/ (unprocessed sources), wiki/ (AI-compiled interlinked topic pages), outputs/ (generated artifacts). Vault defaults to ${SECOND_BRAIN_VAULT:-$HOME/Documents/SecondBrain}/. Six modes — capture (drop something into raw/), compile (process unprocessed raw files into wiki pages, update INDEX.md), query (answer a question from the wiki, save to outputs/), lint (orphans / contradictions / stale / unprocessed raw / topic gaps), connect (suggest new wikilinks between pages), search (quick lookup). Triggers on "/second-brain," "/sb," "capture this," "save this to my brain," "compile the wiki," "process raw notes," "query my wiki," "ask my brain," "lint the wiki," "find connections," "search my notes." Complements deep-research (external corpus) — this is the internal corpus. Team knowledge goes to company-brain, not here.
Communications-domain literature review with Claude-style knowledge-base-first retrieval. Use when the task is about communications, wireless, networking, satellite/NTN, Wi-Fi, cellular, transport protocols, congestion control, routing, scheduling, MAC/PHY, rate adaptation, channel estimation, beamforming, or communication-system research and the user wants papers, related work, a survey, or a landscape summary.
Find and read academic papers (S2 + arXiv). Disambiguate ambiguous queries, search by keyword + citation graph + recommendations + snippets, judge relevance against an authored rubric, and read with L1/L2/L3 strategy. Trigger phrases: find papers, search papers, related work, citation analysis, recent advances, read this paper, baseline with code. Do NOT use for: survey reports (research-survey), idea generation (research-ideation), Related Work sections (paper-writing).
Use when running, diagnosing, or designing internal business operations—process documentation, vendor SLAs, capacity planning, internal comms, SOP/runbook authoring, or procurement spend. Triggers on “BizOps review,” “where's the bottleneck,” “vendor health,” “internal SOP,” “all-hands deck,” “spend categorization,” “capacity for Q3,” and “process mapping.” Forks context to one of six BizOps sub-skills (process-mapper, vendor-management, capacity-planner, internal-comms, knowledge-ops, procurement-optimizer) and returns a digest. Distinct from business-growth (external sales motion) and c-level-advisor (strategic, not operational).
Your launch lead. Builds a dated, step-by-step launch plan: a cheap real-world test first (a waitlist, a pre-sale or a pop-up with a real price, so real buyers confirm what the simulated panel said), then the countdown to opening day with owners and deadlines, the launch-day run sheet, and the first 30 days of what to measure and what to change. Use when the user says "how do I launch", "launch plan", "when can I open", "launch checklist", "go live", or "soft open".
Searches across your Notion workspace, synthesizes findings from multiple pages, and creates comprehensive research documentation saved as new Notion pages. Turns scattered information into structured reports with proper citations and actionable insights.
Use when the user asks to create a feature, write a PRD or TRD, add user stories, write scenarios, create acceptance criteria, plan implementation, initialize product docs, set up product documentation, create, approve, amend, or validate a Product Constitution, run the Constitution Grill, create or maintain Product Vision, run a Vision Grill, or work anywhere in the product development lifecycle from project setup through implementation planning
Run a formal multi-perspective debate on one contested MEL/SRHR design decision: persona agents mapped to real specialist lenses research the call independently and blind, debate one round, then a decision-memo-shaped synthesis keeps agreements and genuine disagreements visible for Ane to decide on. Use when Ane cannot decide between named options and wants independent perspectives argued. Token-heavy by design: reserve for real decisions. Not for sharpening a design she already leans on (/grill-mel), net-new builds (brainstorming), or a plain options paper (/decision-memo), and never for building anything.
Your operations manager. Works out how the business actually runs on day one: suppliers and what they cost, who works when, the step-by-step routines for opening, serving or shipping and closing, the tools to run it, the licences and permits to check, and a risk register with what to do when each thing goes wrong. Feeds real costs back to the CFO. Use when the user says "how do I run this", "operations", "suppliers", "staffing", "SOPs", "what do I need to open", "permits", or "day one".
NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance/Innovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget/scope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.
Operate on Feishu cloud document (Docx / Wiki) content: read, create, and edit documents; insert or download image attachments; and operate on mind notes. Use when the user provides a document URL/token (including /docx/ or /wiki/ on doubao.com); route by URL path/token rather than domain. Route embedded document resources according to the unified rules in the read reference. Use lark-drive for standalone comment operations; use docs +fetch to read comments along with the document body. This skill does not handle spreadsheet or Base internal data.
Google News is a free news aggregator by Google that surfaces headlines from thousands of publishers worldwide. Use this skill to fetch top stories, topic feeds, location-specific news, and keyword searches via the public Google News RSS feeds. No API key or authentication is required.
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).
Captures and organizes chaotic brain dumps into a structured, actionable system with zero information loss. Use whenever the user says “capture this,” “brain dump,” “let me dump some ideas,” “I've got a bunch of thoughts,” “here's everything on my mind,” “idea dump,” “let me get this out of my head,” “I need to organize my thoughts,” “here's what I'm thinking,” or similar phrases about unloading a messy stream of ideas, tasks, thoughts, and plans to make them coherent. Also trigger when the user pastes or dictates a long, unstructured block of mixed ideas, even without an exact phrase. Designed for fast action, with no upfront intake. Output has four sections (Projects/Ideas, Tasks, Connections, How I Can Help) and ends with a directive question. Asks at most one clarifying question during organization when an item is genuinely ambiguous between a task and a project.
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.
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 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).
Use when producing any MEL/SRHR analytical deliverable (brief, evaluation design, indicator set, ToC, evidence review, data analysis) — especially under deadline pressure, on Opus/Sonnet/Haiku-class models, or when tempted to cite a source without opening it, skip a verification pass, or deliver in one draft. Also use when a specialist subagent prompt asks for "working discipline" or "five gates"
Shopping price comparison using Bright Data's web scraping infrastructure. Finds where a product is sold, for how much, and whether it's in stock — across Amazon, Walmart, eBay, Best Buy, Google Shopping, and any retailer URL — then ranks the offers into a single buy-recommendation table. Use this skill when the user wants to compare prices, find the cheapest place to buy something, do a price check, see "how much does X cost on Amazon vs Walmart", track an item's price, or decide where to buy a product. Handles product names, ASINs, and direct URLs, and is region-aware (country affects price, availability, and which retailers apply). This is consumer purchase-decision research — for analyzing a competitor's pricing *strategy*, use competitive-intel instead.
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.
Expert guide for the Gemini Notebook (formerly Google NotebookLM) CLI (`nlm`) and MCP server — interfaces for Gemini Notebook. Use this skill when users want to interact with Gemini Notebook programmatically, including: creating/managing notebooks, checking plan usage and quota windows, adding sources (URLs, YouTube, text, Google Drive), generating content (podcasts, reports, interactive reports, quizzes, flashcards, mind maps, slides, infographics, videos, data tables), conducting research, chatting with sources, or automating Gemini Notebook workflows. Triggers on mentions of "nlm", "notebooklm", "Gemini Notebook", "plan usage", "quota", "podcast generation", "audio overview", "interactive report", "lesson report", "refactor document", "critique draft", or any Gemini Notebook-related automation task
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/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.
Feishu cloud drive enhanced command group. Chunked large-file uploads (automatically split into 3 parts at ≥20MB), streaming downloads, asynchronous document exports (markdown quick path / sheet+bitable csv / sub-id / bounded polling + resume), asynchronous document imports, file/folder moves (automatic folder polling), rich-text comments (text/mention_user/link + wiki URL parsing + inline comments), generic asynchronous task queries, one-way local ↔ cloud drive mirroring (pull/push/status, SHA-256 content diff + --delete-* --yes double confirmation), and v2 doc_wiki/search flat-filter search (folder-tokens / space-ids / creator-ids / only-title). Use when the user requests "upload a large file," "download a cloud drive file," "export as pdf/markdown/xlsx," "import docx into cloud docs," "move a folder," "add a document comment," "@ someone in a document comment," "comment from a wiki link," "check asynchronous task status," "resume a drive task," "chunked upload," "cloud drive mirroring," "directory sync," "compare local files with cloud drive," "SHA comparison," "search documents by folder," "feishu drive," or "lark drive." This skill coexists with the older file/media/comment command group and offers enhanced capabilities (User Token support, asynchronous resume, rich-text comments); file/media remain available for basic scenarios.
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 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.
Fetch trending and hot-search news data from Toutiao (www.toutiao.com), covering popular Chinese content across politics, finance, social events, international news, technology, and entertainment. Outputs trending headlines, popularity scores, and links.
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.