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
\"What is important is seldom urgent and what is urgent is seldom important.\" Master Dwight D. Eisenhower's prioritization framework to focus on what truly matters. Use when: **Feeling overwhelmed** by too many tasks and not enough time; **Weekly planning** to set priorities for the week ahead; **Daily triage** when everything seems urgent; **Delegation decisions** to identify what others should handle; **Saying no** by recognizing tasks that shouldn't be done at all
\"Invert, always invert.\" Apply Carl Jacobi's mathematical principle and Charlie Munger's investing wisdom to solve problems by thinking backward from failure. Use when: **Goal setting** - Define what would guarantee failure, then avoid it; **Risk analysis** - Identify what could destroy your project before starting; **Decision making** - Evaluate choices by examining their worst outcomes; **Problem solving** - When direct approaches aren't working, reverse the question; **Strategy development...
Imagine your project has failed spectacularly—then work backward to identify why. Apply Gary Klein's \"prospective hindsight\" technique to catch failures before they happen. Use when: **Before launching** a product, campaign, or major initiative; **Before making** an important decision (hiring, investment, partnership); **Starting a project** to identify risks the team hasn't considered; **When overconfident** and everyone agrees the plan is great; **Before committing resources** to a signific...
Apply Edward de Bono's parallel thinking framework (1985) to make better decisions by examining ideas from six distinct perspectives systematically. Use when: **Making complex decisions** that require multiple perspectives; **Evaluating new products, offers, or strategies** before launch; **Breaking out of analysis paralysis** with structured thinking; **Running productive meetings** where everyone thinks in the same direction; **Balancing optimism with caution** in strategic planning
Make decisions that your 80-year-old self will thank you for. Master Jeff Bezos' mental model for bold choices that minimize long-term regret. Use when: **Career decisions** with long-term implications; **Startup vs. safe job** choices; **Major life pivots** (relocations, relationships, changes); **Risk-taking decisions** where fear is a factor; **Opportunity evaluation** when considering bold moves
Know when to move fast and when to move carefully. Master Jeff Bezos' framework for distinguishing high-stakes irreversible decisions from low-stakes reversible ones. Use when: **Prioritizing decisions** to know where to invest time; **Team empowerment** to understand what to delegate vs. escalate; **Avoiding analysis paralysis** on decisions that don't matter; **Risk management** to identify where caution is truly warranted; **Speed vs. thoroughness** trade-offs in any context
Think beyond immediate consequences to understand the chain reactions of decisions. Master Howard Marks' investment framework for seeing what others miss. Use when: **Strategic decisions** where long-term consequences matter; **Policy/rule changes** that will trigger behavioral responses; **Competitive moves** to anticipate market reactions; **Product decisions** where user behavior may shift; **Investment analysis** to see past obvious conclusions
Use when facing complex reasoning tasks - multi-step math, logic puzzles, decisions with tradeoffs, problems where direct answers fail, or when you need to show your work. Triggers on arithmetic errors, shallow analysis, or "I'm not sure" hedging.
Systematically validate your business hypotheses before building anything. Master Steve Blank's Customer Development methodology that became the foundation of Lean Startup and YC's approach. Use when: **Starting a new venture** to avoid building something nobody wants; **Before writing a line of code** to validate problem-solution fit; **Pivoting decisions** to systematically test new directions; **Early-stage fundraising** to prove market validation; **Product roadmap planning** to prioritiz...
Extract honest customer insights by asking questions about their life instead of your idea. Master Rob Fitzpatrick's methodology for conversations that can't lie to you. Use when: **Before building anything** to validate if the problem is real and painful; **Customer discovery calls** to get honest feedback without leading questions; **Pivoting decisions** to understand if you should change direction; **Feature prioritization** to learn what customers actually need vs. say they want; **Pricin...
Create research-backed buyer personas that drive real marketing and product decisions. Combine Buyer Personas methodology with Jobs-to-be-Done to build profiles based on actual behavior, not demographics fiction. Use when: **Starting customer discovery** to define who you're validating with; **Marketing campaign planning** to target the right messages to right people; **Content strategy** to create content that resonates with specific audiences; **Product roadmap prioritization** to build fea...
Validez la qualité de vos vidéos IA avant publication avec une checklist complète couvrant technique, créatif, et positionnement marque. Use when: **Avant publication** - Dernière validation avant mise en ligne; **Revue client** - Préparer les points de feedback anticipés; **Itération qualité** - Identifier les problèmes à corriger; **Go/No-Go decision** - Décider si la vidéo est prête; **Post-mortem** - Analyser pourquoi une vidéo a (ou n'a pas) performé
Use this skill when you need to define a test strategy covering scope, methods, resources, risks, and quality gates; triggers include test strategy and QA planning.
Use this skill when you need release-phase QA workflow from T-14 planning to go/no-go and post-release monitoring; triggers include release testing workflow and go/no-go QA.
Design structured customer onboarding workflows with phased checklists, email templates, success milestones, and ownership assignments.
Visualize and map user flows with Mermaid diagrams, decision points, error states, and conversion metrics to optimize user journeys.
Create and manage budgets with variance analysis and departmental allocation
Generate compliance checklists for SOC2, HIPAA, PCI-DSS, and GDPR with gap analysis and remediation priorities.
Develop and execute a content strategy that maps content to audience needs, funnel stages, and business goals through editorial planning and performance analysis.
Schedules meetings with internal and external stakeholders by parsing natural language requests, resolving time zones, checking calendar availability, proposing optimal slots, and managing invitations and RSVPs.
Capture, organize, and retrieve notes efficiently using structured formats, tagging, and file management for meetings, ideas, research, and daily logs.
Automate repetitive tasks and workflows using scripting, file watchers, scheduled jobs, CI triggers, and API polling to eliminate manual toil.
Manages software projects end-to-end — decomposing work into tasks, tracking progress across sprints, generating status reports, and integrating with tools like Jira, Linear, GitHub Issues, and Trello.
Designer-turned-developer who crafts stunning UI/UX even without design mockups. Use for any frontend implementation requiring visual design decisions, aesthetic direction, or pixel-perfect UI work.
[TODO: Complete and informative explanation of what the skill does and when to use it. Include WHEN to use this skill - specific scenarios, file types, or tasks that trigger it.]
Extract and summarize core features, constraints, and priorities from requirement documents. Use when analyzing PRDs, RFCs, business requirements, user stories, epics, or any requirement documentation to identify must-have features, technical constraints, priority levels (P0/P1/P2/MoSCoW), and key decision points. Triggers when users ask to summarize, analyze, extract, or understand requirements from documents.
Interview-based strategic planning for complex software tasks. Conducts structured requirements gathering, gap analysis, and generates detailed work plans before implementation begins.
Preserves or recovers the reasoning behind a codebase - architectural decisions, rejected alternatives, workarounds, incident learnings, operational constraints, and historical context the code itself cannot explain. Use when implementing or reviewing a non-trivial change involving a design decision, workaround, incident fix, operational constraint, rejected alternative, or changed assumption; when documenting an existing or legacy codebase; during onboarding or a maintainer handover; or when interviewing a developer before their knowledge is lost (e.g. before they leave or retire); or when the user expresses frustration with, or reports a problem with, this skill itself. Identifies what the code cannot explain, asks focused questions instead of generic ones, and maintains concise, topic-based, version-controlled documentation readable by both humans and AI agents.
Author and track Architecture Decision Records. Routed to when the user invokes /adr to record a new decision or /adr-status to list ADR health. Authors numbered, dated, user-attributed ADRs under .codearbiter/decisions/, maintains supersede chains, and reports status read-only. Never authors an ADR as its own judgment — every ADR carries explicit user attribution.
Reconcile the project's architectural artifacts against the scaffold and prior decisions, then present each variance as a SMARTS analysis for the user to decide. Routed to when the user asks to arbitrate, reconcile, or consolidate architectural context, requests a variance report, mentions ADR conflicts, or asks which downstream artifacts the current state supports. Never decides alone — every arbitration is user-attributed and logged.
The Socratic spec-refinement front of /feature, and the planning front of /sprint. Routed to BEFORE any code — it takes a one-line idea and drives it to an approved, concrete spec with testable acceptance criteria. Four gated phases — frame, refine, write, approve. No implementation and no handoff to tdd until the spec is on disk and approved; each acceptance criterion becomes one tdd Phase 1 obligation.
The terminal step of /feature and /sprint. Routed to once commit-gate has cleared, to decide the branch's fate — merge via PR, open a PR, or discard. Direct merge to the default branch is forbidden; every change lands through a PR. Under /sprint the skill auto-selects "open PR" and surfaces the merge decision to the user.
The Socratic spec-refinement front of /feature, and the planning front of /sprint. Routed to BEFORE any code — it takes a one-line idea and drives it to an approved, concrete spec with testable acceptance criteria. Four gated phases — frame, refine, write, approve. No implementation and no handoff to tdd until the spec is on disk and approved; each acceptance criterion becomes one tdd Phase 1 obligation.
Author and track Architecture Decision Records. Routed to when the user invokes /adr to record a new decision or /adr-status to list ADR health. Authors numbered, dated, user-attributed ADRs under .codearbiter/decisions/, maintains supersede chains, and reports status read-only. Never authors an ADR as its own judgment — every ADR carries explicit user attribution.
Reconcile the project's architectural artifacts against the scaffold and prior decisions, then present each variance as a SMARTS analysis for the user to decide. Routed to when the user asks to arbitrate, reconcile, or consolidate architectural context, requests a variance report, mentions ADR conflicts, or asks which downstream artifacts the current state supports. Never decides alone — every arbitration is user-attributed and logged.
The terminal step of /feature and /sprint. Routed to once commit-gate has cleared, to decide the branch's fate — merge via PR, open a PR, or discard. Direct merge to the default branch is forbidden; every change lands through a PR. Under /sprint the skill auto-selects "open PR" and surfaces the merge decision to the user.
Report the health of Architecture Decision Records — aged, unchallenged, supersession candidates, unresolved CONFIRM-NN. Read-only.
Author a numbered, dated, user-attributed Architecture Decision Record under .codearbiter/decisions/.
Assemble the governance record for a range — commits, overrides, ADRs, sprint auto-decisions, open questions, checkpoint findings — into one dated audit packet. Read-only.
Start a feature: brainstorm a spec, get it approved, then drive it test-first through the pipeline. The one entry to implementation.
SMARTS arbitration — reconcile architectural artifacts against the scaffold and prior decisions; every variance resolved by an explicit, user-attributed choice.
Autonomous sprint — one interactive spec gate, then plan-to-PR execution with every auto-decision SMARTS-scored and logged. Hard gates remain true stops.
The Socratic spec-refinement front of /feature, and the planning front of /sprint. Routed to BEFORE any code — it takes a one-line idea and drives it to an approved, concrete spec with testable acceptance criteria. Four gated phases — frame, refine, write, approve. No implementation and no handoff to tdd until the spec is on disk and approved; each acceptance criterion becomes one tdd Phase 1 obligation.
Reconcile the project's architectural artifacts against the scaffold and prior decisions, then present each variance as a SMARTS analysis for the user to decide. Routed to when the user asks to arbitrate, reconcile, or consolidate architectural context, requests a variance report, mentions ADR conflicts, or asks which downstream artifacts the current state supports. Never decides alone — every arbitration is user-attributed and logged.
Author and track Architecture Decision Records. Routed to when the user invokes /adr to record a new decision or /adr-status to list ADR health. Authors numbered, dated, user-attributed ADRs under .codearbiter/decisions/, maintains supersede chains, and reports status read-only. Never authors an ADR as its own judgment — every ADR carries explicit user attribution.
The terminal step of /feature and /sprint. Routed to once commit-gate has cleared, to decide the branch's fate — merge via PR, open a PR, or discard. Direct merge to the default branch is forbidden; every change lands through a PR. Under /sprint the skill auto-selects "open PR" and surfaces the merge decision to the user.
Report the health of Architecture Decision Records — aged, unchallenged, supersession candidates, unresolved CONFIRM-NN. Read-only.
Author a numbered, dated, user-attributed Architecture Decision Record under .codearbiter/decisions/.