Individual skill
grant-proposal-writer
Writes the full foundation grant proposal for a nonprofit - need statement grounded in local data, a logic model with real numbers (inputs to activities to outputs to outcomes), SMART objectives, an evaluation plan sized to organizational capacity, a budget narrative where every line traces to an activity, and a credible sustainability answer. Use when a nonprofit leader says "write the full grant proposal", "we got invited to submit", "build our logic model", "our proposal needs an evaluation plan", or "the funder wants a budget narrative". Do NOT use for the initial one-page letter of inquiry - use grant-loi-writer instead - and do NOT use for corporate sales proposals - use sales-proposal-writer instead.
skills/grant-proposal-writer/SKILL.md
Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 24
- Repository last updated
- Oct 13, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 10,408 bytes
Read excerpt
# Grant Proposal Writer
The full proposal is where invited organizations lose grants they should win: national statistics standing in for local need, outcomes that are really activities, an evaluation plan the organization cannot execute, and a budget that does not match the narrative. Program officers read for exactly these four failures. This skill builds the proposal in dependency order so each section is forced to agree with the others. It is third in the grants pipeline: it starts from the LOI that grant-loi-writer got invited, and its numbers must match that LOI exactly - a proposal that contradicts its own LOI reads as an organization that does not know its numbers.
Work the example organization throughout: Bright Futures Tutoring, a youth-education nonprofit with a $420,000 annual budget, 3 staff, serving 250 students, invited by the Hearthstone Foundation to propose for $75,000 to expand to 325 students.
## Operating procedure
Build in this order - logic model before objectives, objectives before evaluation, activities before budget - because each section is derived from the previous one, and writing them independently is how contradictions get in.
### Step 1: Fix the baseline numbers
Copy the LOI's numbers as immutable: ask amount, duration, what it buys, scale, headline outcome. Collect the rest: program costs by line, staff roles and salaries allocated to the program, outcome data from the last two years with sources, and the local need data. Label every guessed number as a guess and resolve it before submission.
