Skill Tracer
Skills › Scientific Agent Skills › research-grants › writing_principles.md

writing_principles.md

99 lines · skills/research-grants/references/writing_principles.md at 5f2bc03

Open on GitHub
1# Writing Principles for Competitive Proposals
2
3Framing, specificity, reviewer psychology, and readability — the practices that separate
4funded proposals from merely competent ones.
5
6Reviewed 2026-10-01. These are writing heuristics, not agency rules or predictors of
7funding. Preserve investigator authorship, check the selected opportunity's AI policy,
8and ground every factual assertion, preliminary result and commitment in evidence.
9Label projections and unknowns rather than polishing them into apparent facts.

Writing Principles for Competitive Proposals

Framing, specificity, reviewer psychology, and readability — the practices that separate funded proposals from merely competent ones.

Reviewed 2026-10-01. These are writing heuristics, not agency rules or predictors of funding. Preserve investigator authorship, check the selected opportunity's AI policy, and ground every factual assertion, preliminary result and commitment in evidence. Label projections and unknowns rather than polishing them into apparent facts.

Raw lines 1 to 10
11## Writing Principles for Competitive Proposals

Writing Principles for Competitive Proposals

Raw lines 11 to 12
13### Clarity and Accessibility
15**Write for Multiple Audiences**:
16- Technical reviewers in your field (will scrutinize methods)
17- Reviewers in related but not identical fields (need context)
18- Program officers (look for alignment with agency goals)
19- Panel members with limited review time (need clear organization)
21**Strategies**:
22- Use clear section headings and subheadings
23- Start sections with overview paragraphs
24- Define technical terms and abbreviations
25- Use figures, diagrams, and tables to clarify complex ideas
26- Avoid jargon when possible; explain when necessary
27- Use topic sentences to guide readers

Clarity and Accessibility

Write for Multiple Audiences:

  • Technical reviewers in your field (will scrutinize methods)
  • Reviewers in related but not identical fields (need context)
  • Program officers (look for alignment with agency goals)
  • Panel members with limited review time (need clear organization)

Strategies:

  • Use clear section headings and subheadings
  • Start sections with overview paragraphs
  • Define technical terms and abbreviations
  • Use figures, diagrams, and tables to clarify complex ideas
  • Avoid jargon when possible; explain when necessary
  • Use topic sentences to guide readers
Raw lines 13 to 28
29### Persuasive Argumentation
31**Build a Compelling Narrative**:
32- Establish the problem and its importance
33- Show gaps in current knowledge or approaches
34- Present your solution as innovative and feasible
35- Demonstrate that you're the right team
36- Show that success will have significant impact
38**Structure of Persuasion**:
391. **Hook**: Capture attention with significance
402. **Problem**: Establish what's not known or not working
413. **Solution**: Present your innovative approach
424. **Evidence**: Support with preliminary data
435. **Impact**: Show transformative potential
446. **Team**: Demonstrate capability to deliver
46**Language Choices**:
47- Use active voice for clarity and confidence
48- Choose strong verbs (investigate, elucidate, discover vs. look at, study)
49- Be confident but not arrogant (avoid "obviously," "clearly")
50- Acknowledge uncertainty appropriately
51- Use precise language (avoid vague terms like "several," "various")

Persuasive Argumentation

Build a Compelling Narrative:

  • Establish the problem and its importance
  • Show gaps in current knowledge or approaches
  • Present your solution as innovative and feasible
  • Demonstrate that you're the right team
  • Show that success will have significant impact

Structure of Persuasion:

  1. Hook: Capture attention with significance
  2. Problem: Establish what's not known or not working
  3. Solution: Present your innovative approach
  4. Evidence: Support with preliminary data
  5. Impact: Show transformative potential
  6. Team: Demonstrate capability to deliver

Language Choices:

  • Use active voice for clarity and confidence
  • Choose strong verbs (investigate, elucidate, discover vs. look at, study)
  • Be confident but not arrogant (avoid "obviously," "clearly")
  • Acknowledge uncertainty appropriately
  • Use precise language (avoid vague terms like "several," "various")
Raw lines 29 to 52
53### Visual Communication
55**Effective Use of Figures**:
56- Conceptual diagrams showing research framework
57- Preliminary data demonstrating feasibility
58- Timelines and Gantt charts
59- Workflow diagrams showing methodology
60- Expected results or predictions
62**Design Principles**:
63- Make figures self-explanatory with complete captions
64- Use consistent color schemes and fonts
65- Ensure readability (large enough fonts, clear labels)
66- Integrate figures with text (refer to specific figures)
67- Follow agency-specific formatting requirements

Visual Communication

Effective Use of Figures:

  • Conceptual diagrams showing research framework
  • Preliminary data demonstrating feasibility
  • Timelines and Gantt charts
  • Workflow diagrams showing methodology
  • Expected results or predictions

Design Principles:

  • Make figures self-explanatory with complete captions
  • Use consistent color schemes and fonts
  • Ensure readability (large enough fonts, clear labels)
  • Integrate figures with text (refer to specific figures)
  • Follow agency-specific formatting requirements
Raw lines 53 to 68
69### Addressing Risk and Feasibility
71**Balance Innovation and Risk**:
72- Acknowledge potential challenges
73- Provide alternative approaches
74- Show preliminary data reducing risk
75- Demonstrate expertise to handle challenges
76- Include contingency plans
78**Common Concerns**:
79- Too ambitious for timeline/budget
80- Technically infeasible
81- Team lacks necessary expertise
82- Preliminary data insufficient
83- Methods not adequately described
84- Lack of innovation or significance

Addressing Risk and Feasibility

Balance Innovation and Risk:

  • Acknowledge potential challenges
  • Provide alternative approaches
  • Show preliminary data reducing risk
  • Demonstrate expertise to handle challenges
  • Include contingency plans

Common Concerns:

  • Too ambitious for timeline/budget
  • Technically infeasible
  • Team lacks necessary expertise
  • Preliminary data insufficient
  • Methods not adequately described
  • Lack of innovation or significance
Raw lines 69 to 85
86### Integration and Coherence
88**Ensure All Parts Align**:
89- Budget supports activities in project description
90- Timeline matches aims and milestones
91- Team composition matches required expertise
92- Broader impacts connect to research plan
93- Letters of support confirm stated collaborations
95**Avoid Contradictions**:
96- Preliminary data vs. stated gaps
97- Claimed expertise vs. publication record
98- Stated aims vs. actual methods
99- Budget vs. stated activities

Integration and Coherence

Ensure All Parts Align:

  • Budget supports activities in project description
  • Timeline matches aims and milestones
  • Team composition matches required expertise
  • Broader impacts connect to research plan
  • Letters of support confirm stated collaborations

Avoid Contradictions:

  • Preliminary data vs. stated gaps
  • Claimed expertise vs. publication record
  • Stated aims vs. actual methods
  • Budget vs. stated activities
Raw lines 86 to 99