K-Dense-AI/scientific-agent-skills / skills/research-grants
research-grants
VerifiedSupports research proposal preparation and review for NSF, NIH, DOE, DARPA, and Taiwan NSTC, including opportunity-specific requirements, aims, review criteria, budgets, broader impacts, forms, and resubmissions. Use for investigator-authored grant development, compliance matrices, and proposal critiques.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.9 KB |
| assets/budget_justification_template.md | markdown | 7.2 KB |
| assets/nih_specific_aims_template.md | markdown | 3.0 KB |
| assets/nsf_project_summary_template.md | markdown | 2.5 KB |
| references/README.md | markdown | 2.4 KB |
| references/broader_impacts.md | markdown | 23.8 KB |
| references/core_components.md | markdown | 16.1 KB |
| references/darpa_guidelines.md | markdown | 7.0 KB |
| references/doe_guidelines.md | markdown | 7.5 KB |
| references/nih_guidelines.md | markdown | 13.3 KB |
| references/nsf_guidelines.md | markdown | 7.8 KB |
| references/nstc_guidelines.md | markdown | 7.5 KB |
| references/proposal_types_and_resubmission.md | markdown | 3.2 KB |
| references/review_criteria.md | markdown | 2.8 KB |
| references/specific_aims_guide.md | markdown | 20.6 KB |
| references/writing_principles.md | markdown | 3.5 KB |
references/specific_aims_guide.md
View on GitHub# NIH Specific Aims Page: The Complete Guide
Reviewed 2026-10-01. This is writing advice, not an official template. All sample
research, preliminary results, statistics, sample sizes and resources below are
hypothetical, unvalidated teaching examples. Replace them with investigator-provided
evidence and current primary citations; do not submit them as real findings. Follow
[NIH application policy](https://grants.nih.gov/grants/policy/nihgps/HTML5/section_2/2.3.7_policies_affecting_applications.htm)
on limited AI assistance and applicant ownership. Read `nih_guidelines.md` for current
review/form requirements before using these patterns.
## Overview
The **Specific Aims page** gives reviewers a compact map of the question, planned work and contribution. Make it understandable on its own while ensuring the full research strategy supports every claim.
**Length**: Up to 1 page for standard applications; verify the NOFO
**Margins**: At least 0.5 inches (all sides)
**Font**: At least 11-point body text; graphic text follows the attachment-rule exception
**Line spacing**: At most six lines per vertical inch; at most 15 characters per horizontal inch. See [NIH attachment rules](https://www.grants.nih.gov/grants-process/write-application/how-to-apply-application-guide/format-attachments).
**Purpose**:
- Communicate your research vision clearly and compellingly
- Establish significance and innovation
- Demonstrate feasibility
- Show that you can accomplish meaningful work in the proposed timeframe
- Make reviewers excited to fund your work
## Anatomy of a Specific Aims Page
### Suggested drafting sequence (not a mandated format)
1. **Opening Hook** (2-4 sentences)
2. **Gap/Problem Statement** (2-4 sentences)
3. **Long-Term Goal** (1 sentence)
4. **Objective** (1-2 sentences)
5. **Central Hypothesis** (1 sentence) [or Research Questions]
6. **Rationale** (2-3 sentences with preliminary data mention)
7. **Specific Aims** (enough to answer the question within the project's scope)
8. **Expected Outcomes and Impact** (2-4 sentences)
## Detailed Structure
### Opening Paragraph: The Hook
**Purpose**: Establish importance and grab attention
**What to include**:
- Broad context (disease burden, biological importance, technological need)
- Epidemiological data or statistics that establish scale
- Why this problem matters for health or science
- Create urgency
**Length**: 2-4 sentences
**Writing tips**:
- Start strong with compelling statement
- Use concrete numbers (prevalence, mortality, costs)
- Avoid jargon in first sentence
- Make it accessible to non-specialists on panel
**Examples**:
*Clinical Example*:
"Pancreatic cancer causes [current, cited burden]. Existing [specified diagnostic or therapeutic approaches] leave [evidence-supported limitation]. Resolving [defined gap] could enable [bounded scientific contribution]."
*Basic Science Example*:
"Mitochondrial dysfunction is a hallmark of aging and age-related diseases, yet the mechanisms linking mitochondrial decline to cellular senescence remain poorly understood. Emerging evidence suggests that mitochondrial-nuclear communication pathways play a central role in longevity determination across species, from yeast to mammals. Understanding how cells sense and respond to mitochondrial stress could reveal new therapeutic targets for age-related diseases affecting millions worldwide."
### Second Paragraph: Gap and Context
**Purpose**: Define what's known, what's unknown, and why it matters
**What to include**:
- Current state of knowledge (brief literature context)
- Specific gap or barrier to progress
- Why this gap is critical to address
- Why current approaches are insufficient
**Length**: 3-5 sentences
**Structure**:
1. What we know (1-2 sentences)
2. What we don't know / what's limiting progress (1-2 sentences)
3. Why this gap matters (1 sentence)
**Examples**:
"Prior studies have identified numerous genetic mutations associated with PDAC development, including KRAS, TP53, SMAD4, and CDKN2A. However, the tumor microenvironment (TME), comprising immune cells, fibroblasts, and extracellular matrix, is increasingly recognized as a critical determinant of therapeutic resistance. Current models fail to recapitulate the complex TME architecture and cell-cell interactions that drive therapy resistance in vivo, limiting our ability to develop effective treatments. Understanding how the TME protects tumor cells from chemotherapy is essential for designing combination therapies that overcome resistance."
### Third Paragraph: Long-Term Goal, Objective, Hypothesis, Rationale
**Purpose**: Set up your specific approach and justification
**Structure**:
**Long-Term Goal** (1 sentence):
- Your overarching research program direction
- Broader than this specific proposal
- Provides context for this work
*Example*: "The long-term goal of our research is to elucidate the molecular mechanisms by which the tumor microenvironment promotes therapeutic resistance in pancreatic cancer."
**Objective** (1-2 sentences):
- Specific objective of THIS grant
- What you will accomplish during the permitted project period
- More focused than long-term goal
*Example*: "The objective of this application is to define the role of cancer-associated fibroblasts (CAFs) in mediating gemcitabine resistance and to develop combination therapies targeting CAF-tumor interactions."
**Central Hypothesis** (1 sentence):
- Testable prediction
- Should unify the specific aims
- Based on preliminary data or logical reasoning
- Clear and specific
*Example*: "Our central hypothesis is that CAF-secreted factors activate protective autophagy in tumor cells, conferring resistance to gemcitabine, and that dual inhibition of CAF signaling and autophagy will restore drug sensitivity."
**Alternative: Research Questions** (if hypothesis-testing isn't appropriate):
- 2-3 focused questions
- Should correspond to specific aims
*Example*: "This project will address the following questions: (1) What factors secreted by CAFs promote tumor cell survival during chemotherapy? (2) How do tumor cells integrate CAF signals to activate protective responses? (3) Can targeting CAF-tumor interactions enhance therapeutic efficacy in preclinical models?"
**Rationale** (2-3 sentences):
- Why you think the hypothesis is true
- Mention key preliminary data (very briefly)
- Logical basis for your approach
- Why this approach will work
*Example*: "This hypothesis is based on our preliminary data showing that CAF-conditioned medium protects tumor cells from gemcitabine-induced apoptosis by 60% (Fig. 1), and that this protection is blocked by autophagy inhibitors (Fig. 2). Proteomic analysis of CAF secretomes identified 15 candidate factors enriched in drug-resistant contexts (Table 1). These findings suggest a targetable pathway linking CAF signaling to tumor cell survival that could be exploited therapeutically."
### Specific Aims (Main Section)
**How many aims**: Choose the number supported by the question, scope and resources.
Two or three is a common drafting pattern, not an NIH requirement. One coherent aim
can be appropriate; many large aims can exceed feasible scope.
**Structure for each aim**:
1. **Aim Statement** (1-2 sentences, bold or underlined)
2. **Rationale and Background** (1-3 sentences)
3. **Working Hypothesis** (1 sentence, if applicable)
4. **Approach Summary** (2-4 sentences)
5. **Expected Outcomes and Interpretation** (1-2 sentences)
**Length per aim**: Keep the combined narrative within the actual page maximum; the expanded teaching examples below are not a one-page finished layout.
**Relationships between aims**:
- **Independent**: Failure of one aim doesn't doom the others
- **Synergistic**: Aims build on each other or address complementary questions
- **Progressive**: Aim 1 enables Aim 2, Aim 2 enables Aim 3 (be careful—creates risk)
#### Example Aim Structure:
**Aim 1: Identify CAF-secreted factors that mediate gemcitabine resistance.**
*Rationale*: CAF-conditioned medium confers significant protection against gemcitabine (Fig. 1), suggesting secreted factors are responsible. We have identified 15 candidate proteins enriched in CAF secretomes from resistant versus sensitive contexts (Table 1).
*Working Hypothesis*: CAFs secrete specific growth factors and cytokines (including IL-6, CXCL12, and HGF) that activate pro-survival pathways in tumor cells.
*Approach*: We will (1) validate candidate factors using neutralizing antibodies in co-culture assays, (2) measure activation of downstream signaling pathways (STAT3, PI3K/AKT, MAPK) in tumor cells, and (3) perform CRISPR screens in CAFs to identify factors required for resistance phenotype. We will use patient-derived CAFs and tumor cells to ensure clinical relevance.
*Expected Outcomes*: We expect to identify 3-5 CAF-secreted factors sufficient and necessary for gemcitabine resistance, and define their signaling mechanisms. These will serve as therapeutic targets for Aims 2-3.
---
**Aim 2: Determine the mechanisms by which CAF signals activate protective autophagy in tumor cells.**
*Rationale*: Our data show that CAF-mediated resistance requires autophagy (Fig. 2), but the signaling pathways linking CAF factors to autophagy activation remain unknown.
*Working Hypothesis*: CAF-secreted factors activate mTOR-independent autophagy through AMPK and ULK1 phosphorylation.
*Approach*: We will (1) measure autophagy flux in tumor cells exposed to CAF factors using LC3 turnover assays and electron microscopy, (2) define signaling pathways using phosphoproteomic analysis and pharmacologic inhibitors, and (3) validate pathways using genetic knockdowns (shRNA/CRISPR) of key nodes. Studies will be performed in 2D and 3D co-culture systems.
*Expected Outcomes*: We will define the signaling cascade from CAF factors to autophagy activation, identifying druggable nodes for combination therapy. Results will inform Aim 3 therapeutic strategies.
---
**Aim 3: Evaluate combination therapies targeting CAF-tumor interactions in preclinical models.**
*Rationale*: Single-agent therapies targeting CAFs or autophagy have shown limited efficacy clinically, suggesting combination approaches are needed.
*Working Hypothesis*: Dual inhibition of CAF signaling and autophagy will synergistically restore gemcitabine sensitivity in vivo.
*Approach*: Using patient-derived xenograft (PDX) models and genetically engineered mouse models (GEMM) of PDAC, we will test combinations of (1) gemcitabine + CAF pathway inhibitors identified in Aim 1, (2) gemcitabine + autophagy inhibitors, and (3) triple combinations. We will assess tumor growth, survival, and mechanism (IHC, RNA-seq) in n=10-15 mice per group.
*Expected Outcomes*: We expect combination therapies will reduce tumor growth by ≥60% compared to gemcitabine alone, with synergistic effects. The most effective regimen will be advanced toward clinical translation through an investigator-initiated trial (we have IND-enabling resources available at our institution).
### Closing Paragraph: Impact and Significance
**Purpose**: Leave reviewers with enthusiasm and clear understanding of importance
**What to include**:
- Expected outcomes of the overall project
- How findings will advance the field
- Positive impact on health or science
- Next steps or future directions
- Why this matters
**Length**: 2-4 sentences
**Writing tips**:
- Be confident but not arrogant
- Connect back to opening (full circle)
- Emphasize transformative potential
- Avoid over-promising
**Examples**:
"The proposed research is significant because it will define a novel mechanism of chemotherapy resistance in pancreatic cancer and identify new therapeutic targets to overcome this resistance. Results will provide mechanistic insights into CAF-tumor interactions that drive drug resistance, immediately applicable to clinical trial design. We expect findings will enable rational design of combination therapies that improve outcomes for PDAC patients, who currently have few effective treatment options. This work will establish new paradigms for targeting the tumor microenvironment in solid cancers."
## Writing Principles
### Clarity and Accessibility
**Write for a mixed audience**:
- Some panel members will be experts in your area
- Others will be in related but not identical fields
- Program officers and council members will read it
- Reviewers should be able to understand the overall logic from this page
**Strategies**:
- Define technical terms at first use
- Explain abbreviations (except very common ones)
- Use clear, direct language
- Avoid excessive jargon
- Make logical flow obvious
### Confidence Without Arrogance
**Confident** ✅:
- "Our preliminary data demonstrate..."
- "We have established a robust model system..."
- "This approach will elucidate..."
**Arrogant** ❌:
- "We are uniquely qualified..."
- "Only our lab can do this..."
- "This will revolutionize the field..."
**Tentative** ❌:
- "We hope to..."
- "We will try to..."
- "It is possible that..."
### Active and Specific
**Aim statements should**:
- Start with action verbs (Determine, Identify, Elucidate, Define, Characterize, Validate, Develop)
- Be specific and testable
- Indicate what will be learned
**Weak Aim** ❌:
"Aim 1: Study the role of protein X in disease Y"
**Strong Aim** ✅:
"Aim 1: Determine how protein X phosphorylation regulates disease Y progression using genetic and pharmacologic approaches"
### Show Feasibility
**Throughout the aims page**:
- Mention preliminary data (figures, tables)
- Reference established methods
- Show you have necessary resources
- Demonstrate expertise
- Indicate prior success
**Don't**:
- Relegate all preliminary data to Research Strategy
- Make it seem like you're starting from scratch
- Propose overly ambitious aims without support
## Common Mistakes
### Mistake 1: Too Much Background
❌ Half page of background before getting to aims
✅ Focused background that motivates your specific approach
The aims page is NOT a mini review article. Provide only enough background to establish importance and gaps.
### Mistake 2: Vague Objectives
❌ "We will study the mechanisms of disease X"
❌ "We will investigate the role of protein Y"
✅ "We will identify the phosphorylation sites on protein Y that regulate its interaction with Z using mass spectrometry and mutagenesis"
### Mistake 3: Overly Ambitious Scope
❌ Four aims, each of which could be a separate R01
❌ Proposing to solve multiple major questions in the field
❌ "Boil the ocean" approach
✅ Focused aims that are achievable within the permitted project period
### Mistake 4: Dependent Aims
❌ Aim 2 and Aim 3 both require Aim 1 to succeed
✅ Aims are synergistic but independent (failure of one doesn't doom the others)
### Mistake 5: No Preliminary Data Mentioned
❌ Seems like a fishing expedition
❌ Reviewers wonder if it's feasible
✅ Brief mentions of preliminary data throughout (refer to figures)
### Mistake 6: Weak Impact Statement
❌ "This will advance our understanding of X"
❌ "Results will be published and presented"
✅ "This will identify new therapeutic targets for disease X, affecting 500,000 patients annually, and provide the foundation for investigator-initiated clinical trials"
### Mistake 7: Jargon-Heavy First Paragraph
❌ Opening sentence full of abbreviations and specialized terminology
❌ Assumes all reviewers are experts in your subfield
✅ Opening that's comprehensible to broad scientific audience
### Mistake 8: No Clear Hypothesis
❌ Just listing aims without unifying framework
❌ Aims without a clear question or contribution
✅ A unifying hypothesis, research question or development objective suited to the work
### Mistake 9: Forgetting Page Limits
❌ Exceeding the applicable page maximum (risks validation failure or return without review)
❌ Tiny fonts to cram in more content (violations)
✅ Within the page maximum with compliant formatting
### Mistake 10: Not Telling a Story
❌ Disconnected aims that feel like 3 separate projects
❌ No logical flow or coherence
✅ Unified narrative with aims building on each other
## Advanced Tips
### Use Visual Elements
**Figures on Specific Aims Page**:
- NIH allows figures on aims page
- Can be very effective to show key preliminary data
- Must be legible at 100%; NIH permits smaller graphic text under its attachment rules
- Don't let figure crowd out text
- Typical: 1 small figure or panel showing most critical data
**Tables**:
- Can summarize preliminary data compactly
- Show patient characteristics, gene lists, etc.
- Must be readable
### Strategic Use of Bold/Italics
**Appropriate**:
- Bold aim statements to make them stand out
- Italicize gene names (standard convention)
- Underline key points (sparingly)
**Avoid**:
- Excessive formatting that looks cluttered
- All caps (looks like shouting)
- Colors (may not print/display correctly)
### The "Skim Test"
**Your aims page should pass the skim test**:
- Someone reading just aim statements should understand the project
- Bold aim statements that can be read independently
- Each paragraph has clear topic sentence
- Logical flow is apparent even when skimming
**Exercise**: Ask colleague to read only bold/underlined text—can they understand the project?
### Tailoring to Career Stage
**Early Stage Investigators**:
- Show you've thought through challenges
- Demonstrate strong mentorship and institutional support
- Emphasize innovation while ensuring feasibility
- Don't over-promise
**Established Investigators**:
- Show how this extends your research program
- Emphasize track record implicitly
- Can propose more ambitious aims if supported by extensive preliminary data
- Show how this opens new directions
## Examples of Strong Opening Paragraphs
### Example 1: Cancer Biology
"[Cited evidence] identifies treatment resistance as an important problem in [defined breast-cancer population]. The role of [specific mechanism] remains unresolved. The proposed work tests [applicant hypothesis] to determine [knowledge gained], without assuming that a preclinical result establishes clinical benefit."
### Example 2: Neuroscience
"Alzheimer's disease creates [current, cited burden]. Despite available treatments, [specific, evidence-supported limitation] remains. We will investigate [defined mechanistic question] using [applicant design]. Findings could inform [bounded future step]." Do not claim that no disease-modifying therapies exist.
### Example 3: Infectious Disease
"Antimicrobial resistance in [defined population/pathogen] causes [current, cited burden]. Existing treatment options leave [documented gap]. We will test [investigator approach] against [specified baseline], measuring efficacy and possible resistance-related tradeoffs rather than assuming either."
## Revision Checklist
Before finalizing, ensure your aims page:
**Content**:
- [ ] Opens with compelling statement of importance
- [ ] Clearly defines the gap or problem
- [ ] States specific, measurable objective
- [ ] Presents testable hypothesis (or focused research questions)
- [ ] Mentions preliminary data supporting feasibility
- [ ] Aim count and scope are justified by the science and resources
- [ ] Each aim is testable and achievable
- [ ] Aims are independent but synergistic
- [ ] Expected outcomes are clearly stated
- [ ] Closes with impact and significance
**Clarity**:
- [ ] First paragraph is accessible to non-specialists
- [ ] Technical terms are defined
- [ ] Abbreviations are spelled out at first use
- [ ] Logical flow is clear
- [ ] Aim statements can stand alone
- [ ] Language is confident and active
**Format**:
- [ ] Within the applicable one-page maximum
- [ ] At least 0.5-inch margins
- [ ] At least 11-point body text; legible graphic text under the applicable exception
- [ ] Readable line spacing
- [ ] Compliant with NIH formatting requirements
- [ ] Figures (if included) are legible
**Impact**:
- [ ] Passes the "skim test"
- [ ] Would make you excited if you were a reviewer
- [ ] Clearly articulates significance
- [ ] Shows feasibility without over-selling
- [ ] Connects to health or scientific impact
## Final Thoughts
Revise the Specific Aims page together with the full research strategy:
- Revise until the question, approach and scope are clear
- Get feedback from colleagues and mentors
- Test it on people outside your field
- Read it aloud to check flow
- Let it sit, then revise with fresh eyes
- Study funded examples in your field
Communicate importance, innovation and feasibility without assuming a particular reviewer workload or promising that writing quality guarantees funding.
---
**Key Takeaway**: The perfect Specific Aims page tells a compelling story within the page limit—establishing a significant problem, presenting an innovative and feasible solution, showing preliminary evidence of success, and articulating transformative impact. Every sentence must earn its place.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |