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 336 copies of these same skills sitting in other people's repositories — counted once here, not 336 times.
3 457 unique 510 authors 2 017 updated this month 293 from vendors
Apply structured decision analysis using decision matrices, decision trees, expected value, and multi-criteria decision analysis (MCDA). Use this skill when the user faces a complex decision with multiple options and criteria, needs to compare alternatives objectively, quantify risk vs reward, or facilitate group decisions — even if they say 'which option should we choose', 'help me decide', 'how do we compare these options', or 'what's the expected outcome'.
Apply a latticework of mental models from multiple disciplines to improve decision quality. Use this skill when the user needs to think more clearly, avoid cognitive blind spots, apply cross-disciplinary reasoning, or evaluate a complex decision from multiple angles — even if they say 'how should I think about this', 'what am I missing', 'give me a different perspective', or 'what frameworks apply here'.
Conduct scenario planning to prepare for multiple plausible futures using driving forces, uncertainty axes, and the 2x2 scenario matrix. Use this skill when the user faces high uncertainty, needs to stress-test a strategy against different futures, or prepare contingency plans — even if they say 'what if things go wrong', 'what could the future look like', 'how do we prepare for uncertainty', or 'stress-test our strategy'.
Design production plans using MPS (Master Production Schedule), MRP (Material Requirements Planning), and capacity planning. Use this skill when the user needs to schedule production, plan material procurement, balance capacity with demand, or optimize production sequencing — even if they say 'we can't keep up with orders', 'when should we order materials', 'production scheduling', or 'how do we plan for next quarter's demand'.
Build and manage content calendars for multi-platform content marketing including editorial planning, content type allocation, and team workflow. Use this skill when the user needs to plan content across channels, coordinate a content team, maintain publishing consistency, or align content with business goals — even if they say 'we post randomly', 'plan our content for next month', 'content strategy', or 'what should we post this week'.
Digital-transformation execution playbook: maturity assessment, transformation roadmap, Operating Model redesign, PMO and transformation governance, data/AI platform deployment, process digitization, organizational agility, digital talent, and change management. Use for DX roadmap design, transformation governance (CDO/PMO/Steering Committee), data/AI/cloud platform planning, ERP or core-system upgrade, traditional-industry digitization, or DX organizational resistance. Triggers: 『DX 從哪開始』『數位長』『資料平台』『AI 落地』『傳產數位化』『ERP 要不要換』『轉型辦公室』『員工不配合數位化』『Operating Model』『敏捷轉型』『PMO』. For Taiwan EMBA info-management/DX/strategy/operations/change courses. Focuses on execution; theory layer: use Asgard `grad-digital-transformation`, `grad-sociotechnical`, `grad-tam-utaut`.
Leadership-style decision framework combining transformational, transactional, servant, situational, and authentic leadership into a situation-based decision tree. Use for diagnosing leadership challenges, succession planning, change management, crisis response, taking over a new team, or generational-gap issues. Triggers: 『該用什麼領導風格』『怎麼帶這個團隊』『接班交棒』『危機領導』『年輕員工不吃這一套』『威權還是授權』『轉型領導』『僕人領導』『情境領導』『真誠領導』. For Taiwan EMBA leadership courses (台大／政大／師大), executive self-diagnosis, and succession-leadership style. 9-box/人才盤點/繼任規劃工具: use `ops-talent-strategy`.
Design and implement OKR (Objectives and Key Results) for goal-setting and strategic alignment across organizational levels. Use this skill when the user needs to set team or company goals, align departments to strategy, track quarterly progress, or transition from KPI to OKR systems — even if they say 'set our quarterly goals', 'how does OKR work', 'align team goals with company vision', or 'our goals feel disconnected'.
Strategic talent-management toolkit integrating 9-box grid (performance × potential), succession planning, competency models, and talent review into one operational flow. Use for key-position-risk diagnosis, succession pipeline design, family-business second-generation grooming, annual talent review, competency/promotion systems, or post-M&A talent retention. Triggers: 『誰來接班』『關鍵職缺斷鏈』『高潛人才』『績效考核跟晉升脫節』『家族二代怎麼養』『留才方案』『9-box』『繼任規劃』『職能模型』『人才盤點』. For Taiwan EMBA strategic-HR/OB/family-business courses (政大／成大). Algorithmic HR tools: use Asgard `algo-hr-compensation`, `algo-hr-matching`, `algo-hr-turnover`.
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: \"What GitNexus tools are available?\", \"How do I use GitNexus?\
Design in a project using Maestro before implementation: use for brainstorm, plan, PRD synthesis, grilling/stress-test, domain model, deepening candidate, wording, workflow, skill/harness, card/task/feature, architecture, UX, or agent-process decisions.
Guides Qdrant scaling decisions. Use when someone asks 'how many nodes do I need', 'data doesn't fit on one node', 'need more throughput', 'cluster is slow', 'too many tenants', 'vertical or horizontal', 'how to shard', or 'need to add capacity'.
Guides Qdrant data volume scaling decisions. Use when someone asks 'data doesn't fit on one node', 'too much data', 'need more storage', 'vertical or horizontal scaling', 'tenant scaling', 'time window rotation', or 'data growth exceeds capacity'.
Guides Qdrant vertical scaling decisions. Use when someone asks 'how to scale up a node', 'need more RAM', 'upgrade node size', 'vertical scaling', 'resize cluster', 'scale up vs scale out', or when memory/CPU is insufficient on current nodes. Also use when someone wants to avoid the complexity of horizontal scaling.
Orchestrate iterative visual style searches with branch prompts, decision graphs, feedback loops, and final direction selection.
Use when needing strategic project analysis from multiple independent expert perspectives. Triggers on business decisions, growth strategy, product direction, competitive analysis, or any situation where diverse C-level opinions reduce blind spots
>- Use when capturing ONE new idea the user voices and wants recorded — "save this idea", (one folder per idea) in your ideas repo, dedups against an index, optionally mirrors to a (use a dedicated extraction skill) and NOT for dated work tasks (use an issue tracker / the
Проводит структурированный сеанс дивергенции вокруг конкретной продуктовой проблемы или возможности. Встроены SCAMPER (7 ракурсов), 5 Whys для поиска корневой причины, кросс-доменное вдохновение, ограничивающие инновации, обратный брейншторм и матрица Impact/Effort для отбора. На выходе — ≥10 идей с детально проработанным Top-3. User-invoked only — do NOT auto-trigger. Triggers on /pm-brainstorm, "идеи для продукта", "продуктовый брейншторм", "дивергенция идей", "How Might We", "SCAMPER", "product brainstorm", "feature ideas".
Use when ranking a list of requirements, features, or backlog items using RICE / ICE / MoSCoW / Kano. Built-in decision tree picks the right framework based on data availability and decision context. Output is a transparent matrix, 2×2 Impact/Effort quadrant, and a Sprint allocation proposal. User-invoked only — do NOT auto-trigger. Triggers on "/pm-prioritize", "/prioritize", "приоритизация", "ранжируй бэклог", "RICE-анализ", "prioritize requirements", "RICE", "ICE", "MoSCoW", "Kano", "rank backlog".
Use when auditing a product, business, or project ecosystem — analyzing data sources, decision loops, bottlenecks, and implementation contours. Triggers on "аудит продукта", "product audit", "data audit", "аудит данных", "аудит бизнеса", "проанализируй экосистему", "аудит систем".
Use when setting up a new project for AI-agent-driven management, generating OKR, connecting GitHub as a command center, or when user says "init project", "настрой проект", "set up my project", "initialize", "okr setup", "оформи okr". First skill in the Personal Corp framework.
Turn the current conversation into a PRD file in the project folder — no interview, just synthesis of what you've already discussed.
Use when transitioning from retro to weekly plan, prioritizing backlog, choosing outcomes for the week, or when user says "план на неделю", "планирование", "W13 plan", "outcomes", "приоритизация". Runs after weekly-retro skill.
>- Use when Codex needs Chinese-language Verilog or RTL design, existing-RTL analysis, verify-repair planning, controlled improvement planning, semantic comparison, debugging, troubleshooting, independent static lint, self-checking testbench scaffolds, or ASIC-quality review for a Verilog-target design, including synthesizable Verilog-2001 RTL, local or remote Vivado/xsim validation, artifact extraction, and workflow trace diagnosis.
JeecgBoot 系统主数据查询与管理。Use when user asks to query/create/manage system master data, or says "查询角色", "查询用户", "查询部门", "查询字典", "创建字典", "创建角色", "查岗位", "查职务", "查租户", "查数据源", "查定时任务", "系统主数据", "query roles", "query users", "query depts", "create dict", "create role", "master data". Also triggers when other skills (desform, bpmn, codegen) need to look up or create roles, users, departments, dictionaries, or positions as dependencies — follows "先查后建" (query-first-create-later) principle.
> Create or update an evidence-backed living Product Requirements Document (PRD) and, when useful, linked context and phase execution files under tasks/. Use for feature planning, implementation scoping, autonomous agent work, or checked-off PRDs that must be validated, reviewed, and revised during this out, update the prd, create an execution plan.
Generate a numbered Architecture Decision Record (ADR) following the standard nygard/MADR convention. Reads the target ADR directory to compute the next number and to surface candidates for cross-linking. Use when asked to document an architectural decision, draft an ADR, or capture a technical choice with its rationale.
Jacky Motion 2.0 的独立 SRT 自动录屏版。把中文口播稿与对应 .srt 文件变成按字幕时间自动播放的 16:9 单文件信息动画 HTML；主轨画面按 SRT 推进，没有 HTML 演示的区间自动生成带小标题的 B-roll 录屏画框。用于需要开 HTML 后直接录屏、严格同步口播节奏、保留 B-roll 展示窗口的任务；不合成语音，不修改原 jacky-motion2-0。
Load automatically when planning, researching, or implementing ANY Medusa backend features (custom modules, API routes, workflows, data models, module links, business logic). REQUIRED for all Medusa backend work in ALL modes (planning, implementation, exploration). Contains architectural patterns, best practices, and critical rules that MCP servers don't provide.
> reviewed spec → dependency-graphed task board → safe-wave TDD execution → verification → converge. Handles features, bugs, refactors, greenfield projects, planning breakdowns, and migrations. Triggers on "absolute work", "build this end-to-end", "plan and build", "break this into tasks", "grill me on this plan", "pick up this ticket", "run this migration".
> Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md.
Interview employees to identify recurring daily work, office workflows, and repetitive tasks that can be automated, co-piloted, or supported by AI. Use when the user wants to find what AI can take off their plate, map available tools such as ChatGPT/OpenAI, Claude, Microsoft Copilot, Excel or PowerPoint add-ins, Google Workspace, no-code/RPA tools, coding agents, or internal automation platforms, and write tool-aware specs with fallback paths.
Automate 7-phase feature development with specialized agents (code-explorer, code-architect, code-reviewer). Use for multi-file features, architectural decisions, or encountering ambiguous requirements, integration patterns, design approach errors.
Automate ML workflows with Airflow, Kubeflow, MLflow. Use for reproducible pipelines, retraining schedules, MLOps, or encountering task failures, dependency errors, experiment tracking issues.
Consult external AIs (Gemini 2.5 Pro, OpenAI Codex, Claude) for second opinions. Use for debugging failures, architectural decisions, security validation, or need fresh perspective with synthesis.
Systematic step-by-step reasoning with revision and branching. Use for complex problems, multi-stage analysis, design planning, problem decomposition, or encountering unclear scope, alternative approaches needed, revision requirements.
Creates detailed technical specifications for software projects covering requirements, architecture, APIs, and testing strategies. Use when planning features, documenting system design, or creating architecture decision records.
Orchestrate a MULTI-PHASE, dependent, or resumable run over many cc-fleet PROVIDER subagents from a JS script, off the main context (`cc-fleet workflow`). Use for fan-out→barrier→synthesis, per-item pipelines, loop-until-dry, or a run that must survive a kill and `--resume` from its journal. Trigger ONLY to run a cc-fleet provider workflow. NOT a flat fan-out of independent tasks (that is /cc-fleet:subagent — cheaper, no script); NOT trivial single-shot work; NOT for editing or researching cc-fleet's own workflow code.
The WOZCODE knowledge base behind the /woz review reviewer. Subcommands — `tune` (end-to-end reviewer tuning), `backtest` (tuning building blocks), `architecture-doc-fetch` (fetch woz/architecture.md from the KB), `cross-repo` (cross-repo planning brief), and knowledge-base ops (`status`, `query`, `note`, `suppress`, `boost`, `ingest`, `refresh`, `ops`).
Configure Cobbler model routes and external-agent preferences for this checkout. Use when the user types /setup-cobbler, asks to set up Cobbler model routes, onboard models, or update which tools handle planning/implement/review in Claude Code.
Rule-based design systems, constraint satisfaction, space planning algorithms, automated layout generation, drawing automation, code compliance checking, and computational workflows for AEC design automation
File format encyclopedia, data exchange strategies, API integration patterns, Grasshopper-to-Revit pipelines, Rhino.Inside workflows, Speckle data streams, and schema mapping for AEC computational design
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
A skill that blends the wisdom of top industry experts, ensures token-efficient PRDs, and organizes outputs in a clear folder structure.
Use when starting a new project, onboarding to an existing product, or setting up a documentation ecosystem for any initiative. Scaffolds the standard document set, folder structure, project memory, and doc-sync config. Works for software products, consulting engagements, platform implementations, and governance programs.
Use this skill when users request new features, enhancements, bug fixes, or any work that needs planning. Creates structured task files and PRDs (Product Requirements Documents) before implementation. Activates for "I want to add X", "implement Y", "create a task for Z", "plan this feature", or any feature request.
Use at the start of any task to route between Superpowers skills and GSD commands based on project state, task scope, and context signals. Fires before other skills when both systems are installed.
Auto-generate a slim CLAUDE.local.md from brain DB. Preserves manual behavior rules. Produces ~1,200 token auto-generated context section with key people, systems, decisions, and project status.