research-proposal
Skill2 starsChanged 8 months agoMITView on GitHub
Defines the structure and requirements for a research proposal.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- luwill/research-skillstheir own version, first seen Oct 10, 2026
- bydeng01/phd-application-skilltheir own version, first seen Jun 17, 2026
- jinsi-ai/agent-skillstheir own version, first seen Apr 3, 2026
- nearthink/agent-skillstheir own version, first seen Apr 3, 2026
- mcmespinaa/scholar-supporttheir own version, first seen Mar 31, 2026
- LeonChaoX/qinyan-academic-skillstheir own version, first seen Mar 13, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- LeonChaoX/qinyan-academic-skills★ 910same name
- luwill/research-skills★ 881same name
- qinyan-ai/qinyan-academic-skills★ 80same name
- mcmespinaa/scholar-support★ 2same name
- bydeng01/phd-application-skill★ 1same name
- jinsi-ai/agent-skills★ 0same name
- nearthink/agent-skills★ 0same name
- XiaYiHann/scholar-3★ 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 repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- arxiv-watcherSkill
- first-principlesSkill
- memory-checkpointSkill
- persistent-personaSkill
- system-infoSkill
- war-roomSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 40
Every section must be present — do not skip or merge sections
“Common” is measured: kept by at least 6 in 10 of the 5 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 Proposal
A research proposal is a structured 2-page document. Every section must be present. Be concrete — vague claims are not acceptable.
Sections
1. Problem Statement and Task Definition
What does the system do? What is its input and output? What real-world problem does it solve? Scope must be neither too narrow nor too broad.
2. Input / Output Behavior
Concrete examples of inputs and outputs. Describe what the input and output variables look like and how they interact. Reference the actual data being used — do not describe hypothetical data.
3. Evaluation Metric
How will success be measured? Why is this metric the right one for this problem? A reasonably sized dataset of example input-output pairs must be identified — either from an existing source or collected from scratch.
4. Related Works
What existing research and projects are relevant? How does the proposed work differ? Reference specific papers and systems, not general fields.
5. Baseline and Oracle
- Baseline: a simple, easy-to-implement approach that gives a lower bound on expected performance
- Oracle: an upper bound — what would near-perfect performance look like?
- Neither needs to be implemented for the proposal, but both must be clearly described. If the gap between baseline and oracle is too small, the task is probably not well-chosen.
6. Methodology and Challenges
How will the problem be approached? Why does this method fit? What are the key challenges? What algorithms or models are appropriate, and what are the tradeoffs between accuracy and efficiency?
Requirements
- 2 pages maximum
- Every section must be present — do not skip or merge sections
- Concrete over vague in every section
- Related works must cite specific papers, not just name fields
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.

