- Home
- Skills
- Business & Operations
- Foundation Report Handoffs
Works with the AI Agents you already use
Foundation Report Handoffs
That gap is where deadlines slip and unverified claims sneak into a funder submission.
$9.99
Foundation Report Handoffs
Example session with this skill installed
We have a $75k foundation grant report due in 30 days. Program has the outcomes, finance has the spend, and development manages the funder - but it's unclear who owns what and some numbers aren't verified yet. Help me get this under control.
- Read your context and instructions
- Compiled the foundation report handoffs
**Foundation Report Handoff Pack:** $75k grant, 30-day deadline **Truth boundary:** Do not invent outcomes, financials, consent, funder requirements, or approvals. This is an internal prep tool, not proof of compliance or acceptance. ## Reporting-readiness position Deadline [DATE, ~30 days out]. Known: program outcomes drafted, finance spend available. Missing: verified figures, funder's exact required sections [NEEDS SOURCE], attachment approvals. Main risk: unclear ownership + unverified numbers reaching the funder. ## Funder requirement map | Requirement | Evidence needed | Owner | Reviewer | Due | Status | Source | |---|---|---|---|---|---|---| | Narrative outcomes | Program results + stories (consented) | Program | Development | [DATE] | DRAFT | [NEEDS SOURCE] | | Financial report | Budget vs actuals + variance | Finance | Leadership | [DATE] | NEEDS SOURCE | [funder template?] | | Attachments | Receipts / photos (approved) | Development | Comms | [DATE] | MISSING | - | ## Ownership & RACI map Development = Accountable (coordinates + funder). Program = Responsible (outcomes). Finance = Responsible (figures) / Consulted on totals. Leadership = Approver. Comms = Consulted (public language + consent). ## Missing-input queue | Gap | Why it matters | Requested from | Due | Blocker | Next move | |---|---|---|---|---|---| | Verified actuals vs budget | Funder requires financial accuracy | Finance owner | [DATE] | P0 | Send finance validation request | | Funder's exact required sections | Wrong format = rejection | Development/funder | [DATE] | P0 | Confirm from grant agreement | | Beneficiary story consent | No consent = cannot include | Program/Comms | [DATE] | P1 | Request approval | ## Copy-ready request messages Initial (to Program & Finance): "For the [Funder] report due [DATE], please send by [DATE]: [exact fields]. Format: [X]. If any data is unavailable, flag it - do not estimate." Finance validation, reminder, escalation and final-approval messages: [provided, ready to send]. ## Claim-to-evidence matrix + Attachment register [Tables flagging every claim without a source and every attachment without an owner/approval.] ## Review gates Source -> Program -> Finance -> Evidence -> Privacy/Consent -> Development -> Leadership. Any draft narrative labeled DRAFT - HUMAN REVIEW REQUIRED. ## Approval-ready handoff summary Deadline [DATE] | Ready now: program draft | Blocked by: verified financials, consent | Owners with open actions: Finance, Program | Next checkpoint: [DATE] | Final approver: [ROLE] | Submission status: NOT SUBMITTED ## To sharpen this pack further (optional) 1. What are the funder's exact required sections/word limits? 2. Who is the named finance owner and approver? 3. Any privacy or consent constraints on stories/photos?
Connects securely to your tools. The creator never sees your data.
About this skill
## The report isn't the problem - the coordination is The grant report is due in 30 days. Program has the outcomes, finance has the numbers, development owns the funder relationship - and nobody is quite sure who owns what, which figures are verified, or which attachments are approved. That gap is where deadlines slip and unverified claims sneak into a funder submission. This skill closes the gap. It is built for ownership and evidence handoff, not generic grant writing. Give it whatever you have - even a pasted funder instruction and a deadline - and your agent returns a complete coordination control pack, ready to run across every reporting cycle. ## What you get in every pack 1. **A reporting-readiness position** - what's known, what's missing, the deadline, and the main coordination risk, with a plain truth boundary: it's an internal prep tool, not proof of compliance or acceptance 2. **A funder requirement map** - funder instructions normalized into a table (requirement, evidence needed, owner, reviewer, due date, status, source) with honest status flags (CONFIRMED / NEEDS SOURCE / MISSING / IN REVIEW / APPROVED / BLOCKED) 3. **An ownership & RACI map** - who is Responsible, Accountable, Consulted and Informed for each input, before any drafting starts 4. **A missing-input queue** - every gap with owner, request date, due date, blocker level (P0/P1/P2) and next move 5. **Copy-ready request messages** - initial request, reminder, escalation, finance validation and final approval - each ready to send 6. **Claim-to-evidence & attachment controls** - flag every claim without a source, figure without a finance check, story without consent, and attachment without a known owner or version 7. **Seven review gates + an approval-ready handoff summary** - source, program, finance, evidence, privacy/consent, development and leadership gates, ending in a compact status block that always reads NOT SUBMITTED until a human confirms ## Why it works It encodes how clean reporting actually happens: ownership before drafting, stateful tracking of every missing input, staged requests instead of chaotic email threads, and evidence controls that catch unsourced claims before a funder does. It is reusable cycle after cycle. And it is safe by design: it never invents outcomes, beneficiary stories, budgets, dates, funder rules or approvals; it never backdates evidence or certifies compliance; it minimizes personal and beneficiary data; and it converts any legal, tax or audit question into a verification question for the qualified person. Unknowns stay as placeholders and status flags - never fake facts. Works for nonprofits, funded projects and program teams reporting to any foundation or post-award funder. Text-only skill: no scripts, no network calls, zero extra permissions. Tested on Claude.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Business & Operations.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago
Permissions
No special permissions declared or detected