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
Production readiness for CometChat — server-side token auth, user management CRUD, environment hardening, and security checklist. Replaces dev-mode authKey with server-side tokens.
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.
This skill should be used when the user asks to "plan a penetration test", "create a security assessment checklist", "prepare for penetration testing", "define pentest scope", "follow security testing best practices", or needs a structured methodology for penetration testing engagements.
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' or 'viral content.' This skill covers content creation, repurposing, and platform-specific strategies.
Use whenever the user wants to find, shortlist, vet, or enrich US B2B law firms — corporate, IP/patent, M&A and securities, employment, commercial litigation, regulatory/compliance, data privacy/cyber, real estate, and tax. Triggers on "find three boutique IP law firms in California", "shortlist M&A counsel for a Series-B fundraise", "patent prosecution for our hardware startup", or "pull contact info for these 10 law firm domains", even when described indirectly (outside counsel, cap-table review, GDPR/SOC2 oversight). Drives the ServiceGraph API (api.servicegraph.co) — a 100k+ US firm catalog filterable by industry, services, location, size, ratings. Skip personal/consumer legal services where the user is the end client (divorce, personal injury, criminal defense, family law, estate planning, wills) — the catalog is B2B-only. Also skip in-house GC hires, "is this NDA enforceable" DIY questions, non-US firms, individual freelancers.
>- Claim the single next governance todo (marks in_progress). Trigger on /pm-next and related English phrases for this command.
Interview the user relentlessly about a plan or design until every branch of the decision tree has an explicit recorded decision and no open questions remain. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
"Preview or rename a GitHub upstream repo and matching local project folder, update origin, and preserve Codex CLI and Claude Code continuity references."
Archive checked TODO.md tasks into `.ai/todos/TODO_UNTIL_YYYY_MM_DD.md`, leaving unchecked tasks.
Search and retrieve global memories — knowledge that applies across all projects. Use when the user asks 'what are our coding standards', 'what conventions do we follow', 'what's our infrastructure setup', 'do we have a rule about', 'what applies to all projects', 'shared knowledge', 'global rules', or when you need cross-project context like architecture decisions, server configs, or team policies.
Search and retrieve memories from Cortex persistent memory. Use when the user asks 'what did we decide about X', 'do you remember', 'what was the fix for', 'find that thing about', 'search memories', 'what do we know about', 'have we seen this before', or when you need context about past decisions, patterns, bugs, or architecture choices. Also use proactively when working on something that likely has relevant historical context.
Store important decisions, patterns, errors, lessons, and context into Cortex persistent memory. Use when the user says 'remember this', 'save this', 'store this for later', 'note this down', 'don't forget', 'this is important', 'bookmark this', or when a significant decision, bug fix, architecture choice, or lesson learned occurs during a session. Also use after resolving tricky bugs, making technology choices, or discovering important patterns.
Author first-class wiki pages (ADRs, specs, file docs, notes) that live alongside Cortex memory. Use when the user says 'this is an ADR', 'document this decision', 'write an ADR', 'add a spec', 'spec this out', 'document this file', 'add a note about', 'link these pages', 'bookmark this as a spec', or when finalizing a design decision that should persist as a human-readable document.
Walk a manager through a full quarterly performance review for a direct report, including peer feedback synthesis, performance/potential ratings, leadership principles assessment, and development planning
Assess Azure resource capacity, quota utilization, and growth trends to prevent outages from resource exhaustion. Use when asked about capacity, quotas, scaling readiness, load testing prep, Black Friday readiness, or growth projections.
Prepare and validate OpenSkills release readiness across runtime, bindings, examples, and regression gates with a deterministic checklist and go/no-go outcome.
Auditing SKILL.md normalization and self-evolving compliance. Scans SKILL.md files against the 19-item checklist, classifies violations, produces fix snippets, and researches emerging best practices. No code. Use when auditing SKILL.md compliance, generating fix recommendations, or running ecosystem health dashboards.
Designing, optimizing, and auditing repository structure. Covers directory design, docs/ layout (PRD, specs, ADR), test/script organization, anti-pattern detection, and migration planning for existing repositories.
Generating, optimizing, and auditing personal development environment config files (zsh/tmux/neovim/ghostty), and automating the macOS desktop via AppleScript/JXA/osascript (Finder, Mail, Safari, Calendar, Notes, System Events). Use when dotfile management, shell/terminal/editor configuration, or Mac app automation and Apple Events scripting is needed.
Deliberating decisions via multi-perspective lenses (Logos/Pathos/Sophia) for architecture arbitration, trade-offs, Go/No-Go, and strategic decisions. Does not write code. Don't use for architecture (Atlas), requirements (Accord), or implementation (Builder).
Planning, executing, and tracking releases in a unified workflow. Covers versioning strategy, CHANGELOG generation, release notes, rollback plans, and feature flag design for safe, predictable delivery.
Designing LLM-optimized folder structures. Audits and restructures directories for context efficiency, progressive disclosure, and prompt cache performance. Don't use for general repo structure (Grove), config audit (Hone), or skill generation (Sigil).
Cleaning up the skill ecosystem by auditing the agent roster for overlap, redundancy, and inactivity; proposes merge candidates and sunset plans with evidence + archive instructions. Propose-only (no execute). Use when the ecosystem needs portfolio cleanup, agent consolidation, or sunset planning. Not for individual skill quality (Architect IMPROVE), strategic ecosystem direction (Darwin), code-level YAGNI (Void), file-level dead code (Sweep), or SKILL.md format audit (Gauge).
Brainstorming interactively to deepen ideas via iterative dialogue using four modes (Expand/Propose/Evaluate/Subtract). Does not write code. Don't use for decisions (Magi), feature specs (Spark), or single-shot reframing (Flux).
Advising founders YC-style by surfacing the #1 bottleneck via socratic probing, giving pattern-matched honest feedback, detecting founder anti-patterns, and extracting 1-2 week action items. Use when seeking founder-mode advisory. Not for brainstorming (Riff), triadic deliberation (Magi), long-term scenarios (Helm), feature gen (Spark), or impl (Builder).
Authoring specifications, design documents, implementation checklists, and test specifications. Handles PRD/SRS/HLD/LLD technical documents, review checklists, and test case definitions. Does not write code. Use when technical documentation is needed.
Proposing new features leveraging existing data/logic as Markdown specifications. Use when brainstorming new features, product planning, or feature proposals are needed. Does not write code.
Channeling the documented thinking of named notable figures (an 'itako' medium) — applies their mental models, heuristics, and decision-style to your problem as advisory lenses. Don't use for decisions/verdicts (Magi), synthetic user personas (Cast), or fixed founder-mentor coaching (Sage).
Delivering working code fastest via build-first product delivery. Routes through minimum agent chains scoped to the task. S/M scopes skip planning and build immediately. Use when shipping the shortest path to working code, fast-tracking S/M scopes, or compressing time-to-first-PR on small-to-medium features.
Designing scheduling and time-aware logic for cron, timezone/DST, retry/backoff, and business-calendar systems. Use when schedule design is needed.
Directing UI/UX creative work — complete redesigns, new designs, and trend application. Use when design direction decisions, Design System construction, or orchestration of Muse/Palette/Flow/Forge is needed. Does not write code. Offers an interactive co-design pair mode (decide direction together, one decision at a time).
Document decisions, not just implementations. ADRs for architectural choices, inline docs for non-obvious code, and runbooks for operational knowledge.
Detects and mitigates LLM hallucinations in production pipelines. Validates AI-generated facts, code, and decisions before they reach end users or downstream systems.
Структурированный мозговой штурм перед любой творческой работой. Используй ПЕРЕД созданием контента, скилов, автоматизаций, проектов. Триггеры: 'давай подумаем', 'мозговой штурм', 'brainstorm', 'придумай', 'нужна идея', 'как лучше сделать', 'варианты'.
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs. Use when user asks about email, calendar events, Google Drive files, contacts, spreadsheets. Triggers on 'почта', 'gmail', 'календарь', 'calendar', 'google drive', 'контакты', 'таблица', 'sheets'.
Generate a complete professional event plan from guest background material. Takes guest bio / CV / intro copy as input, runs a multi-turn clarification dialog (activity type, audience, duration, tone), and outputs a cohesive plan with title + promo copy, minute-level rundown, tiered host question set, and gift / takeaway suggestions. Trigger when user mentions "活动策划", "策划案", "嘉宾对谈", "沙龙策划", "主持人问题", "活动流程", "event planning", "host prep", "salon plan", or pastes a guest bio asking for an event plan.
Vector search indexing and querying workflows using MCP Vector Search, including setup, reindexing, auto-index strategies, and MCP integration.
Emergency release workflow for critical bug fixes and security patches. Use when production issues require fast-track deployment.
PR quality checklist for ensuring comprehensive, well-documented pull requests. Use before submitting PRs to improve review efficiency and code quality.
Compare tradeoffs and recommend architectural patterns — dependency injection, service-oriented architecture, repository, domain events, circuit breaker, and anti-corruption layer. Use when choosing between design patterns, planning microservices boundaries, evaluating system design alternatives, or asking 'which pattern should I use' for a specific coupling or resilience problem.
Interactive idea refinement using Socratic method to develop fully-formed designs
> Use this skill whenever the user wants to FIND new prospects for their managed IT services a prospect list, researching a specific business as a potential client, figuring out who the decision maker or "IT person" is at a company, or planning how to approach a prospect (email vs call vs professional network vs mail, and when). Trigger on "find leads", "find prospects", "who should we go after in [area]", "research this business", "build a lead list", "is [company] a good fit", "who do I contact at [company]", "sweep [town] for candidates", or any mention of generating leads, prospecting an area, or door-knocking researches prospects and plans the approach; msp-sales owns the ICP definition and all outreach copy; msp-marketing owns broad marketing channels. Apply alongside msp-brand and msp-sales.
> questioning a ticket's priority, response and resolution targets, "the client says everything is down", escalation, after-hours or emergency requests, security incident intake, triage order, your PSA (ticketing) system workflow, time entries, or ticket categories. Also trigger when drafting anything that describes support levels or response times to a client, and when training new hires on the service desk workflow (client onboarding is msp-onboarding). Apply alongside msp-client-comms (the messages clients receive during incidents), msp-legal (the SLA schedule lives in each client's Order; security incidents have contract implications), msp-pricing (after-hours billing multipliers), msp-maintenance (alerts that escalate into tickets, and the on-call rotation behind the after-hours line), and msp-metrics (ticket data feeds every business number).
> gives notice, says they are not renewing, is switching providers, or asks to cancel; you decide to exit a client (see msp-metrics for that decision); or anyone mentions data return, removing our access, transitioning to a successor provider, a final invoice, or "offboarding" a client. Also trigger when drafting termination acknowledgments or closure letters. Apply alongside msp-legal (the signed MSA and Order govern notice, fees, and data handling; this is a legal-adjacent workflow), msp-brand (every message), msp-client-comms (the letters), and msp-metrics (log the loss and the reason).
> Guided first-run setup for the MSP Operations Kit. Use this skill whenever the user wants to set customize these skills", "make these skills mine", "replace the placeholders", "finish setup", "resume setup", "am I ready to use this with clients", or any first-run intent after purchase. Also trigger when another msp skill surfaces an unfilled placeholder token or an unreviewed example default, since that means setup is incomplete. Works through msp-brand first, then msp-pricing, then every skill's Setup Decisions, and finishes with a readiness check.
Linear CLI for issue tracking and project management. Use when developers mention: (1) Linear issues or tickets, (2) issue tracking or task management, (3) WDY team issues, (4) closing, updating, or triaging tickets, (5) linking PRs to issues, (6) issue states (triage, backlog, started, completed).
| 雅思听力错题分析 + 精听训练 + 题型追踪。逐题拆解错因，Section 得分分析，推荐精听任务。 触发方式：/ielts-listening、「听力」「错题」「精听」「听力怎么练」
Deliver a large implementation plan, architecture migration, refactor, or feature roadmap as right-sized, coherent subtasks that are meaningful to code, review, test, and recover independently. Use only when the user explicitly requests this skill or workflow, or explicitly accepts it after an optional proposal during a user-initiated brainstorming or planning session before coding. Do not use for ordinary coding requests with clear requirements and no prior user-requested brainstorming or discussion. This skill does not authorize subagents; before any spawn, explain the usage impact and obtain explicit user approval for the proposed agent count and scope.