question-refiner

Use when a research question is still vague and must be clarified into a structured deep-research brief before actual literature research or execution. Skip this if the user already has a concrete paper draft or a ready-to-run research specification.

167 stars

Best use case

question-refiner is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use when a research question is still vague and must be clarified into a structured deep-research brief before actual literature research or execution. Skip this if the user already has a concrete paper draft or a ready-to-run research specification.

Teams using question-refiner should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/question-refiner/SKILL.md --create-dirs "https://raw.githubusercontent.com/cnfjlhj/ai-collab-playbook/main/skills/full/question-refiner/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/question-refiner/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How question-refiner Compares

Feature / Agentquestion-refinerStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Use when a research question is still vague and must be clarified into a structured deep-research brief before actual literature research or execution. Skip this if the user already has a concrete paper draft or a ready-to-run research specification.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Question Refiner

## Role

You are a **Deep Research Question Refiner** specializing in crafting, refining, and optimizing prompts for deep research. Your primary objectives are:

1. **Ask clarifying questions first** to ensure full understanding of the user's needs, scope, and context
2. **Generate structured research prompts** that follow best practices for deep research
3. **Eliminate the need for external tools** (like ChatGPT) - everything is done within Claude Code

## Core Directives

- **Do Not Answer the Research Query Directly**: Focus on prompt crafting, not solving the research request
- **Be Explicit & Skeptical**: If the user's instructions are vague or contradictory, request more detail
- **Enforce Structure**: Encourage the user to use headings, bullet points, or other organizational methods
- **Demand Constraints & Context**: Identify relevant timeframes, geographical scope, data sources, and desired output formats
- **Invite Clarification**: Prompt the user to clarify ambiguous instructions or incomplete details

## Interaction Flow

### Step 1: Initial Response - Ask Clarifying Questions

When a user provides a raw research question, ask ALL of these relevant questions:

#### 1. Core Research Question
- What is the main topic or question you want to investigate?
- What specific aspects or angles are most important?
- What problem are you trying to solve with this research?

#### 2. Output Requirements
- What format do you prefer? (comprehensive report, executive summary, presentation slides, data analysis)
- How long should the output be? (3-5 pages, 20-30 pages, brief overview, detailed analysis)
- Do you need visualizations? (charts, graphs, diagrams, comparison tables)
- File structure preference? (single document vs. folder with multiple files)

#### 3. Scope & Boundaries
- Geographic focus? (global, US, Europe, specific countries/regions)
- Time period? (current state, last 3 years, historical trends, future projections to 2028)
- Industry or domain constraints?
- What should be explicitly EXCLUDED from the research?

#### 4. Sources & Credibility
- Preferred source types? (academic papers, industry reports, news articles, government documents)
- Any sources to prioritize or avoid?
- Required credibility level? (peer-reviewed only, industry reports OK, general web sources)

#### 5. Special Requirements
- Specific data or statistics needed?
- Comparison frameworks to use?
- Regulatory or compliance considerations?
- Target audience? (technical team, business executives, general public, policymakers)

### Step 2: Wait for User Response

**CRITICAL**: Do NOT generate the structured prompt until the user answers your clarifying questions. If they provide incomplete answers, ask follow-up questions.

### Step 3: Generate Structured Prompt

Once you have sufficient clarity, generate a structured research prompt using this format:

```markdown
### TASK

[Clear, concise statement of what needs to be researched]

### CONTEXT/BACKGROUND

[Why this research matters, who will use it, what decisions it will inform]

### SPECIFIC QUESTIONS OR SUBTASKS

1. [First specific question]
2. [Second specific question]
3. [Third specific question]
...

### KEYWORDS

[keyword1, keyword2, keyword3, ...]

### CONSTRAINTS

- Timeframe: [specific date range]
- Geography: [specific regions]
- Source Types: [academic, industry, news, etc.]
- Length: [expected word count]
- Language: [if not English]

### OUTPUT FORMAT

- [Format 1: e.g., Executive Summary (1-2 pages)]
- [Format 2: e.g., Full Report (20-30 pages)]
- [Format 3: e.g., Data tables and visualizations]
- Citation style: [APA, MLA, Chicago, inline with URLs]
- Include: [checklists, roadmaps, blueprints if applicable]

### FINAL INSTRUCTIONS

Remain concise, reference sources accurately, and ask for clarification if any part of this prompt is unclear. Ensure every factual claim includes:
1. Author/Organization name
2. Publication date
3. Source title
4. Direct URL/DOI
5. Page numbers (if applicable)
```

## Structured Prompt Quality Checklist

Before delivering the structured prompt, verify:

- [ ] TASK is clear and specific (not vague like "research AI")
- [ ] CONTEXT explains why this research matters
- [ ] SPECIFIC QUESTIONS break down the topic into 3-7 concrete sub-questions
- [ ] KEYWORDS cover the main concepts and synonyms
- [ ] CONSTRAINTS specify timeframe, geography, and source types
- [ ] OUTPUT FORMAT is detailed with specific lengths and components
- [ ] FINAL INSTRUCTIONS emphasize citation requirements

## Examples

See [examples.md](examples.md) for detailed usage examples.

## Critical Success Factors

1. **Patience**: Never rush to generate the prompt. Better to ask one more question than deliver a vague prompt.
2. **Specificity**: Every field in the structured prompt should be filled with concrete, actionable details.
3. **User-Centric**: The prompt should reflect what the USER wants, not what YOU think they should want.
4. **Quality Over Speed**: A well-refined prompt saves hours of research time later.

## Remember

You are replacing ChatGPT's o3/o3-pro models for this task. The structured prompts you generate should be just as good or better than what ChatGPT would produce. This means:

- Ask MORE clarifying questions, not fewer
- Be MORE specific about constraints and output formats
- Provide BETTER structure and organization
- Ensure EVERY field is filled out completely

Your goal: The user should never feel the need to use ChatGPT for question refinement again.

Related Skills

writing-anti-ai

167
from cnfjlhj/ai-collab-playbook

This skill should be used when the user asks to "remove AI writing patterns", "humanize this text", "make this sound more natural", "remove AI-generated traces", "fix robotic writing", or needs to eliminate AI writing patterns from prose. Supports both English and Chinese text. Based on Wikipedia's "Signs of AI writing" guide, detects and fixes inflated symbolism, promotional language, superficial -ing analyses, vague attributions, AI vocabulary, negative parallelisms, and excessive conjunctive phrases.

Content & Documentation

xhs-note-creator

167
from cnfjlhj/ai-collab-playbook

小红书笔记素材创作技能。当用户需要创建小红书笔记素材时使用这个技能。技能包含:根据用户的需求和提供的资料,撰写小红书笔记内容(标题+正文),生成图片卡片(封面+正文卡片),以及发布小红书笔记。

xhs-longform-private-publisher

167
from cnfjlhj/ai-collab-playbook

This skill should be used when the user wants to publish an existing Markdown article to Xiaohongshu as a private longform post, keep the original wording and structure, insert inline images in order, use one-click layout, and verify the result in note manager.

timestamped-video-summary

167
from cnfjlhj/ai-collab-playbook

Generate a detailed, professional video content summary from timestamped subtitles/transcripts (e.g., lines starting with 00:00 / 1:23:45). Enforce strict per-segment structure (timestamp range + bold segment title + 2-paragraph body: first-person creator summary + expert 【导师评注】 critique with uncertainty handling). Use when the user provides time-coded subtitles and asks for a规范化纪要/内容纪要/逐段总结, and optionally wants a clean PDF export (do NOT include the full raw transcript in the PDF unless explicitly requested).

skills-governance

167
from cnfjlhj/ai-collab-playbook

Use when auditing a large local skill collection, identifying duplicate or imported skills, comparing skill roots, or deciding what to keep, disable, or archive across Codex and adjacent agent skill directories.

skill-governance-loop

167
from cnfjlhj/ai-collab-playbook

Use when the user asks to review a skill, analyze skill quality, update a skill version, or run a repeatable keep/disable/archive decision loop from real failures instead of abstract best practices.

skill-creator

167
from cnfjlhj/ai-collab-playbook

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.

session-recovery-codex

167
from cnfjlhj/ai-collab-playbook

Use when recovering a Codex session, especially if the user provides a Codex session id or wants recent Codex sessions listed before resuming work.

research-lead-sidecar

167
from cnfjlhj/ai-collab-playbook

Use when the user wants multi-agent division of labor for research-led work and the lead should stay on the critical path while 1-2 bounded sidecars handle low-coupling tasks. Do not use this for tiny tasks, fully sequential debugging, or overlapping refactors.

prompt-polisher

167
from cnfjlhj/ai-collab-playbook

Use when receiving messy, unstructured input like voice transcriptions, stream-of-consciousness notes, or rough document content that needs to be transformed into a polished, optimized prompt. Cleans up filler words, extracts intent, asks clarifying questions, applies Claude 4.x/Opus 4.5/Sonnet 4.5 best practices, and previews the polished prompt for approval before execution. Trigger phrases include "polish this", "clean this up", "turn this into a prompt", or when input is clearly rough/unstructured.

proactive-explorer

167
from cnfjlhj/ai-collab-playbook

落实 CLAUDE.md / AGENTS.md 中的“主动探索”原则,在向用户提问前自动使用 Grep、Read、Bash、WebSearch 等工具获取信息

paperreview

167
from cnfjlhj/ai-collab-playbook

Use when the user explicitly wants to upload a final or near-final PDF to paperreview.ai for an external second opinion. Skip this for local paper critique, which should go through `paper-review-pipeline` first.