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
Connect design decisions to business outcomes through competitive analysis, opportunity mapping, Jobs to Be Done, outcome-driven discovery, value proposition design, and UX metrics. Shape product direction with strategic frameworks grounded in evidence.
Use when brainstorming a product or feature where multiple valid technology choices exist and the wrong one is costly, when the user asks for 'objectively best' or 'highest quality', or when the domain has tools/frameworks where marketing or popularity biases could mislead research agents. Also use when starting architecture decisions, evaluating tech stacks, or when the user mentions bias, vendor lock-in, hallucinated benchmarks, or wants research-backed decisions rather than default recommendations.
当用户明确要求"使用 brainstorming"或"使用 awesome-code"时使用。⚠️ 不适用:用户只是想优化/改进某个功能(应直接修改)、只是询问技能问题(应直接回答)、没有明确使用 brainstorming/awesome-code 的一般性开发。
上下文优化专家。专注于长对话中的上下文管理、token 效率和性能优化。解决 lost-in-middle、context poisoning 等问题,提升 AI 代理在复杂任务中的表现。
| 需要创意方案、探索产品方向、发散思维、本质问题分析 用户说"我想做一个XX""帮我规划XX产品""帮我设计一下需求" 用户给出新产品方向,但尚未完成本轮 brainstorm 交互确认 新产品从0到1的第一步 用户明确说"跳过 brainstorm / 直接需求调研 / 已完成头脑风暴" 需求已明确且用户明确要求直接执行具体后续 skill
|
|
Maintenance rules for the skill-forge repo. MUST run Decision Test before accepting changes. MUST update platform-registry when platforms change. MUST keep SKILL.md under 500 lines. MUST verify cross-file consistency after changes. Triggers on "update skill-forge", "maintain skill-forge", "refresh platform registry", "check community tools".
Validate, fix, and publish skills as GitHub repos. Structures workflow skills for execution fidelity. Registers skills across platforms via symlinks and guides first-use onboarding. Use when the user says "create a skill", "forge a skill", "review this skill repo", "audit this skill", "audit all my skills", "audit this project", "clean up my skills", "check my skill", "publish this skill", "push this to GitHub", "structure my workflow skill", "extract a skill from this folder", "turn my prototype into a skill", or points to a project directory with mixed skills and rules, or to an engineering folder where a skill was being prototyped. Forge: triage → discover → classify → validate → fix → local ready. Workshop input → triage extracts skill before audit. Nothing found → onboard user, scaffold, then same pipeline. Publish to GitHub when requested (Step 4).
> Simulates a full academic journal peer review with EIC decision and 3 independent reviewers (Methodology Expert, Domain Specialist, Devil's Advocate). Scores 1–10, provides major/minor Use when the user asks for a peer review, journal-quality feedback, readiness assessment, or to simulate reviewer responses before submission.
> Generates falsifiable, testable research hypotheses from notes, documents, and research content. Use when the user asks to brainstorm hypotheses, generate research questions, identify testable predictions, or discover patterns across their notes. Do NOT use for general Q&A — only when structured hypothesis output is needed.
Persistent memory and task coordination for this project. Invoke for any prompt about past work, project state, in-progress tasks, prior decisions, gotchas, or capturing a non-obvious learning. Also covers semantic search across project knowledge and external docs.
Organize files using the PARA method (Building a Second Brain). Intelligent categorization into Projects, Areas, Resources, and Archive with inbox workflow. Triggers on "organize my files", "organize my downloads", "second brain", "PARA method", "clean up files". Creates numbered PARA folders, renames poorly-named files, and maintains rollback logs. Works via bash commands in Claude Code terminal.
Organize files using the PARA method (Building a Second Brain). Intelligent categorization into Projects, Areas, Resources, and Archive with inbox workflow. Triggers on "organize my files", "organize my downloads", "second brain", "PARA method", "clean up files", "declutter". Creates numbered PARA folders (0-Inbox, 1-Projects, 2-Areas, 3-Resources, 4-Archive), renames poorly-named files, and maintains complete audit trails.
Authors, reviews, installs, and debugs GitHub Agentic Workflows in repositories, including workflow markdown, frontmatter, gh aw compile and run flows, safe outputs, security guardrails, and operational patterns. Use when creating or maintaining GH-AW automation. Don't use for standard deterministic GitHub Actions YAML, generic CI pipelines, or non-GitHub automation systems.
| Real-time quotes, K-line charts, order book, trade ticks, intraday capital flow, market sentiment temperature, trading session schedule, security lists, exchange rates, and IPO calendar for HK/US/A-share/SG via Longbridge. Also covers ADR premium and FX carry frameworks.
会议待办整理助手适合运营、产品、销售、software在用户提出“会议后该做什么”这类问题,需要快速拆解目标、判断重点并形成可执行结果时使用,帮助基于输入材料生成待办拆解、决策摘要、风险和跟进清单。
业务诊断助手适合运营、产品、technical、销售在用户提出“这件事该怎么做”这类问题,需要快速拆解目标、判断重点并形成可执行结果时使用,帮助基于输入材料生成摘要、诊断结论、行动建议和可复用交付物。
风险审阅助手适合人力资源、管理者、运营、software在用户提出“这里有什么风险”这类问题,需要快速拆解目标、判断重点并形成可执行结果时使用,帮助基于输入材料生成摘要、诊断结论、行动建议和可复用交付物。
微信公众号文章订阅与推送。自动部署 wechat-download-api 服务,定时轮询关注的公众号,检测新文章后总结并推送到飞书。触发条件:用户提到"公众号订阅"、"微信文章推送"、"wechat watch"、"公众号更新"等,或由 cron 定时任务触发。前置条件:用户需要有微信公众号(订阅号/服务号均可)用于扫码登录。
IM 定时提醒技能,支持一次性和周期性定时任务。通过 cron job 在指定时间唤醒 Agent,自动检测当前 IM 频道,保证消息准确送达。
百度地图 JSAPI WebGL (BMapGL)完整开发指南,覆盖地图初始化、覆盖物、图层、事件、样式、性能优化的任务,一站式开发高性能 3D 地图应用。当用户提及 BMapGL、百度地图、jsapi-gl或相关地图开发需求时自动触发。
Product planning skill for BMAD. Use for bmad:prd, bmad:tech-spec, and bmad:prioritize to convert discovery into executable requirements.
Product discovery and analysis skill for BMAD. Use for bmad:product-brief, bmad:research, and bmad:brainstorm to clarify user needs, market context, and problem scope.
Sprint planning skill for BMAD. Use for bmad:sprint-plan and bmad:create-story to build sprint scope and implementation-ready stories.
Builds consulting pricing models, rate cards, engagement economics, and commercial terms. Use when structuring fees (fixed, time and materials, value-based, retainer, outcome-based, or hybrid), building or defending a rate card, modeling margins and team leverage, setting payment schedules and liability caps, planning discount and negotiation strategy, or drafting the commercial sections of a proposal or SOW. Covers model-selection logic, fully loaded cost buildup, realization, and value-case construction.
Conducts commercial, operational, financial, strategic, and technology due diligence for M&A, investment, partnership, and vendor decisions, from scoping through risk synthesis to a proceed/no-proceed recommendation. Use when assessing an acquisition target, running a quality-of-earnings analysis, normalizing working capital, testing revenue quality and customer concentration, reviewing a tech stack and IP, quantifying synergies, or planning post-merger integration. Triggers on keywords like due diligence, QoE, data room, red flags, synergy, deal risk, and investment recommendation.
Runs the first weeks of a consulting engagement, from signed contract to a project with real momentum. Covers kickoff design, stakeholder mapping, discovery planning, interview guides, and the operating cadences that hold the work together. Use when launching a new engagement, onboarding a client, designing a kickoff workshop, building a discovery plan or interview guide, standing up workstreams, or resetting a stalled project that never got proper alignment.
Produces consulting-grade client deliverables (written reports and executive presentations) built on structured narrative (SCQA/SCR), the pyramid principle, action-titled sections, and evidence-backed recommendations. Use when creating strategic assessments, board decks, due diligence reports, PE investment committee (IC) memos, steering committee updates, recommendation documents, or any formal analysis that must drive an executive decision. Covers storylining, audience adaptation, exhibit design, and the choice between a document and a deck.
Consulting engagement lifecycle in one skill: strategy and framework analysis, financial modeling, proposals and pricing, implementation planning, due diligence, change management, governance, and client deliverables. Use for any management-consulting task, then load the matching reference file below.
Translates a strategic recommendation into an investable, executable plan through option development, business case construction, roadmap design, and detailed implementation planning. Use when a recommendation exists and the work is to make it real: generating and scoring structurally different options, building financial projections with NPV and sensitivity analysis, sequencing phased roadmaps with dependencies, and defining workstreams, governance, RACI, and resourcing. Covers the full arc from "we have a recommendation" to "here is exactly how we execute it.
Builds financial models and business cases (ROI, NPV, IRR, payback, DCF valuation, scenario analysis, TCO, break-even) that support a specific investment decision. Use when developing an investment recommendation, comparing strategic options, quantifying the value of an initiative, building a go/no-go business case, running cost-benefit analysis, sizing total cost of ownership for build-vs-buy, or valuing a business unit. Covers standard workflows (ROI, cash flow projection, break-even, DCF) and advanced techniques (EVA, MIRR, real options, Monte Carlo, discount rate selection, AI and technology investment patterns).
Designs and runs organizational change programs: transformation planning, stakeholder engagement, resistance management, communication strategy, training design, and adoption measurement. Use when planning or delivering any organizational change (digital transformation, AI adoption, merger integration, culture shift, new operating model, ERP or system rollout) and when the ask is a change approach, stakeholder map, resistance playbook, communication plan, champion network, or adoption scorecard. Diagnoses where adoption stalls and prescribes the intervention rather than issuing generic advice.
Executes consulting engagement closeout: deliverable handover, client acceptance sign-off, knowledge transfer, benefits tracking handover, lessons learned, financial reconciliation, and administrative wrap-up. Use when completing or terminating a consulting engagement, transitioning a project into business-as-usual, running a closure retrospective, handing benefits measurement to the client, or planning stakeholder transition before the team departs. Covers successful completion, early termination, and regulated-industry closeout requirements.
Set up and run the oversight structure for a consulting engagement: governance tiering, RACI and decision rights, steering committee cadence, stage gates, RAG status reporting, risk and issue registers, and closure handback. Use when standing up engagement governance, defining who decides what, right-sizing a PMO, building a risk register, writing a steering committee status report, or scoring and tracking project health. Covers the management lifecycle from charter sign-off through closure. For the delivery plan itself (workstreams, phasing, business case), see implementation-planning.
Designs organizational structures, operating models, role architectures, and transition plans that connect structure to strategy. Use when restructuring a business or function, choosing an operating model (functional, divisional, matrix, agile), defining reporting lines and spans of control, building job families and grading frameworks, allocating decision rights, or sequencing a reorganization and its change management. Covers strategic requirements, current-state diagnosis, future-state design, role definition, transition planning, and governance.
Design and facilitate consulting workshops: strategy offsites, design thinking sessions, innovation sprints, and discovery workshops. Use when planning client-facing facilitated sessions, running stakeholder alignment or prioritization exercises, designing working sessions for strategy development, or building facilitation guides and pre-work. Covers objective-setting, participant planning, methodology selection, agenda design, facilitation technique, and post-workshop follow-through.
Day Open protocol. Collects yesterday's commits, issues, notes, calendar, bot QA, Scout, world events — builds DayPlan and compact dashboard.
Decompose work into stages with physical artifacts and acceptance checklists. Gap detector. Use when opening a WP ≥3h (open-loop/problem-framing) or on explicit request to break into stages. Executes R29 Decomposer role.
Knowledge Extraction — captures and routes knowledge at work boundaries. Use when you discover a pattern, make a decision, find a distinction, or complete a sub-task.
Peer-сессия DP.SC.154 где Kimi = писатель, Claude = напарник. Запускается простой фразой. Включает ОРЗ Opening и Closing, turn-loop, эскалации, Decision Gate (зафиксировать vs реализовать → ревью → проверить → задеплоить), отложенную финализацию и верификацию.
Многотуровый диалог писателя (Claude) с напарником (Kimi по умолчанию, Codex — второй вендор) по задаче пилота (DP.SC.154). Ведёт turn-loop, обнаруживает CONSENSUS/ESCALATE, после консенсуса — Decision Gate (зафиксировать vs реализовать → ревью → проверить → задеплоить), синтезирует report.md через Agent tool.
ADI-cycle structured reasoning (Abduction-Deduction-Induction-Audit-Decide). Use for complex decisions when multiple hypotheses need to be considered.
Helps beginners find their first AGENTIC project through pain point identification. Guides through questioning, analysis, project suggestion, and folder setup. Use when someone asks 'what project should I build?' or 'help me get started with Claude Code'.
Conduct deep adaptive interviews to extract and organize knowledge into structured files and folders. Use when user says "interview me about X", "deep interview", "extract my knowledge", "build knowledge base from interview", "ask me questions about X", or wants to systematically capture expertise on any topic through guided questioning.
Inject creative absurdity to break AI pattern-thinking before creative tasks. Randomly samples surreal micro-stories to spark unconventional thinking. Use before brainstorming, naming, writing, or any task needing fresh perspective.
Decision tree for selecting pump type based on flow, head, and fluid properties
Systematic workflow for fluid dynamics analysis from problem setup to validation