agentleFS
Daisybastioned440Daisybastioned440/lite-research-agents/skills/research-proposal/SKILL.md

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

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
  1. Distinctive:

    Every section must be present — do not skip or merge sections

    line 40

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.