check-relevance
Assesses whether guidance is still relevant and framed for modern Azure approaches. Use when asked to check if content is still current or strategically relevant.
422 repo starsObserved in 1 repos
Research
Research skills
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
research-synthesizer
OwnPilot official general skill for turning mixed research material into concise, sourced briefs, comparisons, decisions, and next steps. Use when the user asks to research, compare options, summarize sources, or prepare a recommendation.
420 repo starsObserved in 1 repos
Research
lazyweb
Lazyweb is the design-evidence skill for AI coding agents. Use it before designing, critiquing, or changing product UI when the agent needs real app screenshots, competitor references, best practices, quick examples, creative cross-category ideas, paywall optimization guidance, or mobile growth and monetization A/B test context. It can also route explicit requests to update the local Lazyweb skill pack. It routes to the right Lazyweb mode and tells the agent to use Lazyweb MCP tools instead of guessing from generic training data.
419 repo starsObserved in 1 repos
Research
lazyweb-quick-search
Use the Lazyweb search MCP tool directly for quick industry references before designing or changing UI. Does not generate a report. Use when the agent needs a lightweight best-practice check from real app screenshots, wants to inspect search coverage, or should grab a few references before building. Trigger on: "quick search", "search Lazyweb", "use lazyweb_search", "quick industry references", "check examples before designing", "look up UI references first".
419 repo starsObserved in 1 repos
Research
question-refiner
Use when a research question is still vague and must be clarified into a structured deep-research brief before actual literature research or execution. Skip this if the user already has a concrete paper draft or a ready-to-run research specification.
415 repo starsObserved in 2 repos
Research
research-lead-sidecar
Use when the user wants multi-agent division of labor for research-led work and the lead should stay on the critical path while 1-2 bounded sidecars handle low-coupling tasks. Do not use this for tiny tasks, fully sequential debugging, or overlapping refactors.
415 repo starsObserved in 2 repos
Research
adversarial-research-analyst
Adversarial research analysis framework that uses structured Bull/Bear/Arbiter debates to help users make better research judgments. Maintains a belief graph as backend engine, applies statistical calibration discipline, tracks phase transitions, and detects biases. MANDATORY TRIGGERS: Use this skill whenever the user asks to analyze a research paper, evaluate a research direction, make a strategic research decision, assess technology trends, review academic papers, or asks "what should I work on / invest in / bet on" in a research context. Also trigger when the user mentions "paper review", "research direction", "trend analysis", "technology forecast", "belief update", or wants structured pro/con analysis of any technical topic. Even casual requests like "what do you think about this paper" or "is X going to be important" should trigger this skill.
415 repo starsObserved in 1 repos
Research
publish-research-site
Turn a thesis, proposition, trend, question, or explainer topic into a citation-backed, image-rich, interactive website and deploy it with Vercel CLI. Use when the user asks to research a claim deeply, generate visuals, build a shareable web experience, publish a microsite, create an interactive story/report, or deploy a researched site to Vercel.
415 repo starsObserved in 1 repos
Research
android-architecture-reference
Android 架构、依赖注入、数据层、测试规范官方参考。涵盖 UDF/MVI 模式、Hilt/Dagger、Room、Paging、 DataStore、WorkManager、ViewModel、测试策略等。安卓开发第一要义：参考官方文档和案例！ Triggers: "Android 架构", "MVVM", "MVI", "UDF", "Hilt", "Dagger", "Room", "Paging", "ViewModel", "WorkManager", "DataStore", "测试", "架构设计", "DI", "依赖注入"
412 repo starsObserved in 1 repos
Research
evo-memory
Manages persistent research memory across ideation and experimentation cycles. Maintains two stores: Ideation Memory M_I (feasible/unsuccessful directions) and Experimentation Memory M_E (reusable strategies for data processing, model training, architecture, debugging). Three evolution mechanisms: IDE (after research-ideation), IVE (after experiment failure — classifies failures as implementation vs fundamental), ESE (after experiment success — extracts reusable strategies). Use when: updating memory after completing research-ideation cycles or experiment pipelines, classifying why a method failed (implementation vs fundamental failure), starting a new research cycle needing prior knowledge, user mentions 'update memory', 'classify failure', 'what worked before', 'research history', 'evolution'. Do NOT use for running experiments (use experiment-pipeline), debugging experiment code (use experiment-craft), or generating ideas (use research-ideation).
411 repo starsObserved in 3 repos
Research