research-grants

89
5
Source

Write competitive research proposals for NSF, NIH, DOE, and DARPA. Agency-specific formatting, review criteria, budget preparation, broader impacts, significance statements, innovation narratives, and compliance with submission requirements.

Install

mkdir -p .claude/skills/research-grants && curl -L -o skill.zip "https://mcp.directory/api/skills/download/368" && unzip -o skill.zip -d .claude/skills/research-grants && rm skill.zip

Installs to .claude/skills/research-grants

About this skill

Research Grant Writing

Overview

Research grant writing is the process of developing competitive funding proposals for federal agencies and foundations. Master agency-specific requirements, review criteria, narrative structure, budget preparation, and compliance for NSF (National Science Foundation), NIH (National Institutes of Health), DOE (Department of Energy), and DARPA (Defense Advanced Research Projects Agency) submissions.

Critical Principle: Grants are persuasive documents that must simultaneously demonstrate scientific rigor, innovation, feasibility, and broader impact. Each agency has distinct priorities, review criteria, formatting requirements, and strategic goals that must be addressed.

When to Use This Skill

This skill should be used when:

  • Writing research proposals for NSF, NIH, DOE, or DARPA programs
  • Preparing project descriptions, specific aims, or technical narratives
  • Developing broader impacts or significance statements
  • Creating research timelines and milestone plans
  • Preparing budget justifications and personnel allocation plans
  • Responding to program solicitations or funding announcements
  • Addressing reviewer comments in resubmissions
  • Planning multi-institutional collaborative proposals
  • Writing preliminary data or feasibility sections
  • Preparing biosketches, CVs, or facilities descriptions

Visual Enhancement with Scientific Schematics

⚠️ MANDATORY: Every research grant proposal MUST include at least 1-2 AI-generated figures using the scientific-schematics skill.

This is not optional. Grant proposals without visual elements are incomplete and less competitive. Before finalizing any document:

  1. Generate at minimum ONE schematic or diagram (e.g., project timeline, methodology flowchart, or conceptual framework)
  2. Prefer 2-3 figures for comprehensive proposals (research workflow, Gantt chart, preliminary data visualization)

How to generate figures:

  • Use the scientific-schematics skill to generate AI-powered publication-quality diagrams
  • Simply describe your desired diagram in natural language
  • Nano Banana Pro will automatically generate, review, and refine the schematic

How to generate schematics:

python scripts/generate_schematic.py "your diagram description" -o figures/output.png

The AI will automatically:

  • Create publication-quality images with proper formatting
  • Review and refine through multiple iterations
  • Ensure accessibility (colorblind-friendly, high contrast)
  • Save outputs in the figures/ directory

When to add schematics:

  • Research methodology and workflow diagrams
  • Project timeline Gantt charts
  • Conceptual framework illustrations
  • System architecture diagrams (for technical proposals)
  • Experimental design flowcharts
  • Broader impacts activity diagrams
  • Collaboration network diagrams
  • Any complex concept that benefits from visualization

For detailed guidance on creating schematics, refer to the scientific-schematics skill documentation.


Agency-Specific Overview

NSF (National Science Foundation)

Mission: Promote the progress of science and advance national health, prosperity, and welfare

Key Features:

  • Intellectual Merit + Broader Impacts (equally weighted)
  • 15-page project description limit (most programs)
  • Emphasis on education, diversity, and societal benefit
  • Collaborative research encouraged
  • Open data and open science emphasis
  • Merit review process with panel + ad hoc reviewers

NIH (National Institutes of Health)

Mission: Enhance health, lengthen life, and reduce illness and disability

Key Features:

  • Specific Aims (1 page) + Research Strategy (12 pages for R01)
  • Significance, Innovation, Approach as core review criteria
  • Preliminary data typically required for R01s
  • Emphasis on rigor, reproducibility, and clinical relevance
  • Modular budgets ($250K increments) for most R01s
  • Multiple resubmission opportunities

DOE (Department of Energy)

Mission: Ensure America's security and prosperity through energy, environmental, and nuclear challenges

Key Features:

  • Focus on energy, climate, computational science, basic energy sciences
  • Often requires cost sharing or industry partnerships
  • Emphasis on national laboratory collaboration
  • Strong computational and experimental integration
  • Energy innovation and commercialization pathways
  • Varies by office (ARPA-E, Office of Science, EERE, etc.)

DARPA (Defense Advanced Research Projects Agency)

Mission: Make pivotal investments in breakthrough technologies for national security

Key Features:

  • High-risk, high-reward transformative research
  • Focus on "DARPA-hard" problems (what if true, who cares)
  • Emphasis on prototypes, demonstrations, and transition paths
  • Often requires multiple phases (feasibility, development, demonstration)
  • Strong project management and milestone tracking
  • Teaming and collaboration often required
  • Varies dramatically by program manager and BAA (Broad Agency Announcement)

Core Components of Research Proposals

1. Executive Summary / Project Summary / Abstract

Every proposal needs a concise overview that communicates the essential elements of the research to both technical reviewers and program officers.

Purpose: Provide a standalone summary that captures the research vision, significance, and approach

Length:

  • NSF: 1 page (Project Summary with separate Overview, Intellectual Merit, Broader Impacts)
  • NIH: 30 lines (Project Summary/Abstract)
  • DOE: Varies (typically 1 page)
  • DARPA: Varies (often 1-2 pages)

Essential Elements:

  • Clear statement of the problem or research question
  • Why this problem matters (significance, urgency, impact)
  • Novel approach or innovation
  • Expected outcomes and deliverables
  • Qualifications of the team
  • Broader impacts or translational pathway

Writing Strategy:

  • Open with a compelling hook that establishes importance
  • Use accessible language (avoid jargon in opening sentences)
  • State specific, measurable objectives
  • Convey enthusiasm and confidence
  • Ensure every sentence adds value (no filler)
  • End with transformative vision or impact statement

Common Mistakes to Avoid:

  • Being too technical or detailed (save for project description)
  • Failing to articulate "why now" or "why this team"
  • Vague objectives or outcomes
  • Neglecting broader impacts or significance
  • Generic statements that could apply to any proposal

2. Project Description / Research Strategy

The core technical narrative that presents the research plan in detail.

Structure Varies by Agency:

NSF Project Description (typically 15 pages):

  • Introduction and background
  • Research objectives and questions
  • Preliminary results (if applicable)
  • Research plan and methodology
  • Timeline and milestones
  • Broader impacts (integrated throughout or separate section)
  • Prior NSF support (if applicable)

NIH Research Strategy (12 pages for R01):

  • Significance (why the problem matters)
  • Innovation (what's novel and transformative)
  • Approach (detailed research plan)
    • Preliminary data
    • Research design and methods
    • Expected outcomes
    • Potential problems and alternative approaches

DOE Project Narrative (varies):

  • Background and significance
  • Technical approach and innovation
  • Qualifications and experience
  • Facilities and resources
  • Project management and timeline

DARPA Technical Volume (varies):

  • Technical challenge and innovation
  • Approach and methodology
  • Schedule and milestones
  • Deliverables and metrics
  • Team qualifications
  • Risk assessment and mitigation

For detailed agency-specific guidance, refer to:

  • references/nsf_guidelines.md
  • references/nih_guidelines.md
  • references/doe_guidelines.md
  • references/darpa_guidelines.md

3. Specific Aims (NIH) or Objectives (NSF/DOE/DARPA)

Clear, testable goals that structure the research plan.

NIH Specific Aims Page (1 page):

  • Opening paragraph: Gap in knowledge and significance
  • Long-term goal and immediate objectives
  • Central hypothesis or research question
  • 2-4 specific aims with sub-aims
  • Expected outcomes and impact
  • Payoff paragraph: Why this matters

Structure for Each Aim:

  • Aim statement (1-2 sentences, starts with action verb)
  • Rationale (why this aim, preliminary data support)
  • Working hypothesis (testable prediction)
  • Approach summary (brief methods overview)
  • Expected outcomes and interpretation

Writing Strategy:

  • Make aims independent but complementary
  • Ensure each aim is achievable within timeline and budget
  • Provide enough detail to judge feasibility
  • Include contingency plans or alternative approaches
  • Use parallel structure across aims
  • Clearly state what will be learned from each aim

For detailed guidance, refer to references/specific_aims_guide.md.

4. Broader Impacts (NSF) / Significance (NIH)

Articulate the societal, educational, or translational value of the research.

NSF Broader Impacts (critical component, equal weight with Intellectual Merit):

NSF explicitly evaluates broader impacts. Address at least one of these areas:

  1. Advancing discovery and understanding while promoting teaching, training, and learning

    • Integration of research and education
    • Training of students and postdocs
    • Curriculum development
    • Educational materials and resources
  2. Broadening participation of underrepresented groups

    • Recruitment and retention strategies
    • Partnerships with minority-serving institutions
    • Outreach to underrepresented communities
    • Mentoring programs
  3. Enhancing infrastructure for research and education

    • Shared facilities or instrumentation
    • Cyberinfrastructure and data resources
    • Community-wide tools or databases
    • Open-source software or methods
  4. Broad dissemination to enhance scientific and technological understanding

    • Public outreach and science communication
    • K-12 educational pr

Content truncated.

software-architecture

davila7

Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.

473163

scroll-experience

davila7

Expert in building immersive scroll-driven experiences - parallax storytelling, scroll animations, interactive narratives, and cinematic web experiences. Like NY Times interactives, Apple product pages, and award-winning web experiences. Makes websites feel like experiences, not just pages. Use when: scroll animation, parallax, scroll storytelling, interactive story, cinematic website.

12580

planning-with-files

davila7

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

7966

humanizer

davila7

Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases. Credits: Original skill by @blader - https://github.com/blader/humanizer

10352

game-development

davila7

Game development orchestrator. Routes to platform-specific skills based on project needs.

14649

2d-games

davila7

2D game development principles. Sprites, tilemaps, physics, camera.

12744

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

1,5711,369

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

1,1161,191

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

1,4181,109

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

1,194747

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

1,154684

pdf-to-markdown

aliceisjustplaying

Convert entire PDF documents to clean, structured Markdown for full context loading. Use this skill when the user wants to extract ALL text from a PDF into context (not grep/search), when discussing or analyzing PDF content in full, when the user mentions "load the whole PDF", "bring the PDF into context", "read the entire PDF", or when partial extraction/grepping would miss important context. This is the preferred method for PDF text extraction over page-by-page or grep approaches.

1,311614

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.