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
Answer App Store release go/no-go questions and choose the next focused release skill. Use for readiness planning, first-submission blockers, release sequencing, or deciding whether to stage or submit; use appstore-review-readiness for concrete validate, submit, monitor, cancel, and repair commands.
Define, validate, run, resume, and audit repo-local `.asc/workflow.json` automations with current `asc workflow`, including safe release/TestFlight flows and step outputs.
Work productively in Tuist-generated Xcode workspaces. Use for `tuist generate`, generated workspace builds, focused generation, tags, buildable folders, and Xcode build/test commands after generation.
Use when designing or reviewing safe Grok Build hooks for linting, tests, formatting, notifications, command guards, lifecycle automation, or project hook trust decisions.
Use for clean architecture, modular monoliths, hexagonal boundaries, service boundaries, data flow, dependency direction, ADRs, or large feature planning.
Apply established brainstorming and ideation methodologies to game design problems, features, systems, UX flows, live-ops ideas, content concepts, and stuck team discussions. Use when the user wants a specific brainstorming method rather than generic ideation, or when you should choose and run a method such as SCAMPER, How Might We, Crazy 8s, Six Thinking Hats, Brainwriting 6-3-5, Worst Possible Idea, forced connections, Lotus Blossom, or a morphological matrix.
Extract 3 to 5 actionable design pillars from a game, feature, loop, or system based on what the design actually rewards and prioritizes. Use when a team can describe mechanics but cannot clearly articulate the principles those mechanics serve, when pillars are vague, generic, or contradictory, or when you need a sharper set of tradeoff-driven pillars that can guide decisions and cut features.
Evaluate game features, feature pitches, live-ops ideas, UX changes, economy changes, roadmap choices, retention initiatives, monetization initiatives, and ambiguous design problems using the GROW model: Goal, Reality, Options, Will. Use when a team needs structure, clearer decision-making, better option generation, explicit tradeoff analysis, or a concrete recommendation and next-step plan instead of circular discussion.
Audit a game, feature, progression loop, return-player experience, metagame layer, or session structure for density of goals, immediacy of goals, safe stopping points, and return triggers. Use when evaluating whether players can quickly find something meaningful to do, whether the game offers enough short-term, mid-term, and long-term goals, whether session lengths are flexible enough for real player schedules, or why a game feels aimless, overwhelming, or unable to fit into fragmented playtime.
Start from the ideal player-facing result and work backward to the design steps, systems, and decisions required to reach it. Use when a team knows the kind of experience it wants but not how to structure the path there, when redesigning a feature around a stronger destination, or when clarifying what must be true for a concept to feel successful.
Extract the ideal player persona and anti-persona for a game, feature, loop, or progression structure based on the design itself. Use when a team can describe mechanics but cannot clearly articulate who the design is truly for, which player motivations and tolerances it suits, which players it will alienate, or how audience fit should shape design decisions. Focus on behavioral and motivational personas first, and optionally add demographic or market-fit hypotheses when the user explicitly asks for that layer.
Design or audit prosocial experiences in session-based multiplayer games using a three-phase chapter model built around Setup, Little Loops, and Long Tail. Use when evaluating co-op games, team shooters, MOBAs, mission-based multiplayer, or other repeat-session formats; when planning how to prime trust before play, reinforce repeatable prosocial actions during play, and carry positive social momentum across sessions; or when a multiplayer game feels socially flat, hostile, forgettable, or unable to turn one good match into another.
Audit game design goals, feature objectives, OKRs, initiative aims, or any stated design intent against the SMART criteria adapted for game design. Use when a user shares a design goal, player experience target, retention goal, or feature aim and wants it evaluated or rewritten. Trigger on phrases like "audit my design goals", "is this a good design objective", "my feature goal is...", "we want players to feel...", "our aim for this feature is...", or whenever someone states what a design should achieve and it feels vague or unmeasurable. Also trigger when a design document contains aims or success criteria that need stress-testing. Even soft goals like "players should feel powerful" are valid — apply the framework and return both the audit and a rewritten version.
Help analyze recurring conflict patterns on software or game projects by identifying likely collaboration archetypes, behavior patterns, project risks, and practical response strategies. Use when someone describes a teammate, lead, founder, stakeholder, client, producer, or collaborator whose recurring behavior is creating friction, slowing decisions, damaging trust, or disrupting execution. Focus on observable behavior and project consequences, not clinical diagnosis, then suggest safer and more effective next moves.
Help a beginner or early-stage game team estimate the likely development time for a game concept based on scope, target milestone, current team, skill coverage, work model, and production constraints. Use when someone asks how long a game might take, whether their current team can hit a target date, what timeline range they should expect for a prototype, vertical slice, release, or live F2P project, or how missing roles and part-time availability change development time. Ask for missing information when concept, team, scope, or staffing assumptions are unclear, then provide a rough timeline range, main schedule drivers, hidden time sinks, and ways to shorten the path.
Generates a complete, polished HTML documentation page, a processing checklist, an AstroBin post JSON, a PixInsight process icon set (XPSM), AND a ready-to-paste PixInsight project Description field for a deep-sky object (DSO) astrophotography project. Use this skill whenever the user mentions astrophotography, a DSO name (NGC, IC, Messier, Sharpless, etc.), wants to document an imaging session, mentions PixInsight project documentation, wants to create an observation report, or asks to generate a page/document for a nebula, galaxy, cluster, or other deep-sky target. Triggers on phrases like "create doc for NGC XXXX", "generate DSO page", "document my session on", "make a PixInsight doc for", "astro documentation page", "pixinsight project description", "description field pixinsight", "processing checklist", "workflow checklist", "astrobin", "astrobin post", "astrobin upload", "process icons", "xpsm", "pixinsight icons". Always use this skill — not a generic HTML generator — when the subject is a deep-sky object.
Generate probability-weighted alternative options that challenge default thinking. Forces unconventional alternatives and exposes hidden assumptions behind the "obvious" choice. For decision-point analysis, NOT full design exploration. Triggers on "대안", "alternatives", "옵션 뽑아", "options", "어떤 방법이", "아이디어", "다른 방법", "선택지".
Prospective failure analysis using Gary Klein's pre-mortem technique. Assumes complete failure, works backward to identify risks, leading indicators, and circuit breakers. Counters optimism bias by forcing systematic exploration of failure modes before they materialize. Use for project plans, architecture decisions, technology adoption, business strategy, or feature launches. Triggers on "리스크", "위험", "실패하면", "swing-mortem", "뭐가 잘못될 수 있어", "risk", "what could go wrong", "걱정되는 점", "failure modes", "리스크 분석", "위험 분석".
Exposes Claude's reasoning chain as an auditable, decomposable artifact. Quick mode (default) gives assumption inventory + weakest-link in 2 stages. Full mode (--full) adds decision branching, confidence decomposition, and falsification conditions. Triggers on "왜 그렇게 생각해", "reasoning", "근거", "show your work", "어떻게 그 결론이", "trace", "판단 근거", "why do you think that".
Use this skill for any task involving Thai date formatting, Buddhist Era (พ.ศ.) ↔ Gregorian (ค.ศ.) year conversion, or Arabic ↔ Thai numeral conversion. Trigger whenever the user asks to: convert พ.ศ. to ค.ศ. or vice versa, format a date in Thai government / business / casual style, parse a Thai date string with full or abbreviated month names, or convert digits between 0123456789 and ๐๑๒๓๔๕๖๗๘๙. Also trigger for requests like "แปลง พ.ศ. เป็น ค.ศ.", "จัดรูปแบบวันที่ไทย", "วันที่แบบราชการ", "เปลี่ยนเป็นเลขไทย", or any variation involving Thai calendar dates.
Implements and customize Syncfusion .NET MAUI Calendar (SfCalendar) control. Use when implementing calendar functionality, date selection (single, multiple, range), or calendar views (month, year, decade, century). Covers date restrictions (min/max dates, EnablePastDates, SelectableDayPredicate), calendar customization, events (ViewChanged, SelectionChanged, Tapped), and header/footer customization.
Automates macOS Calendar via JXA with AppleScript dictionary discovery. Use when asked to "create calendar events", "automate calendar", "JXA calendar scripting", "EventKit automation", or "PyXA calendar automation". Covers events, calendars, recurrence, time zones, batch operations, and EventKit ObjC bridge.
Automates Apple Notes via JXA. Use when asked to "create notes programmatically", "automate Notes app", "JXA notes scripting", or "organize notes with automation". Covers accounts/folders/notes, HTML bodies, queries, moves, and Objective-C/UI fallbacks for Notes.app automation on macOS.
Automates Apple Reminders using JavaScript for Automation (JXA). Use when asked to "create reminders programmatically", "automate reminder lists", "JXA Reminders scripting", or "manage reminders via automation". Covers list/reminder management, filtering with 'whose' queries, efficient creation via constructors and push operations, and copy-delete patterns for moving items.
为中文微信公众号文章分析内容并生成清晰易懂、真实 3D 毛毡质感且图文一体的头条长封面、1:1 分享页封面与正文配图，同时给出每张正文图应插在哪个原句之后。用于用户提供文章、Markdown 或正文，并要求“公众号封面”“分享封面”“方形封面”“毛毡配图”“文章插图”“为正文配图”“只做封面”“生成 N 张配图”“推荐配图数量”等任务；未提供文章标题时默认根据核心命题生成合适的封面文字，正文图未指定画幅时默认 16:9，也支持用户明确指定 4:3 或 3:4，并使用少量毛毡文字帮助单图理解；适配方法论、教程、专业干货、商业科技、情感叙事、个人成长、生活方式、教育与母婴等内容。
> Use when starting significant features, evaluating build-vs-buy decisions, reframing failed approaches, or when the user mentions "outcome engineering", "o16g", "outcome-first", "what's the outcome", or "frame this as an outcome". Also use proactively when a task description focuses on implementation ("build X", "add Y") without defining the desired outcome or verification criteria.
> Automatically triggered when designing system architecture, planning new projects, creating implementation plans, conducting architecture reviews, or auditing existing architectural patterns, infrastructure decisions, API design, testing strategies, CI/CD pipelines, security architecture, or code organization. Works for Python web APIs, infrastructure/DevOps, Garmin/embedded systems, and frontend projects. Distinguishes between personal projects (strict standards) and client work (adaptive approach).
> Facilitate structured brainstorming sessions as a coach and hybrid thinking techniques (SCAMPER, Six Thinking Hats, reversal, analogical thinking, question storming, role playing…), one technique at a time, with the user generating ideas first and the AI building on them with clearly labeled additions — then converge, categorize, and deliver a session document with priorities and next steps. Use this skill whenever the user wants ideas or wants to think out loud together — "brainstorm with me", "give me ideas for…", "help me come up with…", "let's explore options for…", "I'm stuck on the name / the features / the campaign angle" — in any language (e.g. Vietnamese "brainstorm cùng tôi", "cho tôi ý tưởng", "nghĩ cùng tôi xem", "gợi ý phương án giúp tôi"; Spanish "ayúdame a generar ideas"; Japanese 「アイデア出しを手伝って」), even when they never say the word "brainstorm". Trigger for open-ended exploration of a topic, product, name, feature set, campaign, event, career move, or any generative question that does not first require diagnosing why something is broken. Also trigger when the user asks for multiple perspectives on their ideas or a structured devil's-advocate pass — "give me different angles on these ideas", "phản biện mấy ý tưởng này giúp tôi", "party mode" — the skill's party mode handles multi-role ideation and counterpoint. (If the request is "X is failing and we don't know why", root-cause diagnosis comes first — the problem-solver skill in this family leads there; if the question is who the users are and what they need, with real research, design-thinking leads; company-level strategic bets belong to strategy-board.)
> Facilitate a full design-thinking engagement — Empathize, Define, Ideate, Prototype, Test — as a disciplined facilitator and thinking partner that observation plans, experiments with pass/fail criteria), the user brings back real data, and every insight traces to registered evidence. Use this skill whenever the user wants to understand users deeply and design a solution or experience for them — "run design thinking", "understand our users", "design user interviews", "synthesize these interview notes", "build personas", "write How-Might-We questions", "brainstorm solutions for…", "prototype this concept", "design an experiment / usability test to validate…", "our users are churning and we don't know why" — in any language ("tư duy thiết kế", "nghiên cứu người dùng", "phỏng vấn khách hàng", "デザイン思考", "设计思维"), even when the user never says "design thinking". Also trigger when the user drops raw interview notes, transcripts, or survey exports and wants them turned into insights, personas, or product decisions. (For "is there a market for X" desk questions, the market-researcher skill leads; this skill leads when the question is who the users are and what to build for them.)
> scans, market sizing (TAM/SAM/SOM), competitor analysis, customer demand signals, and trend/macro (PESTEL) analysis. Use this skill whenever the user wants to research, size, validate, or enter a market — "is there a market for…", "how big is the market for…", "who are the competitors of…", "should I build/launch/sell…", "validate this business idea", "market research for…", "market entry" — in any language and for any country's market (e.g. "nghiên cứu thị trường", "étude de marché", "市場調査", "análisis de mercado"), even when the user never says the words "market research". Also use it when another skill or workflow (strategy-board, design-thinking, a product brief) needs external market facts delivered into its fact base or research folder.
> facilitator that turns "X is broken and we don't know why" into a precise problem statement, bounds it with Is/Is-Not analysis, finds root causes with the method that fits the problem's shape (Five Whys for linear chains, fishbone for multi-factor tangles, causal loops for systems that fight back), labels every causal claim verified or assumed, designs verification tests, then generates solutions traced to root causes, drives an evidence-cited decision, and plans rollout with pivot triggers. Use this skill whenever the user reports something failing, breaking, slowing, or recurring without a known cause — "sales dropped and we don't know why", "this keeps happening", "orders keep arriving late", "why does X keep failing", "find the root cause", "run a post-mortem", "5 whys" — in any language (e.g. Vietnamese "sao cứ bị vậy hoài", "tìm nguyên nhân gốc", "X đang hỏng "give me ideas to fix falling sales" is a diagnosis request wearing a brainstorm costume. Trigger for operational, process, technical, and business problems with an unknown or unverified cause. (If nothing is broken and the user wants open-ended ideas, brainstorm-coach leads; if the problem is really about understanding users and their behavior — churn driven by what users feel and need — design-thinking leads; company-level strategic bets belong to strategy-board.)
> Act as a disciplined product manager copilot that turns evidence into prioritization with sensitivity analysis, PRDs with story maps and user stories, north-star metrics and OKRs, experiment designs, launch plans with rollback criteria, feedback triage, platform-vs-feature decisions, and light pricing/packaging — all inside a persistent per-product workspace where every number declares its origin. Use this skill whenever the user wants to decide what to build, spec it, or ship it — "write a PRD for…", "prioritize our backlog / these features", "what should we build next", "plan OKRs for the quarter", "define our north star metric", "design an A/B test for…", "plan the launch of…", "triage this pile of customer feedback", "should this be a platform or a feature", "help me manage this product" — in any language ("viết PRD", "ưu tiên tính năng nào", "quản lý sản phẩm", "lập kế hoạch ra mắt", "プロダクト管理", "产品经理"), even when the user never says "product manager". Also trigger when the user returns to an existing `<product>-pm/` workspace with any product question. (Deep user discovery belongs to design-thinking, desk market facts to market-researcher, company-level strategic bets to strategy-board — this skill leads when the question is what to build, in what order, and how to ship it.)
> Act as a disciplined project-management copilot (PM/PMO) that runs the delivery loop — initiation & charter, planning & scheduling, estimation with reference-class checks, risk management (ROAM), honest status reporting, scope change control, stakeholder communication, meetings turned into tracked actions, lessons learned, and portfolio roll-ups — methodology-agnostic (predictive, agile, hybrid) inside a fixed per-project `_project/` workspace where every status color, percent-complete, and estimate declares its evidence. Use this skill whenever the user wants to start, plan, track, rescue, or report on a project — "kick off this project", "make a project plan / timeline / WBS", "estimate how long this will take", "what date can I commit to", "build a risk register", "run a pre-mortem", "write the weekly status report for the steering committee", "the deadline slipped, what now", "turn this meeting transcript into action items and decisions", "prepare the steering-committee pack", "review my project portfolio" — in any language ("gestion de projet", "Projektmanagement", "quản lý dự án", "プロジェクト管理", "项目管理", "gestión de proyectos"), even when they never say "project management". Also trigger whenever a `_project/` directory exists in the working tree and the user asks anything about schedule, deadline, risk, status, scope, budget, or stakeholders. (What to build belongs to product-manager; company-level bets to strategy-board — this skill leads when the question is whether committed work will land on time, in scope, on budget, and who needs to know.)
> A C-level strategy advisory board, run as a team of named specialist agents, that takes an executive from a raw strategic question to a defended, board-ready recommendation. Use this skill whenever the user faces a significant business decision or wants strategic analysis — market entry, build-vs-buy, M&A, digital transformation, annual planning, portfolio prioritization, pricing, a big investment, a competitive threat, a turnaround. Trigger on requests like "should we invest in / build / buy / enter…", "develop a strategy for…", "evaluate this opportunity", "make the business case", "stress-test this plan", "run a pre-mortem", or "prepare a board presentation" — in any language, even when the user doesn't say the word "strategy". Also trigger when the user names a board member (Drucker, Porter, Christensen, Graham, Grove, Wack, Taleb, Minto) or asks to convene the board / open a boardroom session.
Guided process for shaping product ideas, features, and specs by systematically uncovering the user's unknowns before anything gets built. Use this whenever the user wants to shape, spec, define, scope, or think through a product or feature — including phrases like "I have an idea for...", "help me shape...", "let's spec out...", "write a PRD/brief for...", "should we build...", or when they bring a vague product problem (churn, activation, a new market) and need to turn it into a concrete, buildable pitch. Also use when the user asks to brainstorm product directions or wants mockups to react to before committing to a spec.
>- before adding (poster + synopsis), list/remove shows, list today's and upcoming episodes, and run a silent daily cron that alerts only when a tracked show airs. Use when the user wants series tracking, episode air-day alerts, "add this show", "what airs today", TVmaze, TV calendar, or favorite-shows monitoring.
> Self-configuring content creation pipeline with geo-lint validation. On first use, scans your project to learn its framework, content schema, categories, and authors, then creates SEO & GEO-optimized content matched to your brand voice. Validates every piece with geo-lint's 92 rules until "write blog", "new post", "content calendar", "brand voice", "content strategy".
Questionnement structuré pour cadrer une feature ou brainstormer une app : une question à la fois, descend l'arbre de décision, recommandation justifiée. Utilise sur /interroge, \"aide-moi à planifier\", \"j'ai une idée de feature/app\".
> Skill routing and workflow orchestration. Selects Inline Plan or Spec-backed Plan, routes to the correct workflow skill, and manages transitions between phases. Use when starting any conversation or task to determine which planning mode and skill apply.
> Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
> Grill the user relentlessly about a plan, decision, or idea, maintaining the project's domain model (CONTEXT.md, ADRs) as decisions crystallise. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
> Conversational design workshop for substantial work. Interviews the human one question at a time, explores 2-3 approaches with trade-offs, and presents the design section by section for approval before writing the spec. Combines requirements discovery with codebase research and architecture design. Use when the user explicitly requests a spec or when atelier-orchestrator selects a Spec-backed Plan. Ambiguous design or discovery requests route through atelier-orchestrator.
> Write approved implementation plans in one of two modes. Explicit Inline mode creates a conversational plan for bounded work. Spec-backed Plan converts an approved design.md into plan.json and optional tracked tasks. Trigger after atelier-orchestrator selects a mode, when the user asks to plan work, or after spec-brainstorm completes. Direct invocation without a selected mode uses Spec-backed Plan. Do NOT use for research or execution.
> Guides digital forensic evidence collection following NIST SP 800-86 and RFC 3227 order of volatility. Auto-invoked when the user needs to collect forensic evidence, preserve chain of custody, capture volatile data, create disk images, or handle cloud forensics. Produces an evidence collection plan with volatility-prioritized acquisition steps, integrity verification, and chain-of-custody documentation.
> Provides structured incident containment strategies mapped to NIST SP 800-61 Rev 2 and MITRE ATT&CK techniques. Auto-invoked when a confirmed incident requires isolation decisions, credential revocation, network segmentation, or DNS sinkholing. Produces a containment plan with short-term and long-term actions, business impact assessment, and ATT&CK-mapped countermeasures.
> Executes a structured incident response workflow based on NIST SP 800-61 Rev 2 and the SANS Incident Handler's Handbook. Auto-invoked when the user reports a security incident, asks how to respond to a breach, or needs help with incident classification, containment decisions, stakeholder notification, or evidence preservation. Produces an incident response plan with severity determination, containment decision tree, communication templates, and escalation criteria.
> Guides structured triage of security alerts using a four-phase methodology (collect, correlate, classify, escalate) mapped to MITRE ATT&CK v16 and aligned with NIST SP 800-61 Rev 2 incident handling guidelines. Auto-invoked when the user discusses alert investigation, asks "is this a true positive?", or shares alert data requiring disposition. Produces a triage decision with priority assignment, disposition category, and escalation recommendation.
> Prioritizes patches and manages remediation SLAs using SSVC 2.1 decision outcomes, EPSS v3 trend analysis, and CISA KEV catalog cross-referencing. Covers SLA frameworks by severity tier, compensating controls assessment, patch window scheduling, risk acceptance criteria, and exception management. Auto-invoked when users ask about patch scheduling, SLA compliance, risk exceptions, or remediation backlogs.