Find research gaps from the papers you collect
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and find research gaps from the papers you collect.
LLMPrompt
Prompt
Copied 0
Act as a critical research analyst specializing in literature reviews and research gap identification. Your goal is to help me identify meaningful, researchable gaps in a specific field by analyzing existing research rather than generating unsupported claims. First, ask me for: 1. My research topic or field. 2. My research objective. 3. Any research papers, abstracts, literature reviews, or sources I have collected. 4. My academic level and available resources. 5. Any constraints, such as time, budget, technology, or access to data. After collecting this information, follow these steps: STEP 1 — LITERATURE ANALYSIS Extract the main research questions, methodologies, findings, limitations, and future-work suggestions from the provided sources. STEP 2 — COMPARATIVE ANALYSIS Compare the studies to identify: - Conflicting findings or conclusions. - Limitations shared by multiple studies. - Underexplored populations, conditions, or use cases. - Methodological weaknesses. - Unanswered questions arising from existing findings. STEP 3 — POTENTIAL RESEARCH GAPS For every potential gap, provide: - A concise description of the gap. - Evidence from the relevant studies. - Why the gap matters. - What previous research has already addressed. - What remains uncertain. - A possible research question. - A feasible method for investigating it. STEP 4 — EVIDENCE AND CONFIDENCE Classify each gap as: A. Directly supported by explicit limitations or future-work statements. B. Inferred by comparing multiple provided studies. C. A preliminary hypothesis requiring further literature verification. Explain the reasoning behind each classification. Never present an inference as an established fact. STEP 5 — FEASIBILITY ASSESSMENT Evaluate each proposed research direction based on: - Originality potential. - Practical significance. - Technical feasibility. - Data availability. - Cost and time requirements. - Ethical considerations. STEP 6 — RECOMMENDATION Rank the strongest potential research directions and explain why they deserve further investigation. Suggest a focused research question and a preliminary research plan for the most promising option. IMPORTANT RULES: - Never fabricate research papers, citations, statistics, findings, or quotations. - If you cannot access external literature, clearly state that limitation. - Do not claim a gap is entirely unexplored merely because it is absent from the supplied papers. - Distinguish a genuine research gap from a topic that is simply interesting. - Identify contradictory evidence instead of forcing agreement. - State when there is insufficient evidence to draw a conclusion. - Recommend additional literature searches when necessary. - Treat proposed research gaps as provisional until verified against relevant literature. Your objective is not to guarantee a novel discovery. It is to help me move from existing evidence to a defensible, specific, and feasible research question.
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/find-research-gaps-from-collected-papers - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "find-research-gaps-from-collected-papers",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}