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
Maintain portfolio allocations over time using calendar-based, threshold-based, and tax-efficient rebalancing strategies. Use when the user asks about when to rebalance, rebalancing bands, transaction cost trade-offs, tax-efficient rebalancing, or the rebalancing premium. Also trigger when users mention 'my portfolio drifted', 'how often should I rebalance', 'rebalancing across taxable and IRA accounts', 'volatility harvesting', 'buy low sell high automatically', or ask whether to use cash flows to rebalance.
Turn a retirement portfolio into sustainable lifetime income: sequence-of-returns risk, the 4% rule and its assumptions, Guyton-Klinger-style guardrails, RMD calculation from the Uniform Lifetime Table, Social Security claiming math (early reduction, delayed credits, breakeven age, survivor benefits), gap-year bracket-filling with Roth conversions, bucket strategies vs total-return, and SPIA annuitization as longevity insurance. Use when the user asks about a 'safe withdrawal rate', 'when should I claim Social Security', a 'guardrails strategy', 'sequence of returns risk', or 'how much can I spend in retirement'. Also trigger on RMD amounts or missed-RMD penalties, Social Security breakeven analysis, '4% rule', 'bucket strategy', retirement paycheck design, drawdown or decumulation planning, and whether to buy an annuity. For accumulation-side savings math, see savings-goals; for asset location and tax mechanics, see tax-efficiency.
Maximizes after-tax returns through strategic asset location, gain/loss management, and withdrawal sequencing. Use when the user asks about asset location, Roth conversions, tax-efficient withdrawals, tax lot selection, or charitable giving with appreciated securities. Also trigger when users mention 'which account should I hold bonds in', 'tax drag', 'Roth vs Traditional', 'RMD planning', 'bracket stuffing', 'HIFO vs FIFO', or ask how to minimize taxes on investments. For tax-loss harvesting execution and wash-sale mechanics, see the tax-loss-harvesting skill.
Execute a complete tax-loss harvesting workflow from candidate identification through post-harvest monitoring. Use when the user asks about finding TLH candidates, gain/loss budgeting, replacement security selection, wash-sale compliance, or harvest execution planning. Also trigger when users mention 'unrealized losses in my portfolio', 'swap ETFs for tax purposes', 'harvest losses before year-end', 'substantially identical security', 'wash-sale window', 'NIIT offset', 'loss carryforward', or ask how much tax they can save by harvesting.
Use this skill for any work involving a MATLAB Project (.prj file) — creating a new project, tracking files, managing the project path, configuring Simulink cache and code-generation folders, running project health checks, or writing build scripts that keep the project in sync with the file system. Trigger phrases include "set up a MATLAB project", "create a .prj", "track this file in the project", "project health check", "build script conventions". This skill is the generic foundation; domain-specific skills (e.g. `mbse-workflow`) build on it.
Use this skill for guided MBSE work in MATLAB — starting a new project, resuming work mid-workflow on an existing project, or answering orientation questions about how the MBSE skills fit together. Trigger when the user says they want to create, start, or set up a new MBSE project; work on a model-based systems engineering / RFLPV project; or asks which skill covers which phase. Walks through phases one at a time — propose → approve → generate → run → confirm. Use proactively whenever someone mentions starting or continuing an MBSE project.
Use this skill when the user asks about: 'any crypto news', 'latest news', 'market update', 'daily briefing', 'BTC news', 'ETH news', 'news on SOL', 'search SEC ETF', 'regulation news', 'Bitcoin halving', 'is BTC bullish or bearish', 'coin sentiment', 'sentiment trend', 'trending coins', 'top bullish coins', 'bearish sentiment', 'social buzz', 'market mood', 'fear and greed', 'full article', 'read more', 'economic calendar', '经济日历', 'macro data', '宏观数据', 'NFP', 'nonfarm', '非农', 'CPI', 'GDP', 'FOMC', '利率决议', 'interest rate decision', 'PMI', 'unemployment rate', '失业率', 'economic events', '经济事件', or any request for crypto news, market intelligence, sentiment analysis, social trend data, or macro-economic calendar. Requires API credentials. Do NOT use for market prices/candles (okx-cex-market), placing orders (okx-cex-trade), or account info (okx-cex-portfolio).
> Use when designing multi-app Frappe architectures, deciding whether to split functionality into separate apps, or implementing cross-app communication patterns. Prevents monolithic app sprawl, circular dependencies between apps, and broken override chains. Covers multi-app architecture decisions, app dependency management, cross-app hooks, override patterns, when to split vs extend, shared DocType strategies.
> Use when migrating a Frappe app between major versions, detecting breaking API changes, or resolving post-migration errors. Prevents failed migrations from undetected deprecated APIs, removed methods, and changed function signatures. Covers breaking change detection v14-v15-v16, deprecated API mapping, migration checklist, common migration errors, automatic fix suggestions.
> Use when creating or modifying Frappe Workflows, defining states and transitions, adding action conditions, or troubleshooting workflow permission errors. Prevents stuck documents from misconfigured transitions, missing state permissions, and circular workflow paths. Covers Workflow DocType, workflow states, transitions, actions, conditions (Python expressions), workflow permissions, workflow_state field, Workflow Action DocType.
> Use when debugging or handling permission errors in Frappe/ERPNext. Prevents broken document access from throwing in permission hooks. Covers PermissionError (403), has_permission hook failures, User Permission restricting too much or too little, perm_level blocking field access, System Manager bypass not working, Guest access denied, sharing permissions not applying, permission_query_conditions breaking get_list, owner-based permissions confusion, Apply User Permission checkbox behavior, and the permission debug workflow using frappe.permissions.get_doc_permissions. User Permission, perm_level, sharing, guest access, owner permission.
> Use when implementing hooks.py configurations in a Frappe custom app. Covers step-by-step workflows for doc_events, scheduler_events, override/extend_doctype_class, permission hooks, extend_bootinfo, fixtures, asset injection, website hooks, and doctype_js. Prevents broken transactions, missed migrations, and multi-app conflicts. extend doctype class, permission hook, scheduler job, fixtures, doctype_js, extend_bootinfo, website hooks.
> Use when building a custom Frappe app from scratch. Covers bench new-app walkthrough, app structure decisions, adding DocTypes, hooks, patches, fixtures management, development workflow (bench migrate, build, clear-cache), testing, packaging, installing on another site, version app, new frappe app, bench new-app, app structure, module creation, doctype creation, fixtures, patches, deployment, packaging, data migration, patch file, patches.txt, migrate data between DocTypes, create new app from scratch.
> Use when building custom dialogs, extending List View, creating Page controllers, or adding Kanban/Calendar views and realtime updates. Prevents UI freezes from synchronous calls, broken dialogs from wrong field definitions, and missed socket events. Covers frappe.ui.Dialog, frappe.ui.form.MultiSelectDialog, List View customization, frappe.pages, Kanban Board, Calendar View, frappe.realtime, socket.io publish/subscribe.
> Use when implementing document Workflows, approval chains, or state-based transitions in Frappe. Prevents stuck documents from missing transitions, broken approval chains, and permission errors on workflow actions. Covers Workflow DocType, Workflow State, Workflow Action, transition rules, allowed roles, conditions, workflow_state field, apply_workflow.
> Use when configuring backups, restoring sites, encrypting backup files, scheduling automated backups, or planning disaster recovery. Prevents data loss from missing backups, failed restores, and unencrypted sensitive data. Covers bench backup, bench restore, backup encryption, S3/remote storage, scheduled backups, disaster recovery procedures.
> Use when upgrading Frappe/ERPNext between major versions (v14 to v15, v15 to v16), troubleshooting failed migrations, or planning rollback. Prevents broken upgrades from skipped patches, incompatible customizations, and missing pre-upgrade checks. Covers version upgrade paths, bench update, migrate command, patch troubleshooting, rollback procedures, breaking changes per version.
cheat-on-skill 的陪跑进度 skill。用户问“今天该干嘛”“我现在做到哪了”“继续学”“打卡”“我卡住了”“下一步是什么”时触发。读取 .skill-state.json 的 active.progress 和 learning_plan，给当天任务、检查完成情况、记录进度、根据快慢调整计划。前置：已有 .skill-state.json 且 active.learning_plan 存在。
> Builds a feature specification from scratch with plan-a-feature and publishes it to a user-specified Confluence location, posting the spec as a parent page and each companion artifact (decision log, team findings, technical notes) as a child page beneath it. Use when the user wants a new feature planned, designed, scoped, or specified AND posted to a Confluence space or page. Requires a configured Atlassian MCP server. Does not plan to local files only — use plan-a-feature. Does not publish an arbitrary existing markdown file — use markdown-to-confluence. Does not refine or stress-test an existing plan — use iterative-plan-review. Does not document already-built features to Confluence — use project-documentation-to-confluence.
> Break a work-items.md file (produced by /plan-work-items) into independently-grabbable Jira tickets, one per slice, in a single Jira project. Use when you want to turn a work-items file into Jira tickets, publish work items as Jira issues, or create implementation tickets that can be worked on and tracked in Jira. Requires a configured Atlassian MCP server. Does not produce the work-items file itself — use plan-work-items to break a plan into work items first. Does not post to GitHub — use work-items-to-issues for GitHub issues.
> Creates and updates coding standards, conventions, rules, and guidelines for the current project. Use when creating new standards from scratch, converting existing documents into coding standards, or updating existing standards. Does not create architectural decision records — use architectural-decision-record for ADRs. Does not write feature or system documentation — use project-documentation for that. Does not research open-ended options — use research. Does not produce runbooks for operational scenarios — use runbook for that.
> Create, extract, or convert an ADR (architectural decision record) using the ADR template. Use when creating new ADRs, extracting an ADR from existing documentation, converting a document into an ADR, recording an architecture or design decision, or updating the status of an existing ADR. Does not create or update enforceable coding standards or conventions — use coding-standard for that. Does not write feature or system documentation — use project-documentation instead.
> Turn a work-items.md file (produced by /plan-work-items) into Linear issues, one per slice, in a single target Linear team. Use when you want to publish work items as Linear issues, create implementation tickets to track in Linear, or push a broken-down plan into a Linear team. Requires a configured Linear MCP server and a target team. Reads the team's real workflow states, labels, Projects, and members and resolves every option against them before creating anything; defaults each issue to the team's initial state, unassigned, uncategorized, with no parent or Project unless you ask. Links within-file `Depends on` relationships as native Linear "blocked by" relations and annotates the source file so re-runs resume cleanly. Does not produce the work-items file itself — use plan-work-items first. Does not post to Jira — use work-items-to-jira. Does not post to GitHub — use work-items-to-issues.
> Builds a feature specification from scratch through a relentless, evidence-based interview that walks the design tree decision-by-decision, resolving dependencies as it goes. Use when the user wants to plan, design, scope, specify, or flesh out a new feature, capability, or system behavior before implementation. Produces a feature specification focused on system behaviors, not implementation detail. Does not refine or stress-test an existing plan — use iterative-plan-review. Does not document already-built features — use project-documentation. Does not research open-ended options before there is a feature to specify — use research.
> Convert a stakeholder summary markdown file into a single self-contained HTML executive report — bottom line and decision asks up front, supporting detail later — styled with a Test Double-derived palette and self-contained mermaid diagrams. Use when the user wants to turn a stakeholder summary, executive summary, or business summary into an HTML report, generate an HTML version of a summary doc, or produce a shareable HTML file from a summary markdown. Produces an HTML sibling file only; does not publish anything.
面向“学习任何知识”的通用导师型 skill。用于用户想学习新主题、制定学习计划、整理学习笔记、做课后复盘、生成项目任务书、做掌握度检查，或希望基于自己资料与外部权威资料进行中文导师式陪学时。默认采用“导师 + 项目教练”模式，以项目驱动和 Mastery Learning 推进；当用户未提供资料时，主动查找官方文档、原始资料、经典教材、权威机构材料与最佳实践，并区分事实依据与建议判断。
> Guidance for choosing the right protein binder design tool. (2) Planning a binder design campaign, (3) Understanding trade-offs between different approaches, (4) Selecting tools for specific target types. For specific tool parameters, use the individual tool skills (boltzgen, bindcraft, rfdiffusion, etc.).
> (1) Planning binding kinetics experiments, (2) Troubleshooting poor/no binding signal, (3) Interpreting kinetic data artifacts, (4) Choosing between SPR vs BLI platforms.
> End-to-end guidance for protein design pipelines. (2) Need step-by-step workflow guidance, (3) Understanding the full design pipeline, (4) Planning compute resources and timelines, (5) Integrating multiple design tools. For tool selection, use binder-design. For QC thresholds, use protein-qc.
Read analyst.json and detective.json, make all editorial decisions — what the blog argues, which findings matter, narrative arc and section structure. Runs after the Analyst/Imagineer, before the Designer. No visual design. Outputs editor.md (prose) and editor.json (structure with edt_xx IDs).
Read editor.md, editor.json, analyst.json, and designer.json. Resolve chart data from analyst data_tables. Build the final index.html with data-* traceability attributes. Pure implementation — no editorial or visual decisions, no raw data access.
Data Journalist Agent (Data2Story) — orchestrator: turn a dataset into a blog. Runs detective → analyst → editor → designer → programmer → auditor → inspector in sequence. Creates a versioned project folder for each run.
Read editor.md, editor.json, analyst.json, and designer.json. Resolve chart data from analyst data_tables. Build the final index.html with data-* traceability attributes. Pure implementation — no editorial or visual decisions, no raw data access.
Find a dataset for a Data2Story blog. Accepts a topic, a URL, or a DIP-style category. Downloads + validates against 4 completeness gates before handing off to /data2story-pro. Local-first: searches Economist/Pudding/TidyTuesday clones before going online. Supports --validate-only to audit a folder you already have.
This skill should be used whenever the user wants to develop, refine, or stress-test an idea, plan, design, research direction, product/business concept, argument, or any decision with more than one reasonable path — i.e. whenever they want a thinking partner rather than a quick answer. Trigger it when the user says things like "let's brainstorm", "help me think through this", "poke holes in my idea", "be my devil's advocate", "roast this idea", "challenge my assumptions", "sanity-check my plan", "what am I missing?", "I have a rough idea for…", or shares a half-baked concept and wants to make it better — even if they never use the word "brainstorm". It makes Claude a rigorous, anti-sycophantic sparring partner that researches just-in-time, drives the idea through Frame → Diverge → Converge → Pressure-test → Decide, asks sharp questions, and refuses to rubber-stamp. Do NOT use it for simple factual lookups, well-defined tasks with one correct answer, or when the user just wants direct execution of a clear instruction.
用于【AI科幻】题材下的 GoodNovel 平台输出任务。作为题材包装层、兼容入口与路由层，负责保留AI科幻入口、补充关系张力与现实调查边界，并明确要求优先强制加载并使用 `通用-输出GoodNovel版`。关键词：AI科幻GoodNovel版、英文平台、关系张力、调查悬疑。
用于【AI科幻】题材下的 B站 平台输出任务。作为题材包装层、兼容入口与路由层，负责保留AI科幻入口、补充视听化异常、互动讨论感、现实空间压迫与数据链边界，并明确要求优先强制加载并使用 `通用-输出B站版`。关键词：AI科幻B站版、B站、视听化、讨论感。
用于【AI科幻】题材下的 WebNovel 平台输出任务。作为题材包装层、兼容入口与路由层，负责保留AI科幻入口、补充追踪逻辑与跨文化可读边界，并明确要求优先强制加载并使用 `通用-输出WebNovel版`。关键词：AI科幻WebNovel版、跨文化悬疑、英文连载。
用于【AI科幻】题材下的七猫平台输出任务。作为题材包装层、兼容入口与路由层，负责保留AI科幻入口、补充直白短叙、普通人共情、生活化悬念与章末翻页边界，并明确要求优先强制加载并使用 `通用-输出七猫版`。关键词：AI科幻七猫版、七猫、直给反馈、追读。
用于【AI科幻】题材下的 My Fiction 平台输出任务。作为题材包装层、兼容入口与路由层，负责保留AI科幻入口、补充关系黏性与调查驱动边界，并明确要求优先强制加载并使用 `通用-输出My Fiction版`。关键词：AI科幻My Fiction版、英文追更、关系张力。
用于【AI科幻】题材下的今日头条平台输出任务。作为题材包装层、兼容入口与路由层，负责保留AI科幻入口、补充技术事件反转与互动驱动边界，并明确要求优先强制加载并使用 `通用-输出今日头条版`。关键词：AI科幻今日头条版、今日头条平台、开篇钩子、互动驱动、规则怪谈、中式悬疑。
用于【AI科幻】题材下的小红书平台输出任务。作为题材包装层、兼容入口与路由层，负责保留AI科幻入口、补充体感异常、凡人共情、移动端吸附与可分享感官瞬间边界，并明确要求优先强制加载并使用 `通用-输出小红书版`。关键词：AI科幻小红书版、小红书、体感、共情。
用于【AI科幻】题材下的微信订阅号平台输出任务。作为题材包装层、兼容入口与路由层，负责保留AI科幻入口、补充连续追更与社交传播边界，并明确要求优先强制加载并使用 `通用-输出微信订阅号版`。关键词：AI科幻微信订阅号版、公众号连载、微钩子、持续关注。
用于【AI科幻】题材下的出版社平台输出任务。作为题材包装层、兼容入口与路由层，负责保留AI科幻入口、补充出版审读友好度与现实调查质感边界，并明确要求优先强制加载并使用 `通用-输出出版社版`。关键词：AI科幻出版社版、传统出版、审稿友好、现实调查。
用于【AI科幻】题材下的新浪微博平台输出任务。作为题材包装层、兼容入口与路由层，负责保留AI科幻入口、补充短促抓点、话题切口、评论驱动、技术议题锚定与数据链边界，并明确要求优先强制加载并使用 `通用-输出新浪微博版`。关键词：AI科幻新浪微博版、微博、话题切口、评论驱动。
用于【AI科幻】题材下的番茄平台输出任务。作为题材包装层、兼容入口与路由层，负责保留AI科幻入口、补充数据链与压迫感边界，并明确要求优先强制加载并使用 `通用-输出番茄版`。关键词：AI科幻番茄版、番茄平台、强钩子、免费阅读。
用于【AI科幻】题材下的知乎平台输出任务。作为题材包装层、兼容入口与路由层，负责保留AI科幻入口、补充追踪逻辑与技术压迫感边界，并明确要求优先强制加载并使用 `通用-输出知乎版`。关键词：AI科幻知乎版、知乎盐选、逻辑链、讨论感。
用于【AI科幻】题材下的百度百家号平台输出任务。作为题材包装层、兼容入口与路由层，负责保留AI科幻入口、补充冷峻写实、信息抓力、搜索友好、日常物件线索化与顺滑扫读边界，并明确要求优先强制加载并使用 `通用-输出百度百家号版`。关键词：AI科幻百度百家号版、百家号、信息抓力、现实共鸣。