← ClaudeAtlas

grant-pipelinelisted

End-to-end grant-writing pipeline — from a NOFO / fact-sheet / funding opportunity to a submitted application, letters of support, a team briefing, and a tracked record. Use whenever the user shares a grant notice or asks to write a grant application, letters of support, or a grant briefing. Triggers on any "we should apply for this" conversation.
DanielOnPurpose/danielonpurpose-skills · ★ 0 · Data & Documents · score 55
Install: claude install-skill DanielOnPurpose/danielonpurpose-skills
# Grant Pipeline A repeatable loop for turning a funding opportunity into a submitted, rubric-aligned application. Follow it end to end. ## Step 1 — Notice intake From the PDF/URL, extract a structured brief: - Eligibility (and which entity is the right applicant) - **Scoring rubric** — every point category and weight; the application is written to the rubric - Match requirement and deadline (compute days remaining) - Prerequisites: required resolutions, registrations (e.g. SAM.gov), estimates, letters - Required attachments checklist ## Step 2 — Clarifying questions Ask a NUMBERED list of only the questions that block drafting. Rules: - "I don't know" is a valid answer → draft anyway with a clearly flagged `[PLACEHOLDER: …]`, never block on it. - Pull known facts from existing files/notes before asking. ## Step 3 — Draft the application - Write to the scoring rubric, section by section. - Save as **.docx** (most teams work in Word/Google Docs, not markdown) in the project folder. - Flag every unknown as `[PLACEHOLDER: what's needed + who likely has it]`. ## Step 4 — Letters of support Keep a standing signatory bench (partner orgs, institutions, local officials). Tone rules: - **Civic / community pride** for elected officials - **Operational / fiscal** for administrators - **Programmatic partnership** for institutions Each letter: one page, .docx, ready for letterhead. ## Step 5 — Team briefing Draft the internal briefing (use the `team-memo` style): warm and coll