Agent skill · research science · sickn33
research-prompt
Turn vague research needs into one precise deep-research prompt with context and output criteria.
Why this skill is useful
Provides a structured approach to transforming vague research needs into precise prompts, ensuring comprehensive coverage and context that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Research Prompt When to Use Use when the user wants a deep-research brief or researcher prompt. Use when a vague research question needs to become one precise self-contained paragraph. Goal: turn a vague research need into ONE self-contained paragraph that a researcher with zero prior knowledge of the project can act on with zero back-and-forth. Rules One paragraph. No headers, no bullet list in the deliverable. Prompt the job, not the topic. Give search handles (timeframe, ranking, source type, decision logic) — not just a subject. Assume zero prior knowledge. Write for a researcher who has never heard of the project. Open by explaining, in plain English, what the project/product is, why it exists, and the current situation — so they understand what's going on, what we need, and why we need it. Lead with the goal + decision. Right after that explainer, state the single question the research must answer and the decision/use it informs. Embed all context. Names, dates, product, prior known facts, constraints. The researcher must not need to ask anything or guess. Number the sub-questions inline (1, 2, 3…) so coverage is explicit. Keep to 3–6. One mission per prompt — don't cram unrelated questions. State constraints. What to include, what to avoid (e.g. "only non-Chinese competitors", "no marketing fluff"). Source hierarchy. Prefer primary sources (official docs, GitHub, papers, filings, changelogs); forums/X/Reddit are weak signal only, never factual proof. Contradiction handling. If sources conflict, separate confirmed facts / inference / unresolved uncertainty — don't force fake consensus. Flag low-confidence claims for verification. Completion bar (define "done"). Don't stop at the first plausible answer. Corroborate each key claim with multiple independent primary sources where they exist; where sources are scarce, say so explicitly instead of padding. Keep going until every numbered sub-question is covered to this bar. Gap round before finishing. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/research-prompt