Productivity Claude Skills
3 457 productivity skills from 510 authors. They keep notes, tasks, calendars and plans in order. Half of them fit into 1 851 tokens or less — that is what one costs your context window when the agent loads it. 479 ship runnable scripts rather than instructions alone. 51 of them cannot work without an MCP server, most often rube. We also found 364 copies of these same skills sitting in other people's repositories — counted once here, not 364 times.
3 457 unique 510 authors 6 updated this month 293 from vendors
> A tool for generating initial packed molecular configurations (XYZ format) from single-molecule structures by calculating box dimensions, writing input scripts, and executing Packmol. USE WHEN you need to randomly pack a specific number of molecules into a simulation box (defined by target density or fixed lengths) to create starting geometries for molecular dynamics or related computational chemistry workflows.
> Acts as a knowledge base providing environment checklists, directory/scratch management, and bash command templates. USE WHEN you need to guide the execution of Gaussian computational chemistry jobs (.gjf) on local or remote/HPC environments.
Manage Obsidian vault operations. Handles markdown formatting, YAML frontmatter, folder organization, internal linking, and vault-specific conventions. Use when creating, updating, or organizing Obsidian notes.
Generate a custom checklist for the current feature based on user requirements.
Execute the implementation planning workflow using the plan template to generate design artifacts.
Intelligent skill router that analyzes user requests and automatically dispatches to the most appropriate skill(s) or zen-mcp tools. Routes to zen-chat for Q&A, zen-thinkdeep for deep problem investigation, codex-code-reviewer for code quality, simple-gemini for standard docs/tests, deep-gemini for deep analysis, or plan-down for planning. Use this skill proactively to interpret all user requests and determine the optimal execution path.
Method clarity-driven planning workflow using zen-mcp tools (chat, planner, consensus). Phase 0 uses chat to judge if user provides clear implementation method. Four execution paths based on automation_mode × method clarity - Interactive/Automatic × Clear/Unclear. All paths converge at planner for task decomposition. Produces complete plan.md file. Use when user requests "create a plan", "generate plan.md", "use planner for planning", "help me with task decomposition", or similar planning tasks.
Match UI/UX interaction needs to proven SwiftUI animation patterns from curated open-source catalogs. Use when planning or building iOS/macOS screens where an interaction should feel alive - loaders, likes, toggles, card decks, reveals, shaders - or when asked which animation fits a moment. Recommends system-first restraint before custom motion.
Premium website pre-build gate for cinematic, editorial, Squarespace-polished, Raycast/Linear/Vercel-precise, or motion-heavy web work. Use before implementing or redesigning a homepage, landing page, portfolio, product site, agency/studio site, or high-polish web app when the user wants non-generic visual quality, strong scroll/motion choreography, strict content scope, or an award-level result. Produces a build-ready UI spec, source-trust decisions, motion storyboard, and QA gates before code.
First Principles Framework (FPF) — thinking amplifier. Use when user wants to think through a complex problem, architect a system, evaluate alternatives, decompose complexity, classify problems, define quality attributes, plan, apply an FPF pattern to a first useful result, decide under uncertainty, establish causality, reason about time and trends, describe or synthesize architecture, check model fit, recover project/process/case/system subjects, trace outside-use dependencies, distinguish relation kinds or occurrences, govern ontic/U-kind admission, publish multi-view artifacts, refresh SoTA packs, trace provenance, or improve pattern quality. Also triggers on: FPF, bounded contexts, SoTA packs, assurance calculus, decision theory, causal/temporal reasoning, architecture, modularity, transformation-flow networks, narrative rendering, structural adequacy, cultural evolution, quality gates, lexical discipline, FPF Parts A-I. Not for simple task planning, general philosophy, or Agile unrelated to FPF.
Agent-callable Dropbox tools — upload, organize, find, and share files and folders. Use when the user wants to manage Dropbox content (save, move, search, share, list, or read files), including requests that don't name Dropbox explicitly, e.g. "save this report to my cloud storage" or "share that folder with Sam".
Agent-callable Google Calendar tools — create, update, move, search, and delete events, manage calendars, check free/busy availability, resolve event colors, and manage calendar sharing. Use when the user mentions Google Calendar or wants to schedule, find, reschedule, or share events and calendars — including requests that do not name Google Calendar explicitly, e.g. "put a meeting on my calendar Tuesday 3pm" or "am I free Friday afternoon".
Agent-callable Microsoft Outlook tools — read and search mail, send/reply/forward, organize messages and folders, manage calendar events, and manage contacts. Use when the user mentions Outlook, Microsoft 365 mail/calendar/contacts, or wants to send, read, search, or organize email, schedule events, or look up contacts — even if they don't name Outlook explicitly.
Agent-callable Microsoft SharePoint tools — find sites and document libraries, browse, search, upload, move and share files, manage lists and list items, and author site pages. Use when the user mentions SharePoint or wants to work with SharePoint sites, files, folders, lists, or pages, even if they don't name SharePoint explicitly.
Agent-callable Trello tools — create and update cards, manage boards, lists, labels, checklists, and search. Use when the user mentions Trello or wants to create cards, move tasks, or manage boards, even if they do not name Trello explicitly.
Create, find, complete, and organize tasks and task lists in Microsoft To Do (Microsoft's to-do app), plus break tasks into checklist steps. Use when the user wants to capture a task, check their to-do list, mark something done, or manage their tasks/lists — even if they don't say "Microsoft To Do" explicitly (e.g. "add buy milk to my tasks", "what's on my to-do list", "mark that done").
Use when the user asks to audit what's wrong with a project, "make it right", "看看项目出了什么问题", "为什么用户的需求还没上线", "为什么没提交App Store", "为什么没新build", or wants a holistic state-of-the-project check covering unmerged branches, stalled PRs, failed GitHub Actions, stale builds, plan drift (TODOS.md / ROADMAP), unreleased commits, and log errors. Runs read-only investigation, presents a grouped checklist, fixes only after explicit user confirmation. Aware of the Cathier iOS app workflow (Xcode + fastlane + auto-merge @claude PRs from in-app feedback).
Implementation planning specialist. Use when the user requests a feature, refactor, or architectural change. Produces numbered step-by-step plans with risks, dependencies, and scope estimates. Never writes code.
| 触发词：「广告公司绩效」「广告外包绩效管理」「agency 绩效」「广告公司 KPI」「广告公司 OKR」
| 触发词：「AIGC」「AI 创作」「AI 绘画」「AI 作画」「AI 出图」
| Trigger this skill when the user works on implant dentistry — surgical placement and prosthetic restoration of osseointegrated dental implants; covers diagnosis & treatment planning, site preparation (bone augmentation, sinus elevation, soft-tissue grafting), implant placement (delayed / immediate / immediate-loading), provisionalization and final restoration (cement / screw retained, custom abutments, full-arch), digital workflow (CBCT planning, intra-oral scanning, guided surgery, CAD-CAM milled prosthetics), and long-term maintenance including peri-implantitis prevention and treatment; NOT general restorative dentistry, NOT orthodontics, NOT pediatric dentistry, NOT maxillofacial oncology / trauma reconstruction, NOT clear-aligner business. problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「种植牙」「种植」「口腔种植」「牙种植」「implant」
| Trigger this skill when the user works on WeChat private-domain operations — 微信生态(企微 + 个人号 + 公众号 + 视频号 + 小程序)的私域操盘 problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「私域」「私域运营」「私域操盘」「微信私域」「企业微信」
| Trigger this skill when the user works on Youth Mental Health Education problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「青少年心理」「心理健康教育」「校园心理」「学校心理辅导」「社交情感学习」
Brainstorms and debates approaches, then drives toward an actionable decision. Use whenever someone needs a thinking partner for a decision they're facing: 'discuss', 'debate', 'brainstorm', 'weigh options', 'tradeoffs', 'should I do X or Y', 'help me decide', 'I'm torn between', 'sanity check my thinking', or 'what do you think about'. The user must be asking for help reasoning through a choice — not asking to build, fix, evaluate, plan, or modify something (even if the topic involves this skill itself). Picks the right decision lens, surfaces tradeoffs and blind spots, pushes back when reasoning is genuinely weak, and never implements.
Answer questions about code, architecture, and technical decisions — no implementation. Trigger on questions asking 'why', 'what does this do', 'what is the purpose of', 'explain', 'what's the difference', 'compare', or 'what are the tradeoffs' — even when referencing specific files, code snippets, or inline code. The key signal is the user wants to UNDERSTAND something, not change it. Do NOT trigger for requests to build, fix, plan, review, research, or add/modify code.
Use when the user wants a written, reviewable plan or spec produced before coding starts. Triggers on: mapping out changes without implementing, thinking through risks of upgrades or migrations, evaluating approaches before committing to one, writing specs for team review, phasing work into stages, or any request that explicitly defers coding ('don't implement yet', 'before we build'). The distinguishing signal is that the user wants a plan artifact — not implementation, not a conversational answer. MUST activates inside Claude's native plan mode to have a better planning behavior.
Judge product usability and evidence quality. Use when running Persona-based walkthroughs on a built product, planning an expert heuristic review, defining evidence-backed success metrics, or checking quantitative claims without inventing measurements. Use lamina-research to plan or synthesize evidence collection and lamina-ux to design interaction behavior.
Frame product problems and decide what to build. Use when establishing business context, aligning actors with conflicting goals, discovering or prioritizing features, defining traceable requirements, comparing consequential tradeoffs, or recording a product decision. Use lamina-ux for interaction details and lamina-product-behavior for authoritative runtime rules.
ALWAYS START HERE for any LangChain, Deep Agents, or LangGraph agent building project. Required starting point before choosing other skills or writing any code. Covers framework selection (LangChain vs LangGraph vs Deep Agents), agent archetypes, dependency setup, and which skills to load next based on your decisions.
This skill should be used when the user asks about the "CAP theorem", "PACELC", a "consistency model", "eventual vs strong consistency", "read-your-writes", "causal consistency", "quorum" or "R+W>N", "consensus", "Raft / Paxos", "leader election", "consistent hashing", a "distributed transaction", "2PC", or "saga". Use it whenever a design has multiple copies of data or coordinating nodes and a decision hinges on what a reader is guaranteed to see during replication lag, a network partition, or a node failure — even if the user doesn't say "consistency".
This skill should be used when the user needs to "estimate QPS", "back-of-the-envelope" (BOTEC) numbers, "how much storage / bandwidth", "how many servers", "peak load", "capacity planning", or wants the standard latency / throughput / availability numbers to ground a design (latency table, QPS rates, powers of two, nines). Use it whenever a design decision hinges on scale — convert any "high traffic" / "huge data" phrase into concrete numbers before choosing components, even if the user doesn't say "estimate". Prefer it even for a quick "rough numbers" question (DAU × actions/day → QPS, storage per day/year, replication): it carries a calculator and the reference numbers, so the arithmetic and unit conversions are checked instead of done from memory.
This skill should be used when the user designs a "task scheduler", "job scheduler", "job queue", "cron at scale", "distributed cron", "delayed / scheduled / recurring tasks", a "worker pool", reaches for "Celery / Sidekiq / Airflow", or wrestles with "task leasing", visibility timeouts, job priorities, fairness, or duplicate task execution. Use it whenever work must run later, on a schedule, or be reliably leased to a pool of workers, even if the user doesn't say "scheduler". (For plain queue transport and delivery guarantees, that is `messaging-streaming`.)
> Optimize a skill by planning, exploring available tools, diagnosing failures, and implementing fixes via PR. Use this skill as soon as an optimization loop starts, especially on the first iteration when community tools or reference approaches should be explored before implementation.
Expert guidance on Webflow CMS architecture and best practices. Use when planning collections, setting up relationships, optimizing content structure, or troubleshooting CMS issues.
Comprehensive audit of a Webflow site including pages, CMS collections, health scoring, and actionable insights. Use for site analysis, migration planning, or understanding site structure.
Guide conversations through dynamic shifts between zoom levels (scale) and connecting/exploring (intent) to unlock creative breakthroughs and prevent rigid thinking. Helps enhance and develop biased, focused, diversified, dispersed states. Receives signals from writing assistant's pattern detection to diagnose cognitive states. Identifies structural gaps between idea clusters as spaces for innovation. Tracks temporal dwelling patterns and manages energy across personality modes. Uses playfulness for difficult transitions from chaos to clarity. Reads emotional feedback—inspiration signals continuation, exhaustion/frustration trigger transitions. Prevents obsessive loops through sustainable cycling through topical clusters and latent nodes. Maximum creative potential lives in gaps and dissipative states. Apply for complex analysis, when a user is stuck, breakthroughs, decision paralysis, group facilitation, breaking repetitive patterns, or when grammatical patterns reveal cognitive issues.
> An intelligent shopping research assistant that helps users find the best product to buy through systematic comparison, review analysis, and value assessment. Use this skill whenever the user wants to buy something, is comparing products, asks "what should I buy", "help me choose", "best X for Y", mentions shopping, purchasing decisions, product comparisons, or needs help deciding between options. Also trigger when users mention wanting to research a product category, check reviews, or find the best deal. This skill uses web search extensively to gather real product data, ratings, reviews, and prices.
| Turn insights, findings, or research into an actionable plan with deadlines and scheduled Telegram reminders. Collaboratively designs the plan with the user via AskUserQuestion, saves it to .plan/ in the project, sets up cron reminders via Telegram bot, and shows overdue/today tasks on session start. Use when asked to "make a plan", "actionize this", "turn this into tasks", "schedule this", "create deadlines", "track this", or "diagnose my planning". Invoke with "diagnose" argument to run planning pattern analysis (Phase 7). Proactively suggest when the user has completed research, brainstorming, or /office-hours and has a list of insights without concrete next steps. Proactively suggest "/actionize diagnose" when a plan has >30% deferred tasks.
Pull and stream US stock market data from Alpaca — REST snapshots/bars/trades/quotes, historical bars with timeframes and feeds (IEX vs SIP), the assets master list, market clock & calendar, news, and the real-time WebSocket stream. Use when building charts, quotes, price feeds, or asset metadata on Alpaca in any language.
|
Write Minecraft vanilla commands, NBT scripts, scoreboards, and complex execute chains for use in command blocks, chat, or .mcfunction files. Covers full execute subcommand reference (as/at/in/positioned/rotated/facing/anchored/if/unless/store/run), selector arguments with all filter options, scoreboard objectives and operations, NBT path syntax for entities/blocks/storage, schedule and forceload commands, tellraw/title JSON text components, bossbar, team management, item modification commands, attribute commands, particle/playsound effects, and RCON scripting. Targets Minecraft 1.21.x Java Edition. Use for command-only work; for full function/advancement/recipe systems use the minecraft-datapack skill instead.
Operate EssentialsX on Minecraft 1.21.x servers with safe, practical admin workflows. Covers module scope, install and version-alignment checks, Vault economy integration, kits/warps/homes/spawn operations, permissions patterns, moderation workflows (mute, jail, tempban), and common config pitfalls. Use when the task involves EssentialsX commands, config, permissions, economy, or moderation operations — not plugin development or general server deployment.
Create, generate, update, repair, trim, or split minimal AGENTS.md files for repository roots and confirmed nested modules using progressive disclosure. Use for missing, bloated, contradictory, or outdated agent instructions, monorepos, services, packages, module context, and portable agent guidance without assuming any fixed agent folder structure.
Build, fix, review, and validate adaptive or responsive Flutter UIs for mobile, tablet, desktop, web, large screens, foldables, and mixed input devices. Use when creating breakpoint-driven layouts, responsive navigation, adaptive dialogs/lists/grids, keyboard/mouse/touch behavior, window-size decisions with MediaQuery or LayoutBuilder, or Capability and Policy patterns for platform-specific behavior.
Interrogate a written engineering implementation brief before work starts. Use when a user brings a ticket, PRD, design note, or substantive engineering task brief and wants to begin implementation planning; force every fixed rubric element to be accounted, cite present/weak claims against the brief, surface gaps, solution-as-goal traps, contradictions, and questions, then emit an intent-level plan. Do not use for bare one-line requests, non-engineering artifacts, code diff review, bug fixing, or execution itself.
> Transforms any process description — however rough, incomplete, or disorganized — into a clear, delegatable Standard Operating Procedure (SOP). Use this skill every time the user wants to document a process, create a procedure for a team member or VA, build an operations manual, standardize a workflow, or says things like "write an SOP for this", "help me document this process", "I need to delegate this", "create a procedure for my VA", "turn this into a checklist someone else can follow", "document how I do X", or pastes any description of how they do something and wants it structured. Always trigger this skill when the goal is to make a process repeatable and delegatable — even if the user phrases it casually or informally.
Activates a brutally honest thinking partner mode that sharpens reasoning, surfaces blind spots, dismantles flawed logic, and forces concrete action planning. Use this skill every time the user wants honest feedback on a plan, decision, or idea — especially when they seem to be rationalizing, avoiding something, or stuck. Also trigger when the user says things like "be honest with me", "tell me what you really think", "am I thinking about this wrong", "what am I missing", "stress-test this", "play devil's advocate", "challenge my thinking", "I need brutal feedback", or pastes a plan, decision, or idea asking for feedback. Trigger even when the request is casual — if the user shares a plan and seems to want validation, this skill is what they actually need. Do NOT use for pure information requests with no decision or reasoning component.
Collaborative brainstorming partner for multi-session ideation projects. Use when the user wants to brainstorm, ideate, explore ideas, or think through problems—whether for SaaS products, software tools, book ideas, newsletter content, business strategies, or any creative/analytical challenge. Handles session continuity across days/weeks via versioned markdown documents. Includes brainstorming methods catalog and supports both connected (cross-project awareness) and clean-slate modes.