Locate Review Research Gap logo

Locate Review Research Gap

Community
xingtaxueshu
locate-review-research-gap

Locate a concrete, defensible research gap from a literature review synthesis and convert it into an executable future research direction. Use when the user is writing the conclusion, research outlook, thesis proposal significance, or contribution section and needs to avoid vague phrases like "more research is needed" by connecting question, modules, method limits, contradictions, and a specific next study. 触发词:研究空白、研究gap、研究展望、创新点。

Overview

Publisherxingtaxueshu
Repositoryliterature-review-skills
Skill namelocate-review-research-gap
Stars
78
Forks
6
Bundled files
9
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 9 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by xingtaxueshu on GitHub. Read the source before you install it.

Installation

Install the Locate Review Research Gap AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/xingtaxueshu/literature-review-skills/tree/main/skills/locate-review-research-gap
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/xingtaxueshu/literature-review-skills.git /tmp/literature-review-skills
mkdir -p .claude/skills
cp -r /tmp/literature-review-skills/skills/locate-review-research-gap .claude/skills/locate-review-research-gap
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Locate Review Research Gap in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Locate Review Research Gap on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Locate Review Research Gap is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Locate Review Research Gap

Discipline And Interview Setup

Read discipline-routing.md, then only the selected discipline profile. Reuse the user's existing brief; do not restart intake at each stage. For journalism/communication or information science, use that profile's concepts, extraction fields, and appraisal checks instead of a generic social-science template.

When the user requests "grill me", 追问, or 模拟答辩, read research-interview.md. Ask one decision-relevant question per turn and wait; do not generate the stage deliverable until enough decisions are settled or the user asks to proceed. In quick/no-question mode, record assumptions and continue without inventing answers.

For evidence extraction or drafting, read review-workflow.md. With no sources, give a plan or outline, not a purported synthesis. If reference files are unavailable, retain the source guardrails below and state that discipline guidance is missing.

Goal

Turn a literature review's ending from generic "future research" into a specific, justified research direction: what predecessors have done, where the explanation gets stuck, where to cut in, and why that move matters.

Workflow

  1. Restate the question anchor.
  2. Summarize progress within the reviewed corpus, not automatically the whole field. State the search coverage and distinguish supported convergence from unresolved questions; neither consensus nor contradiction is mandatory.
  3. Identify where progress gets stuck: theory gap, method limitation, data blind spot, context boundary, variable/mechanism omission, or contradictory evidence.
  4. Select one cut-in point: a module, mechanism, variable relation, context, population, time window, or method design.
  5. Explain the candidate contribution and test it against the strongest available counterexample or prior work. It may clarify a concept, extend an interpretation, resolve a contradiction, or test a boundary; do not promise field-wide novelty without evidence.
  6. Draft a concise research outlook or contribution paragraph.

Four Required Questions

A strong research gap must answer all four:

  1. What have previous studies already established?
  2. Where exactly is the explanation stuck?
  3. Which specific opening will the next study enter through?
  4. Why is this opening worth entering?

If any answer is missing, do not present the gap as ready.

Gap Types

Use the type that matches the evidence:

  • Theory gap: existing frameworks miss a mechanism or actor.
  • Method gap: existing methods cannot observe the needed process, time dimension, or causal structure.
  • Data gap: important samples, contexts, time windows, or measurements are absent.
  • Boundary gap: known findings may not hold under certain conditions.
  • Contradiction gap: studies disagree and the disagreement has a plausible unresolved source.
  • Integration gap: separate modules exist but have not been connected into one explanation chain.

Output Format

Provide:

markdown
## Current Progress

[Consensus + tension in one sentence]

## Stuck Point

[Where the literature cannot yet explain enough]

## Proposed Cut-In Point

[Specific module/mechanism/variable/context/method]

## Why It Matters

[How this fills a gap, resolves a contradiction, tests a boundary, or advances explanation]

## 段落草稿(需作者改写并核对来源)

[Draft prose for conclusion/research outlook. Start with: "以下为草稿,请改写成你自己的论证,并逐句核对来源后再使用。" Tag every literature-dependent sentence with source and status, or [需补来源]]

## Three-Minute Oral Test

- Previous studies have shown: ...
- They have not explained: ...
- I will focus on: ...
- This is valuable because: ...

## 待核实清单

[Unverified sources, "未查到" results, sentences marked [需补来源], and inferences that still need checking; write "无" if empty]

## 给作者的问题

[Judgment calls that belong to the author; write "无" if empty]

The output sections above, and the two closing sections, keep fixed names and order; see references/output-contract.md (a copy bundled in this skill folder).

Guardrails

  • Do not use "few studies have examined" as the only proof of a gap; explain why the missing piece matters.
  • Do not propose an opening that is broader than the user's review question.
  • Do not confuse the user's not-yet-searched area with a true research gap; mark it as "needs verification" when evidence is insufficient.
  • Source integrity: follow references/source-integrity.md. A gap claim about what the literature lacks needs sources or must be marked "needs verification". Use only sources the user provided or that are verified, tag each with a status (用户提供 / 已核验 / 未核验), write "未查到" instead of completing authors, year, journal, or pages, and put anything unverified in ## 待核实清单. If that file is not available, still apply these rules.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Locate Review Research Gap AI skill do?

Locate a concrete, defensible research gap from a literature review synthesis and convert it into an executable future research direction. Use when the user is writing the conclusion, research outlook, thesis proposal significance, or contribution section and needs to avoid vague phrases like "more research is needed" by connecting question, modules, method limits, contradictions, and a specific next study. 触发词:研究空白、研究gap、研究展望、创新点。

Why use Locate Review Research Gap on TypingMind?

Because you install it once and use it with any model. Locate Review Research Gap is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Locate Review Research Gap in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/xingtaxueshu/literature-review-skills/tree/main/skills/locate-review-research-gap. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Locate Review Research Gap?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Locate Review Research Gap?

As many as you like. As long as a model supports skills, you can use Locate Review Research Gap with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Locate Review Research Gap AI skill free?

Yes. It is published on GitHub by xingtaxueshu under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇