研究与知识
研究、检索、摘要和知识工作
Skills 列表
keyword-research
When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata, see metadata-optimization. For auditing current keyword performance, see aso-audit.
appeekyapp-marketing-context
When the user wants to create or update their app marketing context document. Also use when the user mentions "app context", "marketing brief", "app positioning", or when starting any ASO or app marketing project. This is the foundation skill — all other skills check for this context first.
appeekylocalization
When the user wants to localize their App Store listing for international markets. Also use when the user mentions "localization", "translate my app", "international markets", "expand to new countries", "localize metadata", or "which countries should I target". For keyword research in specific markets, see keyword-research. For metadata writing, see metadata-optimization.
appeekyapp-launch
When the user wants to plan a launch strategy for a new app or major update. Also use when the user mentions "app launch", "launch plan", "launch checklist", "pre-launch", "launch day", or "how to launch my app". For ongoing ASO after launch, see aso-audit. For paid acquisition during launch, see ua-campaign.
appeekyandroid-aso
When the user wants to optimize their Google Play Store listing — title, short description, full description, keywords, ratings, or Play Store-specific features. Use when the user mentions "Google Play", "Android", "Play Store", "Play Console", "short description", "full description indexed", "Google Play ASO", or wants Google Play-specific keyword, creative, or ratings strategy. For iOS App Store optimization, see aso-audit and metadata-optimization.
appeeky
web-perf
使用 Chrome DevTools MCP 分析网页性能。测量核心网页指标（LCP、INP、CLS）和辅助指标（FCP、TBT、速度指数），识别渲染阻塞资源、网络依赖链、布局偏移、缓存问题和可访问性差距。当被要求审计、分析、调试或优化页面加载性能、Lighthouse 分数或网站速度时使用。倾向于从当前文档中检索，而非依赖预训练知识。
cloudflaredurable-objects
创建和审查 Cloudflare Durable Objects。用于构建有状态协调（聊天室、多人游戏、预订系统）、实现 RPC 方法、SQLite 存储、告警、WebSocket，或审查 DO 代码的最佳实践。涵盖 Workers 集成、wrangler 配置和 Vitest 测试。倾向于从 Cloudflare 文档中检索而非依赖预训练知识。
cloudflare
team-topologies
Organize business and technology teams for fast flow using Skelton & Pais''s "Team Topologies". Use when the user mentions "team topologies", "Conway''s law", "platform team", "stream-aligned team", "team boundaries", "cognitive load", "how should we split teams", "who owns this service", "team dependencies", or "reorg". Also trigger when reorganizing engineering teams, aligning team and service boundaries, splitting a monolith and deciding ownership, reducing cross-team handoffs, or designing an internal platform. Covers the four team types, three interaction modes, the inverse Conway maneuver, and fracture planes. For bounded contexts, see domain-driven-design. For dependency direction in code, see clean-architecture.
wondelaiworkers-best-practices
审查并编写符合生产最佳实践的 Cloudflare Workers 代码。在编写新的 Worker、审查 Worker 代码、配置 wrangler.jsonc 或检查常见的 Worker 反模式（流处理、未处理的 Promise、全局状态、密钥、绑定、可观测性）时加载。倾向于从 Cloudflare 文档检索，而非依赖预训练知识。
cloudflare
asd-ste100
Use when English text must be parsed without a human to resolve ambiguity — tool descriptions, error messages, inter-agent instructions, system prompts, status reports — and misreading has a real cost, or when text reads as dense, hedged, or easy to misparse. Triggers: disambiguate, STE100 rewrite, apply Simplified Technical English, plain-language rewrite, controlled-language rewrite, rewrite so an agent cannot misread this. Not for creative or marketing copy.
danyuchn
documentation
Creates, structures, and reviews technical documentation following the Diátaxis framework (tutorials, how-to guides, reference, and explanation pages). Use when a user needs to write or reorganize docs, structure a tutorial vs. a how-to guide, build reference docs or API documentation, create explanation pages, choose between Diátaxis documentation types, or improve existing documentation structure. Trigger terms include: documentation structure, Diátaxis, tutorials vs how-to guides, organize docs, user guide, reference docs, technical writing.
mcollina
microsoft-code-reference
Find working code samples, verify API signatures, and fix Microsoft SDK errors using official docs. Use whenever the user is writing, debugging, or reviewing code that touches any Microsoft SDK, .NET library, Azure client library, or Microsoft API—even if they don't ask for a "reference." Catches hallucinated methods, wrong signatures, and deprecated patterns. If the task involves producing or fixing Microsoft-related code, this is the right skill.
microsoftdocsmicrosoft-skill-creator
Create agent skills for Microsoft technologies using official documentation. Use whenever the user wants to build, generate, or scaffold a skill for any Microsoft technology (Azure, .NET, M365, VS Code, Bicep, etc.)—even phrased casually like "make a skill for Cosmos DB." Investigates the topic via official docs, then generates a hybrid skill with essential knowledge stored locally and dynamic lookups for depth.
microsoftdocsmicrosoft-docs
Understand Microsoft technologies by querying official documentation. Use whenever the user asks how something works, wants tutorials, needs configuration options, limits, quotas, or best practices for any Microsoft technology (Azure, .NET, M365, Windows, Power Platform, etc.)—even if they don't mention "docs." If the question is about understanding a concept rather than writing code, this is the right skill.
microsoftdocs
code-review-skill
Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C#/.NET, Kotlin, Swift, Dart, Flutter, NestJS, C/C++, Zig, CSS/Less/Sass, Qt, and more. Covers architecture review, performance review, security audit, code quality anti-patterns, and common bugs across all ecosystems. Use when: reviewing pull requests, conducting PR reviews, code review, reviewing code changes, establishing review standards, mentoring developers, architecture reviews, security audits, performance reviews, checking code quality, finding bugs, giving feedback on code.
awesome-skills
stripe-docs
Use when the user or agent needs to read, search, or look up Stripe documentation or API reference. Prefer this over curl or WebFetch for any docs.stripe.com content.
stripe
android-aso
When the user wants to optimize their Google Play Store listing — title, short description, full description, keywords, ratings, or Play Store-specific features. Use when the user mentions "Google Play", "Android", "Play Store", "Play Console", "short description", "full description indexed", "Google Play ASO", or wants Google Play-specific keyword, creative, or ratings strategy. For iOS App Store optimization, see aso-audit and metadata-optimization.
eronredconnect-recommend
Use this skill when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform, multi-vendor store, gig platform, or subscription platform, needs to pay out sellers, vendors, or providers, mentions split payments, revenue sharing, multi-party payments, or similar payment distribution concepts, provides a company URL or business description for a recommendation, builds SaaS that routes money between parties (for example, POS, booking, invoicing — not operational SaaS without payment routing), asks about onboarding or KYC for merchants, sellers, and vendors, mentions connected account Dashboard or responsibility configurations, or asks about payment flows, white-label payments, or embedded payments.
stripedrive-motivation
使用自主性、掌控感和目标感（AMP）为产品和团队设计激励系统。当用户提到“内在动机”、“游戏化不起作用”、“奖励不起作用”、“自主性”、“掌控感”、“目标驱动”、“我的团队缺乏参与感”或“如何激励他人”时使用。也适用于设计入职进阶、修复失效的游戏化，或构建维持高绩效的团队结构。涵盖为什么胡萝卜加大棒会失败，以及如何构建进步系统。如需习惯养成型产品循环，请参见 hooked-ux。如需留存行为设计，请参见 improve-retention。
wondelaiddia-systems
通过理解存储引擎、复制、分区、事务和一致性模型来设计数据系统。当用户提到“数据库选择”、“应该用哪个数据库”、“SQL还是NoSQL”、“复制延迟”、“分区策略”、“一致性与可用性”、“流处理”、“ACID事务”、“最终一致性”、“我的查询在大规模下变慢”或“副本间数据不一致”时使用。在选择数据存储、设计数据管道或调试分布式系统一致性问题时也会触发。涵盖数据模型、批处理/流处理和分布式共识。关于系统设计，请参见system-design。关于弹性，请参见release-it。
wondelaiapp-marketing-context
当用户需要创建或更新应用营销上下文文档时使用。在用户提及“app context”、“marketing brief”、“应用定位”，或启动任何 ASO 及应用营销项目时也可触发。这是核心基础 Skill —— 所有其他 Skill 都会优先校验该上下文。
eronredlocalization
当用户希望将其 App Store 应用商店页面进行多语言/跨国本地化时使用。当用户提到“本地化”、“翻译我的应用”、“海外/国际市场”、“拓展新国家/地区”、“本地化元数据”或“我应该先出海哪些国家”时，也可触发此 Skill。如需针对特定市场进行关键词调研，请参考 keyword-research。如需编写元数据，请参考 metadata-optimization。
eronredapp-launch
当用户想要为新 App 或重大版本更新规划上线发布策略时使用。当用户提到“App 上线”、“发布计划”、“上线清单”、“预热”、“上线首日”或“如何发布我的 App”等词汇时也可触发。关于上线后的日常 ASO 优化，请参考 aso-audit。关于上线期间的付费买量，请参考 ua-campaign。
eronred
setup-arxiv-mcp
Guide for setup arXiv paper search MCP server using Docker MCP
neolabhq