Research

Curiosity-driven web browsing with corpus-building — explore, synthesize, archive, and resume threads across sessions.

Universal deep research agent team. 13-agent pipeline for rigorous academic research on any topic. 7 modes: full research, quick brief, paper review, lit-review, fact-check, Socratic guided research dialogue, and systematic review with optional meta-analysis. Covers research question formulation, Socratic mentoring, methodology design, systematic literature search, source verification, cross-source synthesis, risk of bias assessment, meta-analysis, APA 7.0 report compilation, editorial review...

Orchestrator for the full academic research pipeline: research -> write -> integrity check -> review -> revise -> re-review -> re-revise -> final integrity check -> finalize. Coordinates deep-research, academic-paper, and academic-paper-reviewer into a seamless 10-stage workflow with mandatory integrity verification, two-stage peer review, and reproducible quality gates. Triggers on: academic pipeline, research to paper, full paper workflow, paper pipeline, end-to-end paper, research-to-publi...

12-agent academic paper writing pipeline. 10 modes (full/plan/outline/revision/revision-coach/abstract/lit-review/format-convert/citation-check/disclosure). 6 paper types, 5 citation formats, bilingual abstracts, LaTeX/DOCX-via-Pandoc/PDF output. Style Calibration + Writing Quality Check + Anti-Patterns with IRON RULE markers. Triggers: write paper, academic paper, guide my paper, parse reviews, AI disclosure, 寫論文, 學術論文, 引導我寫論文, 審查意見.

Given a research direction (e.g. "generated image detection", "对比学习", "neural machine translation"), research the literature and produce a NON-LINEAR development genealogy: a terminal ASCII tree (built from `--` connectors and text) plus a narrative tracing who proposed what, against which problem, what built on what, and which lines ran in parallel — from the founding work up to the latest. Use when the user wants to understand how a field evolved, not just a flat list or a theme-organized s...

论文投稿前的科研诚信自检（self-check）。从【数值数据异常】和【图像 PS 痕迹】两个方向， 检查 LaTeX / Word 论文中的常见造假信号——末位数字异常、Benford 偏离、等差数列、重复数据块/行、 GRIM 均值不自洽，以及图片的复制重用、拼接、克隆/涂抹等痕迹——最终导出 PDF 报告。 灵感来自"耿同学"的学术打假方法。当用户要检查论文数据/图片是否有造假风险、做投稿前诚信自查、 或要生成数据完整性/图像取证报告时使用。

Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal linking architecture, template recommendations (12 types), TL;DR drafts, citation capsule planning, information gain prompts, and multi-channel distribution plans. Briefs are optimized for Google rankings and AI citations (GEO/AEO). Use when user says "content brief", "blog brief", "write brief", "outlin...

Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.

Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal linking architecture, template recommendations (12 types), TL;DR drafts, citation capsule planning, information gain prompts, and multi-channel distribution plans. Briefs are optimized for Google rankings and AI citations (GEO/AEO). Use when user says "content brief", "blog brief", "write brief", "outlin...

Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.

Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal linking architecture, template recommendations (12 types), TL;DR drafts, citation capsule planning, information gain prompts, and multi-channel distribution plans. Briefs are optimized for Google rankings and AI citations (GEO/AEO). Use when user says "content brief", "blog brief", "write brief", "outlin...

SRE agent that does what you can't. Queries your observability stack. Finds root causes. Doesn't panic. Doesn't guess. Doesn't care about your feelings. Use for incident response, debugging, root cause analysis, or log analysis.

Structured research summarization agent skill for non-dev users. Handles academic papers, web articles, reports, and documentation. Extracts key findings, generates comparative analyses, and produces properly formatted citations. Use when: user wants to summarize a research paper, compare multiple sources, extract citations from documents, or create structured research briefs. Plugin for Claude Code, Codex, Gemini CLI, and OpenClaw.

Research and stress-test open-source project names, from collision checks to launch-ready decisions. Use when the user asks to name or rename a project, compare candidate names, screen GitHub or package namespace risk, verify language or mythology claims, or improve SEO/GEO clarity. Perform live web and registry research, separate brand from category descriptor, classify collisions, and return one evidence-backed recommendation.

Writes neutral, verifiable, encyclopedic prose following Wikipedia's core content policies and manual of style - NPOV, inline citations, notability-backed claims, and a strict ban on promotional language. Use when someone asks "write this like a Wikipedia article", "draft a Wikipedia page for this company or person", "make this neutral and encyclopedic", or "why does my article draft keep getting rejected". Do NOT use for persuasive or opinion writing - use op-ed-writer instead; for thesis-dr...

Structures and writes authoritative B2B whitepapers - a standalone executive summary, a data-sized problem statement, methodology, evidence-driven findings, recommendations, and a soft call to action - flagging every claim that needs a real citation. Use when a marketer asks "write a whitepaper on this topic", "turn our research into a lead-gen asset", "make this credible enough for executives", or a draft reads like a product pitch instead of analysis. Do NOT use for customer-story-driven pr...

Finds unmet market gaps by ranking jobs-to-be-done on importance versus satisfaction, overlaying them against current solutions and workarounds, and validating that each gap is real, winnable, and worth winning. Use when someone asks "where are the gaps in this market", "what's underserved here", "where should we play next", or is hunting for product, feature, or market-entry opportunities. Do NOT use for profiling competitors and building battle cards - use competitive-intelligence instead; ...

Synthesizes interview notes, surveys, support tickets, and analytics into evidence-based user personas that drive design decisions, with every claim traced to source data. Use when someone asks "build personas from our research", "turn these interview notes into personas", "how many personas do we need", or "are our personas evidence-based". Do NOT use for sales-targeting ideal customer profiles with filterable firmographics and buying committees - use icp-persona-builder instead. Do NOT use ...

Turns many sources into a decision-ready synthesis - atomic claims clustered into named themes, surfaced tensions between sources, gaps no source answers, and explicit so-what/now-what implications with confidence ratings. Use when someone says "synthesize this research", "what do all these reports agree on", "pull the themes out of these articles", or has a pile of sources and needs conclusions rather than source-by-source summaries. Do NOT use for synthesizing user interview transcripts - u...

Turns synthesized research findings into a crisp stakeholder readout - so-what up front, 3-5 confidence-tagged findings each following the finding-evidence-implication rule, and owned recommendations. Use when someone says "present these research findings", "turn this study into a readout for leadership", "our research isn't landing with the product team", or needs a deck or brief that gets findings acted on. Do NOT use for building a narrative around quantitative metrics and charts - use dat...

Designs a rigorous primary research protocol for collecting new data - research question, hypotheses, method selection, sampling with a power analysis, instrument design, a named control for every bias threat, and a pre-specified analysis plan. Use when someone asks "design a study to test this", "how many respondents do I need", "should this be a survey or interviews", or must produce defensible first-hand evidence rather than cite existing work. Do NOT use for synthesizing already-published...

Runs a systematic prior-art search - feature decomposition into claim elements, CPC/IPC classification plus keyword vocabulary, patent databases AND non-patent literature, forward and backward citation walks - and maps results into claim charts with a novelty assessment and a documented search log. Use when someone asks "is my invention novel", "has anyone already patented this", "find prior art against this claim", or is deciding whether a filing or an invalidity argument is worth pursuing. ...

Builds conversion funnels from raw event data with drop-off attribution, segment comparison, and significance testing, and delivers a filled funnel table with a diagnosed bottleneck and next action. Use when someone asks "where are users dropping off", "why did checkout conversion fall this week", "build a signup-to-activation funnel", or "is mobile converting worse than desktop". Do NOT use for rewriting page copy or layout to lift a known weak step - use landing-page-cro instead; for decomp...

Designs an expert-interview package - sourcing criteria for the right experts, a funneled discussion guide with timing, open-then-probe question design, laddering, and a neutral probe kit - that extracts honest insight without leading the witness. Use when someone asks "help me write questions for an expert call", "build a discussion guide", "prep me for this expert network interview", or is planning customer-development or domain-expert conversations. Do NOT use for designing a full data-col...