Skills
96,981 packaged capabilities and playbooks for agents. Install any of them with one command.
Productivity
Create, read, update, move, and manage kanban board feature files backed by markdown with YAML frontmatter. Use when working with kanban boards, task/feature tracking, `.devtool/features/` directories, feature files with status/priority frontmatter, or any project management tasks involving markdown-based kanban workflows.
Resume generation and optimization tool. Supports two modes: create a new resume from scratch (collecting information through structured dialogue), or optimize an existing resume (read and improve the existing resume). Outputs both HTML and PDF, with professional formatting and a strict limit of two pages. Supports resumes in Chinese and English. Trigger when users mention: generate a resume, write a resume, make a resume, resume creation, optimize a resume, edit a resume, resume styling, resume create, resume build, resume optimize, help me make a resume, resume layout, make a resume, change my resume, resume template, resume design. Also trigger when continuing from resume-match with an already optimized Markdown resume to generate HTML+PDF. Trigger even if the user only says “help me make a nice-looking resume” or “format my resume.”
/c-level-agents:execute [decision] — Generate a 90-day execution plan with weekly milestones, DRIs, and check-in cadence from an approved decision. Use when a logged decision needs to become an operating plan — e.g. turning an approved market-entry call into weekly milestones with DRIs.
/c-level-agents:cross-eval [memo] — Multi-model consensus on a board memo or strategy brief. Claude + Codex + Gemini cross-review with graceful degradation. Use when a high-stakes memo needs an independent sanity check before the boardroom — e.g. a bet-the-company pivot or fundraise terms.
Every Slack read your token can make, mirrored to local SQLite so your history outlives Slack's own retention wall. Trigger phrases: `search old slack messages`, `what did I miss in slack`, `which slack channels are dying`, `find unanswered slack threads`, `who is this slack user id`, `use slack-pp-cli`, `run slack`
Generate a professional, detailed, figure-rich LaTeX course note and final PDF from a Bilibili lecture, tutorial, or technical talk. Use when the user provides a Bilibili URL (BV number) and wants structured Chinese teaching notes that combine the video's title, chapters, diagrams, formulas, code, subtitle explanations, the original video cover on the front page, and a final synthesis chapter, with key frames extracted from the highest usable video resolution and inserted as figures, and where the final deliverable must include a rendered PDF. Falls back to Whisper speech-to-text when no CC subtitles are available.
Use when looking up journal impact factors (JCR IF), checking a journal's impact factor by name, comparing IF across journals, or answering questions about "影响因子" / "impact factor" / "IF". Triggers on "impact factor", "journal IF", "影响因子", "JCR", "IF score", "journal rank", "which journal has higher IF", "what is the IF of". PROACTIVELY USE when user mentions journal prestige, publication venue quality, or manuscript submission target evaluation.
Use when asked to "opportunity solution tree", "OST", "Teresa Torres", "map customer opportunities to outcomes", "structure discovery around opportunities", or "compare solutions for a customer need". Helps product teams connect outcomes to customer opportunities and test solutions with Opportunity Solution Trees (created by Teresa Torres).
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to “open a website”, “fill out a form”, “click a button”, “take a screenshot”, “scrape data from a page”, “test this web app”, “login to a site”, “automate browser actions”, or any task requiring programmatic web interaction.
Operate a BKD kanban board over its REST API. Use when the user wants to manage BKD projects, issue execution workflows, cron jobs, or execution capacity, including three-tier coordination with an event-driven L1, multiple cron-driven L2 workstreams, and L3 execution, multi-repo coordination across several git repos in one workspace directory (trigger phrases like "start BKD multi-repo coordination"), plus multi-subtask orchestration (trigger phrases like "use bkd to start coordination", "start BKD L1"), and the messages system that sends decisions and notifications to BKD's inbox (trigger phrases like "enable the messages system", "启用消息系统", "启用决策系统", "notify me when …", "通知我"). Requires a reachable BKD server ($BKD_URL).
Generate a pre-meeting prep brief in Claude Code. Researches participants, pulls vault context, builds agenda, surfaces sharp questions. Use when user says "prep for this meeting," "I have a call with," "meeting tomorrow with," or "prep brief for [name/company]."
Listen for one or more IMAP inboxes with the IDLE command, fetch unread email metadata plus text previews, and forward each message to OpenClaw webhooks. Use when tasks need near-real-time mailbox monitoring, multi-account inbox ingestion via environment variables, and automatic trigger delivery into OpenClaw automation
Generate a long-form Chinese interview-prep cheat sheet on a specific ML/LLM topic, with formulas and derivations, from-scratch PyTorch code, comparison tables, and 25 frequently asked interview questions (L1 essential / L2 advanced / L3 top labs). Use when the user asks for an interview cheat sheet, an X tutorial, help preparing for Y interview questions, an X quick reference, or a 600–1,000-line Chinese tutorial on a specific ML topic.
This skill should be used when configuring Make module parameters, assigning connections, mapping data between modules, setting up webhooks or data stores in modules, working with IML expressions, handling keys, or defining data structures for module inputs/outputs. Covers the practical HOW of module configuration — complementary to make-scenario-building which covers WHICH modules to use and WHY.
Use this by default for non-trivial multi-step work that needs persistent planning, progress tracking, or durable notes on disk. Trigger when a task will likely span multiple tool calls, research steps, verification loops, or enough context that the plan should not live only in transient chat memory.
Full-pipeline App Store opportunity research. Discovers underserved niches, analyzes competitor gaps, produces revenue-validated top-3 opportunity reports, writes MVP PRDs, and builds working prototypes on Rork (https://rork.com/?ref=frederik) — all automated through browser research.
Query and manage Google NotebookLM notebooks with persistent profile auth, source sync, batch/multi queries, and structured exports. Use when user asks to query NotebookLM, 'ask my notebook', shares NotebookLM notebook URLs, wants to list/create notebooks, manage sources, do bulk folder sync, dedupe, or audit exports
Turn messy daily-sync requests into one honest coordination-cadence packet: decide whether live-daily, async-daily, hybrid-daily, less-frequent syncs, or no recurring standup is justified, then pick the lightest standup mode that still catches blockers and handoffs. Use when the user needs a daily scrum, async check-in, board-walk, blocker-first sync, remote-team standup, launch- week cadence reset, or help fixing an overlong / low-signal standup. Route backlog planning to `task-planning`, sizing to `task-estimation`, retrospective process repair to `sprint-retrospective`, and incident-command work to debugging / launch-specific skills.
A skill for refining stock investment research questions. Turns user-provided stock names or tickers into structured eight-stage investment due diligence instructions. Clarifies investment style (value/growth/turnaround), holding period (short/medium/long term), risk tolerance, and research focus through questions, then generates structured research tasks that meet professional investment research standards. Use when users mention stock analysis, investment research, or stock due diligence.
Official Dailybot agent skill pack — report progress, check messages, send emails, announce agent status, complete check-ins, give kudos (to users or teams), resolve teams, run the full forms lifecycle (list, submit, update, transition between workflow states), author check-ins and forms from scratch (create/configure questions, workflow states, permissions, reminders, scheduling, AI settings, sharing), send/edit chat messages on the team's Slack/Teams/Discord/Google Chat (including report-style threads, sending as a user's identity, and interactive buttons with approval flows, workflow triggers, modals, and callbacks), open (or reuse) a Slack group DM with the bot and post a report to it, ask the Dailybot AI a question headlessly, browse/read/trigger the workspace (`me` / `org` / `user get`, kudos browsing, workflows), manage organization Labels (`dailybot label` CRUD + assign/batch on forms, check-ins, workflows) and private Featured stars, manage Plan (Beta — boards, backlog, sprint/kanban columns, owners, attachments, bulk with dry run, project updates, milestones, goals, open-org structure for non-guest members, agent-attributed work on a handed task with `task brief` — `dailybot plan tasks` for the workspace and `dailybot plan task` for one task), and manage per-repo API keys through `.dailybot/env.json` (pack baseline `dailybot-cli >= 3.9.0`; Plan needs `>= 3.25.0`). Routes to the right sub-skill based on intent. Use when the developer mentions Dailybot or wants to interact with their team
Use when asked to “working backwards”, “PR/FAQ”, “Amazon PR/FAQ”, “write a press release”, “define a new product”, or “write a customer-focused PRD”. Helps define products by starting with the customer problem and desired outcome before building. The Working Backwards process (developed at Amazon) forces clarity on customer value before committing engineering resources.
Turn raw ideas into one clear pre-planning concept artifact by choosing the right framing mode: problem framing, audience and value framing, concept shaping, game concept framing, or story packaging. Use when the user needs the next artifact before PRDs, sprint plans, launch execution, or game-production routing.
Your board of directors. Puts a business idea in front of a three-member board, each a sub-agent reading the idea through one published framework: the Offers lens (from Alex Hormozi's $100M Offers), the Monopoly lens (from Peter Thiel's Zero to One) and the Product lens (from Walter Isaacson's biography of Steve Jobs). Each member scores the idea, names the risks that would kill it and votes fund, fund with conditions, or pass. Use when the user says "test my business idea", "would this work", "pressure-test this", "what would a board say", "is this a good business", or starts the founder pack on a new idea.
Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.
/c-level-agents:freeze [decision] [days] — Lock a strategic decision for a cooldown period to prevent impulse reversal. Mirrors gstack's safety primitives for the business layer. Use when an irreversible decision was made under pressure — e.g. a layoff plan or multi-year contract — and deserves a cooling-off lock before execution.
Facilitate sprint retrospectives, milestone postmortems, or iteration reviews that turn completed work into a few owned process improvements instead of another stale template ritual. Use when the user needs a retrospective mode, remote or hybrid facilitation plan, action-item follow-through reset, or help reviewing what the team should change after a sprint, release, milestone, or rough delivery cycle. Also owns the retired `retro` name: run a retro, start/stop/continue, 4Ls, sailboat, action items with owners and deadlines, compact sprint summary with velocity vs commitment and carry-over. Route backlog planning to `task-planning`, sizing to `task-estimation`, daily coordination to `standup-meeting`, and deep incident forensics to debugging/incident-specific skills.
Interview the user in rounds about their plan, decision, or idea until the important unknowns surface, then start executing. Works in any domain, not just coding. Use when the user wants to clarify their thinking, stress-test an idea, or says things like: grill me, pick my brain, help me think this through, help me sort this out, poke holes in this, anything I'm missing, stress-test this, interview me.
Plug-in web search, X (Twitter) search, and page fetch for models without native web access. Use whenever the task needs current information, external facts, source links, posts from X, or the content of a specific URL, and the active model/harness has no native search or fetch tool. Runs the modsearch CLI to return structured JSON evidence. Also use when the user asks how to install or configure modsearch, or wants to switch engines or add a key
Manage Confluence documentation with downloads, uploads, conversions, and diagrams. Use when asked to “download Confluence pages”, “upload to Confluence”, “convert Wiki Markup”, “sync markdown to Confluence”, “create Confluence page”, or “handle Confluence images”.
Your business planner. Compiles everything the other founder skills wrote (the board's verdict, the competitors, the buyer panel, pricing, the offer, the CFO's numbers, marketing, brand, operations and the launch plan) into one business plan with a verdict at the top that is computed from the numbers, never written by hand: Profitable, Not yet (with the failing numbers) or Incomplete. Adds an executive summary and a one-page version for a partner, lender or investor. Use when the user says "write my business plan", "put it all together", "is it profitable", "give me the plan", or at the end of the founder pack.
/cs-onboard — Founder interview that populates ~/.claude/company-context.md using the canonical 7-dimension cs-onboard schema. The first command to run when starting with c-level-agents. Use when setting up the virtual C-suite for a new company, or when advisors lack company context — e.g. before a first /c-level-agents:boardroom or after a fundraise changes the numbers.
Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf. Team-scope sibling to second-brain — personal notes go there, not here. Modes — capture, compile (wiki pages + INDEX.md), query (trust-weighted, saved to outputs/), review (verify / deprecate / supersede stale captures), lint, connect, search. Structured raw dirs (people/, companies/, meetings/, sops/, decisions/, customer-language/, sales-objections/). Every capture stamps author, timestamp, and trust status. Optional sync from call transcripts, Slack/email exports, CRM. Vault at ${COMPANY_BRAIN_VAULT:-$HOME/Documents/CompanyBrain}/. Triggers on "/company-brain," "/cb," "capture this into the team brain," "log this meeting," "save this SOP," "compile the company wiki," "query the team brain," "what does the team know about X," "review the company brain," "lint the company brain," "who's the internal expert on X."
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.