Skip to content
Back to skills

Statement Of Need

ASecurity

Draft the statement of need, problem statement, significance, or background section of a grant proposal. Covers evidence hierarchy, framing the problem around the population served rather than the applicant's funding gap, connecting local data to the funder's priorities, and avoiding deficit-based language.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 5, 2026
ai-agents

Security analysis

A100/100

Scanned September 5, 2026

npx -y skills add darylalim/grant-writer-agent --skill statement-of-need --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Statement Of Need?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Statement Of Need
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/darylalim-statement-of-need/badge)](https://www.skillsdirectory.com/skills/darylalim-statement-of-need)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: statement-of-need
description: Draft the statement of need, problem statement, significance, or background section of a grant proposal. Covers evidence hierarchy, framing the problem around the population served rather than the applicant's funding gap, connecting local data to the funder's priorities, and avoiding deficit-based language.
---

# Statement of Need

## Overview

This section answers one reviewer question: *is this problem real, urgent, and
worth this funder's money?* It is not about the applicant. Nothing about the
organization's budget shortfall belongs here.

## When to Use

Drafting a statement of need, problem statement, background, or significance
section.

## Instructions

### Structure

1. **The problem, in one sentence.** Specific population, specific place,
   specific harm. Open with it — do not build up to it.
2. **Scale and severity.** Quantified, cited, and as local as the data allows.
3. **Why it persists.** What existing services do not reach or do not solve.
   This is where you earn the right to propose something.
4. **Consequences of inaction.** Concrete downstream costs.
5. **Bridge to the approach.** One or two sentences pointing at the solution,
   without drafting the approach section here.

### Evidence hierarchy

Prefer, in order:

1. The applicant's own service data (waitlists, intake numbers, outcomes).
2. Local or regional administrative data (school district, county health,
   census tract).
3. State-level data.
4. Peer-reviewed literature establishing the mechanism.
5. National statistics — weakest, because reviewers have read them before and
   they do not establish local need.

Every statistic needs a source and a year. A statistic older than five years
needs a reason for being there.

### Framing

- **Assets, not deficits.** Describe conditions and structural barriers, not
  deficient people. "Families in the service area face a 14-mile average
  distance to the nearest pediatric provider" — not "families fail to seek
  care."
- **Mirror the funder's framing.** If the solicitation talks about "systems
  change", show the systemic driver, not just individual hardship.
- **Name the population precisely.** Age range, geography, and the criteria
  that define eligibility for services.

## Rules

- Never invent or estimate a statistic. If you need a number you do not have,
  write `[NEEDS INPUT: <precise question, including the geography and year>]`.
- No claim that the organization is uniquely qualified — that belongs in
  organizational capacity.
- Cut every instance of "innovative", "critical", "vital", and "urgent" used as
  an adjective rather than demonstrated by evidence.
- Confirm length with `measure_text` before finishing.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.