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
Build and configure the DevExpress Blazor Scheduler (DxScheduler) — a calendar/appointment scheduling component for Blazor Server, WebAssembly, and Hybrid apps. Use for day/week/work-week/month/timeline views; data binding via DxSchedulerDataStorage and AppointmentMappings; appointment creation, editing, deletion, drag-and-drop and resize; recurring appointments (RecurrenceInfo / recurrence rules); resources (rooms/people); labels/statuses; and time/work-time configuration. Also use for DxScheduler, scheduler, calendar, appointment calendar, recurring appointments, and scheduling feature comparisons or migration scenarios.
> Build calendar/scheduling UI with DevExtreme Scheduler. Covers data binding and field mapping, view configuration, appointment types (one-time, all-day, recurring), editing, resources and grouping, remote data with lazy loading, toolbar customization, and templates.
DevExpress WinForms Scheduler (SchedulerControl with SchedulerDataStorage; Day/WorkWeek/FullWeek/Month/Year/Timeline/Agenda/Gantt views; appointments, resources, recurrence, reminders, labels, statuses). Covers getting started (NuGet, RibbonForm, DateNavigator, Start), data binding (bound mode with appointment/resource field mappings, custom mappings, unbound code mode, resource grouping, RefreshData), data items (Appointment types Normal/Pattern/Occurrence/Exception, recurrence Daily/Weekly/Monthly/Yearly, RecurrenceInfo, reminders, labels, statuses, custom fields), views (SchedulerViewType, DayView TimeScale/WorkTime, MonthView CompressWeekend, TimelineView scales, ActiveViewType, grouping by resource/date), and appearance customization (AppointmentViewInfoCustomizing, CustomDrawAppointment, InitAppointmentDisplayText). Use for any SchedulerControl scenario — calendar scheduling, resource booking, project timelines, appointment management.
Build WPF applications with the DevExpress Data Editors library — text, numeric, date/time, lookup, combo/listbox, image, color, visualization and utility editors. Use when adding TextEdit, ButtonEdit, ComboBoxEdit, DateEdit, SpinEdit, LookUpEdit, MemoEdit, PasswordBoxEdit, ListBoxEdit, CheckEdit, ToggleSwitchEdit, BrowsePathEdit, ImageEdit, ColorEdit/PopupColorEdit, TrackBarEdit, ProgressBarEdit, RatingEdit, SparklineEdit, BarCodeEdit, HyperlinkEdit, AutoSuggestEdit, PopupCalcEdit, or simple controls (SimpleButton, DropDownButton, SplitButton, FlyoutControl, RangeControl, Calculator, DateNavigator, DateRangeControl, TimePicker). Also use when someone mentions "BaseEdit", "EditValue", "DevExpress.Xpf.Editors", "dxe:", "StyleSettings", "operation modes", "editor masks", "ButtonInfo", "GlyphKind", or asks about input validation, masked input, in-place editors for GridControl/PropertyGrid, password fields, calendar pickers, or token combos. Covers both .NET 8+ and .NET Framework 4.6.2+.
Build WPF applications with the DevExpress Scheduler Control (SchedulerControl) — an Outlook-style calendar control for displaying and editing appointments, time regions, and resources. Use when adding SchedulerControl to a WPF project; binding to a DataSource with AppointmentsSource / ResourcesSource / AppointmentLabelsSource / AppointmentStatusesSource / TimeRegionsSource; configuring AppointmentMappings, ResourceMappings, custom field mappings; switching between Day, Work Week, Week, Month, Timeline, Agenda, List views; customizing appointment appearance via templates (AppointmentContentTemplate), styles (AppointmentStyle), brushes (BrushSet, BrushProvider); managing recurrence, reminders, labels, statuses, time regions, time zones. Also use when someone asks about "DevExpress WPF scheduler", "dxsch:SchedulerControl", "DevExpress.Xpf.Scheduling", "AppointmentItem", "ResourceItem", "TimelineView", "GroupType". Covers .NET 8+ and .NET Framework 4.6.2+.
>- Audit and safely clean Xcode-related developer storage on macOS. Use whenever a developer mentions low disk space, Xcode storage, DerivedData, simulator devices or runtimes, stale beta platforms in Xcode Settings, DeviceSupport, archives, dSYMs, CocoaPods caches, simulator dyld caches, project .build folders, downloaded Xcode DMGs/XIPs, duplicate Xcode installers, or old Xcode applications. Also use this skill proactively when you hit low storage during other work, such as a build, download, or install failing with an out-of-disk-space error. Always measure first, report recoverable GiB with evidence, and obtain explicit itemized approval before any mutation.
Organize and categorize files into logical structures. Creates folder hierarchies, renames files systematically, and consolidates related data.
Extract insights and intelligence from meeting discussions. Identifies key decisions, action items, and patterns from meeting content.
Provide expert guidance on iOS development and design. Advises on platform capabilities, best practices, and architectural decisions.
Document and communicate plans clearly. Structures implementation plans with tasks, decisions, and success criteria.
Develop software with validation requirements first. Emphasizes writing tests before implementation to guide design decisions.
Excellence-first strategic decision support. This skill should be used when users need to choose between options, pressure-test a plan, evaluate risk, or make a specific decision — across security, product, growth, operations, org design, and finance. Use when there is a decision with tradeoffs to score and a recommendation to make. For pure research ("what does the best in the world do about X?"), use best-in-world-research instead.
Expert Architecture Decision Record (ADR) creation and lifecycle management based on Olaf Zimmermann's methodology. Use when creating ADRs, reviewing architectural decisions, evaluating decision readiness, writing MADR templates, assessing decision quality, or managing ADR logs. Covers the full lifecycle from readiness (START criteria) through creation, MADR formatting, completion (ECADR criteria), and ongoing maintenance.
Expert full-cycle enterprise sales strategist for B2B SaaS. Use when planning sales strategy, pipeline management, deal progression, account planning, competitive displacement, or territory optimization. Covers multi-threading, executive engagement, champion development, buying committee navigation, and complex deal orchestration. Use for enterprise selling, account expansion, land-and-expand, and quota attainment.
Expert pricing strategy and monetization guidance for SaaS and digital products. Use when designing pricing tiers, creating pricing pages, setting value metrics, developing bundle strategies, planning price increases, writing pricing copy, analyzing competitive pricing, or optimizing annual vs monthly positioning. Use for packaging decisions, discount policies, enterprise pricing, and behavioral pricing tactics.
Expert platform and API product management guidance for developer-focused products. Use when planning API product strategy, designing APIs, improving developer experience (DX), creating developer documentation, building SDKs, planning API versioning and deprecation, building developer communities, creating integration marketplaces, or measuring platform health. Covers REST, GraphQL, webhooks, and platform ecosystems.
Expert product management guidance for day-to-day PM work. Use when creating roadmaps, prioritizing features, managing stakeholders, planning sprints, grooming backlogs, scoping features, planning releases, defining OKRs, managing technical debt, or coordinating go-to-market. Covers RICE, ICE, MoSCoW frameworks, cross-functional collaboration, and product metrics.
Expert product strategist for vision, strategy, and market positioning. Use when defining product vision, assessing product-market fit, sizing market opportunities (TAM/SAM/SOM), competitive positioning, or choosing between build/buy/partner. Covers business model design, monetization strategy, platform decisions, and strategic roadmap planning.
Expert Quarterly Business Review facilitation for maximizing customer value and strategic alignment. Use when designing QBR programs, preparing executive presentations, demonstrating ROI and value realization, conducting strategic account planning, aligning product roadmaps, identifying risks and opportunities, facilitating business reviews, or automating QBR processes. Use for EBR preparation, success metrics presentation, renewal preparation, and stakeholder engagement.
Bridges asset requirements from motion design specs to production-ready assets. Parses specs for required assets, recommends free/paid sources, provides format conversion guidance, generates validated import code, and offers asset preparation checklists. Use when preparing assets for Remotion projects or when asked "where to get assets", "how to prepare assets", "asset formats for Remotion".
Expert sales negotiation strategist for B2B deal-making. Use when planning negotiation strategy, handling discount requests, closing deals, navigating procurement, or structuring win-win agreements. Covers anchoring, framing, BATNA development, multi-party negotiations, and contract terms. Use for enterprise deals, pricing discussions, and high-stakes negotiations.
Strategic sales leadership guidance for B2B SaaS and enterprise software companies. Covers sales strategy, team building, pipeline management, enterprise selling, discovery calls, demos, proposals, negotiations, and sales operations. Use when building sales teams, designing sales processes, improving win rates, or scaling revenue operations. Use for "sales strategy", "sales process", "pipeline review", "deal strategy", "sales hiring", "quota planning".
Expert sales strategy and operations guidance for B2B SaaS companies. Use when designing sales processes, implementing qualification frameworks (MEDDIC, BANT, SPICED), territory planning, forecasting, quota setting, compensation design, or optimizing pipeline velocity. Covers sales methodology, org structure, tech stack selection, win rate analysis, and deal acceleration strategies.
> Load this skill when building any web feature, reviewing architecture decisions, or evaluating JavaScript dependencies. Under no circumstances build features that break completely when JavaScript is unavailable or fails. Absolutely always start with semantic HTML, layer CSS enhancements, and add JavaScript as the final, optional layer. Prioritize resilience and universal access over cutting-edge features.
Use when creating or iterating staged planning artifacts for a complex feature: design discussion, structure outline, final executor plan, or supporting research/research questions. Also use when designing before coding, breaking work into vertical slices, or deepening a high-value roadmap item, NNN improve plan, architecture candidate, or HumanLayer-style task.
Build evidence-backed software/product roadmaps from repo state, tickets, ideas, audit findings, or user goals — prioritize and sequence work across Now/Next/Later, milestones, dependencies, risks, and handoffs. Use when asked for a roadmap, feature roadmap, technical roadmap, release plan, milestone plan, backlog prioritization, sequencing, what to build next, or to turn improve/ideate/brainstorm/design-discussion outputs into an execution sequence. Not for implementing code or writing PR-level plans.
Use to create and maintain comprehensive documentation that helps agents navigate code effectively. Document directory structure, file purposes, architectural relationships, and design decisions so agents can work independently.
Use when starting a complex project, task, or feature to deeply clarify requirements, identify scope boundaries, map dependencies, and structure work into phases before any coding begins.
Use when starting a non-trivial coding task, feature, or bug fix that would benefit from upfront planning, research, and structured decomposition before writing code.
Use when creating new files, modifying existing files, adding new folders, or making structural changes to a codebase and you want documentation that agents (and humans) can grep/search to navigate the project.
Use when starting a new feature, writing a spec, or brainstorming architecture and you want to capture richer intent than typing allows. Speak your thoughts into a transcription tool, then feed the raw transcript to Claude Code for structuring.
Capture current work context for handoff to another agent/developer. Gathers git state, todos, and modified files into a structured handoff document saved to the related spec folder.
Use when responding to a Revise & Resubmit decision from AER, AER:Insights, or an AEJ, and a point-by-point response letter plus aligned manuscript revisions are needed. Handles triage, the concede / clarify / push-back decision, and the response-letter format that editors actually read.
Route gh-aw workflow design/create/debug/upgrade requests to the right prompts.
Diagnoses and fixes issues in Atlassian Forge apps. Use this skill whenever a Forge app has errors, crashes, shows blank UI, fails to deploy, doesn't appear after installation, has permission issues, or produces unexpected output. Trigger on any mention of forge logs, forge deploy errors, resolver errors, blank panels, missing scopes, Custom UI not rendering, production vs dev discrepancies, or any Jira/Confluence app that "stopped working". Also trigger when the user asks to debug, troubleshoot, investigate, or fix a Forge app issue — even if they haven't used the word "Forge" but describe a Jira panel or Confluence macro acting up.
| Delivery-risk reviewer that sizes the investment a plan is asking for against the team's actual confidence that it will land, and names specifically what's most likely to make it slip or fail to ship at all. Hunts the plan that asks for a six-month bet with three-week confidence, or hides its biggest unknown behind a confident-sounding timeline. Sounds like a delivery lead who has watched too many "should be straightforward" estimates blow up on the one unknown nobody named out loud. Not a cost reviewer — a bet-sizing reviewer. A lens for any product checkpoint — plan, roadmap, or investment/sequencing decision. has, a plan's riskiest unknown is buried in a status update instead of named up front, or nobody has said what would make this slip — any time the worry is "what's most likely to make this slip or fail to land, and is the investment sized to our confidence?"
Convene the persona panel on the CURRENT conversation / work-in-progress — the plan, design, or decision you've been building in this session. The INLINE counterpart to /council (which forks and runs isolated, so it cannot see the chat). Use when you want the council to critique what we're working on right now.
| Curmudgeonly engineering advisor that provides grounded skepticism, evidence-linked judgment, and constructive progress on architectural decisions, legacy refactors, tooling choices, and broad "how should I start?" questions. Sounds like a senior systems engineer who has reviewed too many designs to be impressed, but still cares about correctness. A lens for any checkpoint — brainstorm, design, plan, implement, debug, or review — not just up-front decisions. a tooling/legacy call, an implementation path, or a fix — any time the worry is "what will this cost us later?"
| Simplicity-obsessed design reviewer that interrogates complexity, questions every abstraction, and insists on the minimal viable design. Sounds like a senior engineer who has watched too many systems collapse under their own weight and now treats every unnecessary layer as a personal affront. Not a generalist skeptic — a simplicity zealot. A lens for any checkpoint — brainstorm, design, plan, implement, debug, or review — not just design. a layer, an over-built fix — any time the worry is "do we actually need this, or can it be deleted?"
| Goal-clarity reviewer that refuses to judge a solution until the intent behind it is pinned. Hunts goal drift and translation loss — the slow substitution of "the thing we set out to do" with "the thing we happen to be building." Sounds like a patient, relentless interrogator of "why are we doing this?" who will not be hurried past the question. Not a solution reviewer — a reviewer of whether the solution is even pointed at the right thing. A lens for any checkpoint — brainstorm, design, plan, implement, debug, or review — not just kickoff. nobody can say in one sentence what success looks like — any time the worry is "is this still the real goal?"
Convene the Product Development Council on the CURRENT conversation / work-in-progress — the plan, roadmap, or scope decision you've been building in this session. The INLINE counterpart to /product-council (which forks and runs isolated, so it cannot see the chat). Use when you want the council to critique what we're working on right now.
| Momentum-driven engineering reviewer that holds one uncompromising gate — is it REAL, proven end-to-end as a user would — while driving work forward. Demands proof over claims, plumbing before polish, fail-loud over fallbacks, trust in the model over instructions, and protects the critical path so good-but-costly ideas don't stall the work. Warm, blunt, forward-driving — not a curmudgeon. A lens for any checkpoint — brainstorm, design, plan, implement, debug, or ship — not just the finish. whether you're building in the right order, whether a fix is real or a band-aid, or whether work is actually done/ready — any time the worry is "are we fooling ourselves about what's real?"
| Adversarial breaker that reviews code by trying to make it fail, not by confirming it works. Hunts the unhappy paths — the malformed input, the empty string, the reversed range, the race condition — that the happy-path reviewer never types. Sounds like a gleeful adversary who thinks in inputs nobody intended and assumes everything is broken until a concrete attempt to break it comes up empty. Not a QA checklist — a hostile witness for the failure that hasn't happened yet. A lens for any checkpoint — brainstorm, design, plan, implement, debug, or review — not just a test gate. for "I tried to break it and couldn't," or nobody has named the input that makes this fall over — any time the worry is "how does this fail, and where are the edges?"
| User-need reviewer that speaks for the person who isn't in the room — the one who will actually live with what gets built. Hunts the gap between "we can build this" and "they actually want this," and between "it works" and "they can live with it." Sounds like the patient, slightly impatient voice of the absent user — uninterested in how clever the build is, relentless about whether anyone asked for it and whether it survives contact with a real person. Not a UX consultant — an advocate for the served person's desire and lived experience. A lens for any checkpoint — brainstorm, design, plan, implement, debug, or review — not just design. celebrated while the recovery path is missing, or nobody can name the person this serves — any time the worry is "does the person we serve actually want this, and can they live with it?"
> Use with root `twg` for Jira workitems, projects, boards, sprints, fields, transitions, comments, links, and administration. Applies Jira semantics and safe mutation rules.
> Use with root `twg` for deep iterative enterprise/company knowledge search and internal research with Rovo Search across connected apps/connectors including Confluence, Jira, Drive, Slack, Bitbucket, and GitHub.
> Clean up stale or unresolved Jira workitems. Dry-run single items, lists, boards, sprints, epics, or projects by matching Jira keys/titles to merged PRs, repos, Rovo/search-code hits, and assignee activity.
> Use with root `twg` to route owners, subject-matter experts, maintainers, reviewers, approvers, decision authorities, Heads of Engineering, or escalation paths for a topic, area, ask, project, service, or component.