科研 Skill

综述选题聚焦收紧

refine-literature-question

Narrows a broad literature-review topic into a bounded, searchable question for scoping, conceptual, or historical reviews. Use when a review topic is too broad to search or screen.

发布者 Codar安全审核通过v0.1.0更新于 2026-11-18

SKILL.md

Refine Literature Question

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 broad topic into a usable question anchor before searching, reading, or writing the review. The output should be a one-sentence research question that forces selection: some papers become clearly relevant, and others become safe to skip.

Workflow

  1. Identify whether the user's input is a topic, a phenomenon, or an actual question.
  2. Identify the review type, then replace vague nouns with bounded concepts, objects, relationships, periods, or puzzles.
  3. Generate 3-5 candidate angles after scope decisions are clear; do not flood an interview turn with candidates.
  4. Evaluate each candidate against the three-anchor test.
  5. Recommend one primary question and 1-2 backups, then explain what each would make the review include or exclude.

Three-Anchor Test

A strong literature review question should:

  • Match the review purpose: explanation, bounded evidence mapping, conceptual distinction, or historical interpretation. A causal "why/how" question is not mandatory.
  • Force literature selection by making some studies irrelevant to the question.
  • Feel worth answering if a reader could get a credible answer from the review.

If the question fails any item, revise it before proceeding to search or outline the literature.

Question Patterns

Use these patterns when generating candidates:

  • Mechanism: Why does [phenomenon] occur in [context], and through what mechanism?
  • Contrast: Why does [outcome] differ between [group/place/time A] and [group/place/time B]?
  • Condition: Under what conditions does [factor] influence [outcome]?
  • Tension: Why do existing studies disagree about [relationship/result]?
  • Process: How does [actor/system] move from [state A] to [state B]?
  • Scoping: What concepts, methods, and populations have been studied for [object] within [scope]?
  • Conceptual/history: How has the meaning of [concept] changed across [traditions/periods], and what does that change explain?

Output Format

Provide:

## Candidate Questions

1. ...
2. ...

## Recommended Anchor

[One sentence]

## Why This Works

- Selection boundary: ...
- Likely literature modules: ...
- What to skip: ...

## Revision Notes

- If the user wants broader scope: ...
- If the user wants narrower scope: ...

## 待核实清单

[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 accept an unbounded label such as XX research review as the final anchor. Descriptive, historical, and conceptual reviews are valid when their corpus, scope, and analytical purpose are explicit.
  • Do not invent a domain-specific claim when the user has not provided enough context; offer candidate angles and mark assumptions.
  • Treat AI as a sparring partner: generate options and pressure-test wording, but keep the user's academic judgment in charge.
  • Source integrity: follow references/source-integrity.md. Claims about what "existing studies" do or disagree on are assumptions until the user supplies sources; mark them. 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.

示例提示词

我的综述题目太宽,帮我把它收紧成一个可检索的具体研究问题。

所属插件

跨学科科研方法跨学科通用科研方法:系统综述与元分析、预注册、实验与问卷设计、文献矛盾与研究空白、科学计量与专利分析、可复现研究、答辩与审稿回复。

安装该插件会一并获得同领域的 54 个 Skill / MCP。

同插件的其他科研 Skill

常见问题

综述选题聚焦收紧能做什么?

Narrows a broad literature-review topic into a bounded, searchable question for scoping, conceptual, or historical reviews. Use when a review topic is too broad to search or screen。

如何安装综述选题聚焦收紧?

在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「综述选题聚焦收紧」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。

综述选题聚焦收紧需要哪些权限?

该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。

综述选题聚焦收紧经过官方审核吗?

是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。