Research Grants
K-Dense-AI/claude-scientific-writer
Write competitive research proposals for NSF, NIH, DOE, DARPA, and Taiwan NSTC.
Grant writing and proposal architecture: funder fit, proposal structure, budget design, and success-factor scoring.
Install Grants
$ npx skills add borghei/Claude-Skills --skill grants -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills grants --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/research/grants .claude/skills/grants && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "grants" agent skill from https://github.com/borghei/Claude-Skills/tree/main/research/grants into .claude/skills/grants/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grants", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/research/grantsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill grants -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills grants --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/research/grants .agents/skills/grants && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "grants" agent skill from https://github.com/borghei/Claude-Skills/tree/main/research/grants into .agents/skills/grants/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grants", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill grants -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills grants --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/research/grants .cursor/skills/grants && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "grants" agent skill from https://github.com/borghei/Claude-Skills/tree/main/research/grants into .cursor/skills/grants/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grants", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path research/grants--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill grants -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills grants --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/research/grants .gemini/skills/grants && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "grants" agent skill from https://github.com/borghei/Claude-Skills/tree/main/research/grants into .gemini/skills/grants/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grants", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills grantsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill grants -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/research/grants .github/skills/grants && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "grants" agent skill from https://github.com/borghei/Claude-Skills/tree/main/research/grants into .github/skills/grants/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grants", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill grants -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills grants --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/research/grants .opencode/skills/grants && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "grants" agent skill from https://github.com/borghei/Claude-Skills/tree/main/research/grants into .opencode/skills/grants/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grants", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
grants- GitHub stars
- 874
- Token cost
- ~1.8k tokens
- SKILL.md length
- 806 words
- Files
- 7 (incl. scripts, references)
- Skills in repo
- 364
- Repo updated
- First seen
- Licence
- MIT
At a glance
Grant writing and proposal architecture: funder fit, proposal structure, budget design, and success-factor scoring.
- Works in 3 steps: Capture funder, program, project idea,… → Run funder_fit_scorer.py to grade fit on… → If fit < 65, look for better-aligned…
- Writing a grant proposal
- SKILL.md covers When to use this skill, Inputs the advisor expects, Clarify First and Workflows, plus 5 more sections
- Runs Python scripts from its folder; calls python3
What it does
Grants is an agent skill from borghei/Claude-Skills. Grant writing and proposal architecture: funder fit, proposal structure, budget design, and success-factor scoring. Use when writing a grant proposal, evaluating funder fit, auditing a draft for competitiveness, or planning a budget.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `references/budget-design-and-justification.md`, `references/funder-fit-and-research-strategy.md` and `references/proposal-structure-and-narrative.md`).
It sits in Research & Science, covering Grant writing and Proposals and quotes. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Writing a grant proposal
- Evaluating funder fit
- Auditing a draft for competitiveness
- Planning a budget
Example prompts
- “/grants”
Requirements
- Python 3
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Capture funder, program, project idea, team strengths.
- Run funder_fit_scorer.py to grade fit on 7 dimensions.
- If fit < 65, look for better-aligned funder; don't waste 4 weeks.
What it can do on your machine
Read from SKILL.md and the folder at commit c9a1487. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Grants loads about 1.8k tokens when it runs, and up to ~7.3k if it reads all its reference files. Until then it costs about 60 tokens; SKILL.md has 806 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from borghei/Claude-Skills at commit c9a1487, republished under its MIT licence (© borghei). 806 words, ~1,757 tokens.
Download SKILL.mdSave it as
.claude/skills/grants/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- grants
- description
- Grant writing and proposal architecture: funder fit, proposal structure, budget design, and success-factor scoring. Use when writing a grant proposal, evaluating funder fit, auditing a draft for competitiveness, or planning a budget.
- license
- MIT + Commons Clause
- metadata.version
- 1.0.0
- metadata.author
- borghei
- metadata.category
- research
- metadata.domain
- research
- metadata.updated
- 2026-05-27
- metadata.tags
- grants, proposals, funding, nih, nsf, foundation, research, budget
Grant Writing & Proposal Architecture
A skill for crafting competitive grant proposals across funder types: government (NIH, NSF, DOE, ARPA), foundation, corporate, philanthropic, and SBIR / STTR. Focuses on the architecture of a winning proposal: fit, structure, narrative, budget — not boilerplate templating.
When to use this skill
- Evaluating funder fit before investing weeks in a proposal
- Designing the proposal structure for a specific funder
- Writing or auditing the narrative for competitiveness
- Designing a realistic, defensible budget
- Pre-submission proposal review for common failure modes
- Building a grants strategy (which to apply to over the year)
Inputs the advisor expects
- The funder name + specific program / RFP
- The research / project idea (problem, approach, outcomes)
- Team composition (PI, co-investigators, key personnel)
- Institutional / org context
- Past funding history
- Budget envelope (or constraint)
- Submission deadline
Clarify First
Before generating the proposal, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- Funder + specific program / RFP — sets the mental model (NIH 5-criteria vs NSF merit+impact vs foundation mission fit); drives structure and narrative
- Project idea (problem, approach, outcomes) — drives the significance/innovation narrative and the Heilmeier answers
- Budget envelope — drives budget design and whether scope matches the funder's typical award size
- Team composition (PI, key personnel) — drives the investigator/environment fit dimension
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Workflows
Workflow 1 — Score funder fit before committing
- Capture funder, program, project idea, team strengths.
- Run
funder_fit_scorer.pyto grade fit on 7 dimensions. - If fit < 65, look for better-aligned funder; don't waste 4 weeks.
python3 grants/scripts/funder_fit_scorer.py \
--input funder_fit.json --format markdownWorkflow 2 — Validate proposal structure against funder expectations
- Capture the proposal section list + page allocation.
- Run
proposal_structure_validator.pyagainst funder type expectations. - Adjust before drafting deep.
python3 grants/scripts/proposal_structure_validator.py \
--input proposal_structure.json --funder-type nih --format markdownWorkflow 3 — Audit budget for realism
- Capture budget line items with justifications.
- Run
budget_realism_checker.pyagainst funder norms + project scope. - Adjust before submission.
python3 grants/scripts/budget_realism_checker.py \
--input budget.json --format markdownDecision frameworks
Funder fit dimensions
- Topic alignment — does the funder fund this area?
- Mechanism alignment — does the funder fund this kind of work (R&D, services, scale-up)?
- Stage alignment — early-stage / mid / scale?
- Geographic alignment — does the funder fund your region?
- Team profile alignment — does the funder fund your kind of team?
- Budget envelope alignment — does the funder's typical award size match?
- Competitive density — is it 5% acceptance or 35%?
A score below 65 across these is usually a "skip this funder" signal.
Funder type — distinct mental models
| Funder type | Emphasizes | De-emphasizes |
|---|---|---|
| NIH | Significance + innovation + approach + investigator + environment (5 criteria) | Commercial outcome |
| NSF | Intellectual merit + broader impacts | Direct commercial outcome |
| ARPA / DARPA | Heilmeier catechism (defined moonshot question) | Incremental work |
| SBIR / STTR | Commercial path + technical risk | Pure science |
| Foundation | Mission fit + measurable outcomes | Pure academic novelty |
| Corporate | Commercial relevance to sponsor | Independence from sponsor |
| Crowdfunding | Story + community appeal | Technical rigor |
Write to the funder's mental model, not a generic "good grant."
Show full SKILL.md (318 more words)Show less
The Heilmeier catechism (good for any proposal)
- What are you trying to do?
- How is it done today; what are the limits?
- What's new in your approach; why succeed?
- Who cares; if you succeed, what difference does it make?
- What are the risks; how will you mitigate?
- How much will it cost; how long?
- What are the mid-term + final outcomes you'll deliver?
A proposal that can't answer all seven crisply isn't ready.
Common engagements
"Help me decide between two RFPs"
- Score both for fit; the higher one is usually right.
- If close: which has earlier deadline / smaller proposal effort?
- Don't submit to both same year unless funders are independent.
"Audit my draft proposal"
- Check funder-fit assumptions (did the program actually fund what you're proposing?)
- Check structure against funder template
- Check narrative: is the problem compelling? approach novel?
- Check budget: realistic + justified
- Check team credentials: matches scope?
- Read for: jargon, vague claims, unjustified assumptions
"We've never applied for an NIH R01. What's the prep?"
- Smaller grant first (R21, K, F32) if eligible — build track record
- Talk to a program officer before drafting (essential)
- Pre-submission inquiry where allowed
- Get a mock review from someone who's reviewed for NIH
Anti-patterns to avoid
- Applying without funder fit. Wastes 4-8 weeks.
- Generic proposal sent to multiple funders. Each wants a specific mental model.
- Budget that doesn't match scope. Reviewer red flag.
- Vague significance statement. "This is important" without specifics.
- No risk discussion. Reviewers know there's risk; not acknowledging it = naive.
- Team without right credentials. Match key personnel to scope.
- Submitting at last minute. Errors; missed letters of support.
References
references/funder-fit-and-research-strategy.md— fit dimensions, funder types, multi-funder strategyreferences/proposal-structure-and-narrative.md— per-funder structures, narrative disciplinereferences/budget-design-and-justification.md— budget categories, indirect costs, common errors
Related skills
research/litreview— literature review for proposalsc-level-advisor/general-counsel-advisor— legal review of termsc-level-advisor/cfo-advisor— financial review
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 6 other files (scripts, references) in research/grants of borghei/Claude-Skills.
- SKILL.md
- references/budget-design-and-justification.md
- references/funder-fit-and-research-strategy.md
- references/proposal-structure-and-narrative.md
- scripts/budget_realism_checker.py
- scripts/funder_fit_scorer.py
- scripts/proposal_structure_validator.py
Open the folder on GitHubat commit c9a1487
Compare with similar skills
Grants next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Grants this skillborghei/Claude-Skills | 874 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Research GrantsK-Dense-AI/claude-scientific-writer | 2.4k | 16 repos | ~3.6k | Automated safety check: Notes | MIT | |
| Research Grantsaipoch/medical-research-skills | 2k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Grant Writing Guidewentorai/research-plugins | 298 | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Academic HumanizerAIScientists-Dev/academic-humanizer | 1.8k | 1 repos | ~4.2k | Automated safety check: Pass | MIT | |
| Mechanical Engineering Researchccplugins/awesome-claude-code-plugins | 967 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Research Grants
aipoch/medical-research-skills
Write competitive research proposals for NSF, NIH, DOE, DARPA, and Taiwan's NSTC when you need agency-compliant narratives, budgets, and review-criteria alignment for a specific solicitation/FOA/BAA.
Grant Writing Guide
wentorai/research-plugins
Write competitive research proposals with clear objectives and budgets
Academic Humanizer
AIScientists-Dev/academic-humanizer
Improve the clarity and voice of AI-assisted academic writing (papers, theses, rebuttals) and funding proposals (NSF Project Summary/Description, NIH Specific Aims): preserve scholarly conventions…
Mechanical Engineering Research
ccplugins/awesome-claude-code-plugins
Research, write, code, analyze, present, and develop proposals for thermal-fluid mechanical engineering work with source-aware rigor.
Business Proposal
FerroxLabs/wayland
Writes structured business proposals with executive summary, scope of work, pricing, timeline, and next steps for client-facing or vendor engagements.
More from borghei/Claude-Skills
All 364 skills in this repoAgents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Brainstorm Okrs
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Related
Categories
Questions about Grants
What does Grants do?
Grant writing and proposal architecture: funder fit, proposal structure, budget design, and success-factor scoring. Grants is an agent skill from borghei/Claude-Skills. Grant writing and proposal architecture: funder fit, proposal structure, budget design, and success-factor scoring.
When should I use Grants?
Grants fits situations like: writing a grant proposal; evaluating funder fit; auditing a draft for competitiveness; planning a budget.
How do I install Grants in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill grants -a claude-code`. Or copy the skill folder (research/grants in borghei/Claude-Skills) into .claude/skills/grants in your project. Claude Code loads it when a task matches its description.
How do I install Grants in Codex?
Run `npx skills add borghei/Claude-Skills --skill grants -a codex`. Or copy the skill folder (research/grants in borghei/Claude-Skills) into .agents/skills/grants in your project. Codex loads it when a task matches its description.
Can I use Grants in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill grants -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/grants, .gemini/skills/grants, .github/skills/grants and .opencode/skills/grants in your project.
What does Grants need to run?
Going by SKILL.md and its folder, Grants needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Grants access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Grants safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Grants use?
Grants is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Grants use?
About 1.8k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.5k tokens, read only when the agent opens those files.
What are the alternatives to Grants?
Skills that share tags, products or a category with Grants: Research Grants (K-Dense-AI/claude-scientific-writer, 2.4k stars), Research Grants (aipoch/medical-research-skills, 2k stars), Grant Writing Guide (wentorai/research-plugins, 298 stars) and Academic Humanizer (AIScientists-Dev/academic-humanizer, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Grants?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 874 GitHub stars. The repository holds 364 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.