research-question
Skill6 starsChanged 6 months agoMITView on GitHub
Formulate research questions, hypotheses, and contribution statements from identified literature gaps. Use when defining a research problem, framing a thesis topic, identifying novelty, or writing the "contribution" section of a proposal or paper.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- matthewdigiuseppe/MStacktheir own version, first seen Nov 1, 2026
- 1second1/personal-research-skillstheir own version, first seen Oct 7, 2026
- cellrishi-code/claude-skills-atlastheir own version, first seen Oct 4, 2026
- deanmikan/ai-native-company-startertheir own version, first seen Sep 4, 2026
- crfldrxyz/AuthorOps-Skillstheir own version, first seen Sep 1, 2026
- KhaledSaeed18/dotclaudetheir own version, first seen Jul 4, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- matthewdigiuseppe/MStack★ 17same name
- cellrishi-code/claude-skills-atlas★ 6same name
- KhaledSaeed18/dotclaude★ 5same name
- 1second1/personal-research-skills★ 1same name
- crfldrxyz/AuthorOps-Skills★ 0same name
- deanmikan/ai-native-company-starter★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository75 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-browserSkill
- agent-desktopSkill
- agent-expertise-protocolSkill
- ai-figure-generationSkill
- api-securitySkill
- architecture-decision-recordsSkill
- architecture-reviewSkill
- art-of-war-software-engineeringSkill
- browser-automationSkill
- business-product-leadershipSkill
- c4-level1-contextSkill
- c4-level2-containerSkill
- c4-level3-componentSkill
- c4-level4-codeSkill
- c4-modelSkill
- clean-architectureSkill
- cloud-securitySkill
- code-quality-gateSkill
- collaborative-engineering-agentSkill
- conference-paperSkill
- container-securitySkill
- database-designSkill
- ddd-coreSkill
- ddd-patternsSkill
- ddd-tacticalSkill
- defense-prepSkill
- dependency-managementSkill
- diffusion-release-trackingSkill
- docker-containerizationSkill
- dora-coreSkill
- evolutionary-architectureSkill
- exam-rubricSkill
- experiment-trackingSkill
- federated-learning-dqnSkill
- git-workflowSkill
- golang-developmentSkill
- internal-critiqueSkill
- javascript-typescriptSkill
- journal-q1-polishSkill
- kinhluan-routerSkill
- kubernetes-orchestrationSkill
- merge-request-reviewSkill
- milestone-trackerSkill
- paper-auditSkill
- paper-writingSkill
- pastureSkill
- payment-systemsSkill
- penetration-testingSkill
- phd-proposalSkill
- problem-discoverySkill
- product-analyticsSkill
- product-ux-researchSkill
- progress-reportSkill
- proposal-defenseSkill
- publication-strategySkill
- python-developmentSkill
- research-designSkill
- research-watchSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Run sota-survey first. You need a gap table before formulating RQ.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Research Question Formulation
Bridge the gap between what exists (SOTA) and what you'll contribute.
Prerequisite
Run sota-survey first. You need a gap table before formulating RQ.
Workflow
Step 1 — Gap → Problem Statement
For each gap from SOTA survey, apply this template:
Despite [what exists], [limitation/gap] remains unsolved because [root cause].
This causes [concrete consequence] in [application domain].Example:
Despite federated learning achieving competitive accuracy, communication efficiency in heterogeneous IoT networks remains unsolved because existing methods assume uniform client capabilities. This causes excessive energy drain in resource-constrained healthcare devices.
Step 2 — Formulate Research Questions
Main RQ (1 sentence):
How can [method/approach] be designed to [achieve goal] in [context/constraint]?Sub-questions (2-4, each answerable in ~1 paper/chapter):
- RQ1: [measurable, specific]
- RQ2: [builds on RQ1]
- RQ3: [validates or extends]
RQ Quality Check:
- Specific — not "improve performance" but "reduce communication rounds by X%"
- Feasible — answerable in your timeline with your resources
- Novel — not already answered in literature
- Significant — matters to the field
- Ethical — no harm, IRB if needed
Step 3 — Hypothesis (if experimental)
H0 (null): [Method A] performs no better than [baseline] on [metric] in [setting]
H1 (alternative): [Method A] achieves [≥X% improvement] over [baseline] on [metric]Step 4 — Contribution Statement
Structure for proposal and paper Introduction:
## Contributions
This work makes the following contributions:
1. **[Type: Algorithm/Framework/Dataset/Analysis]**: We propose [name], which [what it does] to address [gap].
2. **[Type]**: We demonstrate [empirical result] on [benchmark], showing [magnitude] improvement over [baseline].
3. **[Type]** (optional): We release [artifact] for reproducibility.Contribution types: Algorithm, Framework, Dataset, Benchmark, Analysis, Survey, System, Theorem.
Step 5 — Scope Boundary
Explicitly state what you will NOT do (saves you from committee scope creep):
Out of scope:
- [Related problem you won't solve and why]
- [Assumption you're making]
- [Limitation you accept]Output Format
## Research Problem Definition
**Problem:** [1-2 sentence problem statement]
**Main RQ:** [Single question]
**Sub-questions:**
- RQ1: ...
- RQ2: ...
**Hypothesis:**
- H0: ...
- H1: ...
**Contributions:**
1. ...
2. ...
**Out of scope:** ...Links to Other Skills
- Requires →
sota-survey(gap table as input) - Feeds into →
phd-proposal(problem statement section) - Feeds into →
paper-writing(Introduction + Contribution sections)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

