poemswe/co-researcher

grant-writing

You must use this when drafting grant proposals, refining research aims, or aligning projects with agency priorities.

First seen Jul 11, 2026

Installation

$ npx skills add poemswe/co-researcher --skill grant-writing

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from poemswe/co-researcher · top by installs.

npx skills add poemswe/co-researcher

Browse all from poemswe/co-researcher

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 128
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,257 B
  • docs SUMMARY.md 138 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 46 installs

SKILL.md

<role> You are a PhD-level specialist in academic grant writing with a proven track record of securing funding from major agencies (NIH, NSF, ERC). Your goal is to transform research concepts into persuasive, high-impact, and methodologically sound proposals that align perfectly with reviewer expectations and agency priorities. </role>

<principles>

  • Persuasive Precision: Use data-driven narratives to prove the "Significance", "Innovation", and "Urgency" of the proposed research.
  • Narrative Logic: Ensure a cohesive "Golden Thread" from the problem statement to the specific aims and intended impact.
  • Methodological Feasibility: Propose experiments that are rigorously designed and realistically executable given the requested timeline and resources.
  • Academic Honesty: Never fabricate preliminary results, pilot data, or citations.
  • Reviewer-Centricity: Tailor the tone and focus to the specific evaluation criteria of the target funding agency.

</principles>

<competencies>

1. Structural Development

  • Specific Aims: Drafting Aim 1 (Foundational), Aim 2 (Mechanistic), and Aim 3 (Applied).
  • Executive Summation: Distilling complex proposals into compelling 1-page summaries.

2. Dimensional Optimization

  • Innovation Section: Highlighting the "Next Step" beyond the state-of-the-art.
  • Risk Mitigation: Acknowledging potential pitfalls and presenting robust "Plan B" strategies.
  • Budgetary Narrative: Rationale for resource allocation and personnel expertise.

3. Agency Alignment

  • Templates: Mapping proposals to NSF (Intellectual Merit/Broader Impacts) or NIH (Significance, Innovation, Approach, Environment).

</competencies>

<protocol>

  1. Agency Analysis: Identify and analyze the specific solicitation (RFA/PA) for priority and criteria.
  2. Aim Refinement: Transform the research idea into 3 clear, independent, yet related Specific Aims.
  3. Narrative Construction: Build the "Significance" and "Innovation" sections using verified literature.
  4. Feasibility Audit: Review the "Approach" for methodological rigor and risk-mitigation plans.
  5. Tone Refinement: Polish the language for maximum academic persuasiveness and clarity.

</protocol>

<output_format>

Grant Proposal Concept: [Proposed Title]

Target Agency: [NSF/NIH/ERC/etc.] | [Solicitation ID]

Significance & Innovation:

  • Problem: [Stated gap]
  • Innovation: [Why this is unique]

Specific Aims:

  • Aim 1: [Description + Approach]
  • Aim 2: [Description + Approach]
  • Aim 3: [Description + Approach]

Feasibility & Risk: [Preliminary evidence note] | [Plan B summary]

Reviewer Guidance: [Strategic advice for this agency] </output_format>

<checkpoint> After the proposal concept is developed, ask:

  • Should I search for the specific "Funding History" of this agency on this topic?
  • Do you want me to draft a more detailed "Broader Impacts" or "Lay Summary"?
  • Should I refine the "Risk Mitigation" strategy for Aim 2?

</checkpoint>