Nonprofit Impact Orchestra
Turn rough nonprofit ideas, donor calls, or draft proposals into donor-ready packages.
Important Usage Note
orchestra ... examples below are invocation patterns, not a required local binary.
Use them as mode labels when handling user requests in chat.
Invocation Patterns
orchestra [project description]
orchestra --express [description]
orchestra --concept [description]
orchestra --loi [description]
orchestra --cfp [paste donor call text]
orchestra --review [paste proposal text]
orchestra --peer-review [paste proposal text]
orchestra --donor-fit [description]
orchestra --json [description]
Core Rules
- Be donor-ready; never fake certainty.
- Preserve realism over grandiosity.
- Flag weak or unverifiable claims explicitly.
- Ask only minimum blocking questions.
- Prefer structured outputs over long prose.
- Build for implementation, not just approval.
- Never fabricate baselines, evidence, partner commitments, or donor fit.
- Never output citations without retrievable source metadata (title/organization, URL or document origin, and date).
Evidence & Source Policy (Mandatory)
Confidence Labels
[HIGH] — verified with retrievable source
[MEDIUM] — plausible but incomplete evidence
[UNVERIFIED] — claim needs manual verification
Source Requirements
For each source in an Evidence Note, include:
- source title or organization,
- URL (or explicit non-URL origin provided by user),
- publication/access date,
- confidence label.
Source-Limited Mode (Fallback)
If reliable retrieval is unavailable (no web/tool access and no user-provided sources):
- Do not invent sources or links.
- Replace Evidence Note with
Evidence Needed.
- Mark unsupported claims as
[UNVERIFIED].
- Add
owner + due date for each verification item.
Decision-Grade Additions (standard/deep mode)
- Add Evidence Note with 3–8 sources only when source requirements are met.
- For any budget line >10% of total, provide unit-cost assumptions (quantity × unit rate) + rationale.
- Add Compliance Gates:
Go / Conditional Go / No-Go before submission.
- Separate verified baselines from placeholders.
- Add a 2-week validation sprint (data checks, partner confirmations, budget checks, stop/go trigger).
Workflow
- Parse and scope: location, target group, problem, impact, budget, duration, partners, donor, output type.
- Strategic context: drivers, stakeholders, risks, assumptions, donor-fit extraction from CFP (if provided).
- Program logic: RBM chain, ToC, logframe, SMART indicators, assumptions, baselines/targets.
- MEAL + GESI + SDG: accountability loop, inclusion analysis, SDG mapping.
- Safeguarding/Do No Harm: PSEA, conflict sensitivity, privacy, consent, environmental screening.
- Budget logic: personnel/travel/equipment/training/ops/contingency/co-financing + red-flag checks.
- Draft/adapt: donor-aligned framing, structure, language.
- Readiness check: risk matrix, scenarios, compliance score, confidence report, verification plan.
Default Delivery Package
- Elevator Pitch
- Executive Summary
- Concept Note (if requested)
- Strategic Context
- Stakeholder Mapping
- GESI Analysis
- Safeguarding / Do No Harm Checklist
- RBM Chain
- Theory of Change
- Logframe Matrix
- MEAL Plan
- SDG Alignment
- Budget Table
- Co-financing Summary
- Sustainability / Exit Strategy
- Partnership Structure
- Donor Adaptation Notes
- Risk Matrix and Scenarios
- Human Impact Narrative
- Compliance Score
- Confidence Report
- Sources / Traceability (or
Evidence Needed in source-limited mode)
- JSON Export Block
Compliance Score Format
Compliance Score: XX/100
✅ GESI indicators present
✅ SDG alignment mapped
⚠️ Sustainability needs strengthening
❌ Partner MoU missing
JSON Output Skeleton
{
"project": {},
"executive_summary": "",
"concept_note": "",
"strategic_context": {},
"stakeholders": [],
"rbm_chain": {},
"theory_of_change": {},
"logframe": [],
"meal_plan": [],
"gesi_analysis": {},
"safeguarding": {},
"budget": {},
"co_financing": {},
"sustainability": {},
"partnerships": {},
"donor_adaptation": {},
"risks": [],
"scenarios": [],
"sdg_alignment": [],
"narrative": "",
"compliance_score": {},
"confidence_report": {},
"sources": []
}
Limits
Do not:
- guarantee donor approval,
- replace legal/financial review,
- fabricate data, baselines, citations, or partner commitments.
If data is weak, explicitly flag uncertainty and define verification steps.
Author
Vassiliy Lakhonin
1---2name: nonprofit-impact-orchestra3description: Generate donor-ready nonprofit project packages for grants, concept notes, logframes, MEAL plans, budgets, safeguarding reviews, and funder adaptation. Use when designing a new project, adapting to a donor call, building RBM logic, or preparing a proposal for submission. Also covers GESI, SDG alignment, risks, compliance scoring, and JSON-ready outputs.4metadata:5 source: https://skillmd.com/skills/claw-works/nonprofit-impact-orchestra6---78# Nonprofit Impact Orchestra910Turn rough nonprofit ideas, donor calls, or draft proposals into donor-ready packages.1112## Important Usage Note1314`orchestra ...` examples below are **invocation patterns**, not a required local binary.15Use them as mode labels when handling user requests in chat.1617## Invocation Patterns1819- `orchestra [project description]`20- `orchestra --express [description]`21- `orchestra --concept [description]`22- `orchestra --loi [description]`23- `orchestra --cfp [paste donor call text]`24- `orchestra --review [paste proposal text]`25- `orchestra --peer-review [paste proposal text]`26- `orchestra --donor-fit [description]`27- `orchestra --json [description]`2829## Core Rules30311. Be donor-ready; never fake certainty.322. Preserve realism over grandiosity.333. Flag weak or unverifiable claims explicitly.344. Ask only minimum blocking questions.355. Prefer structured outputs over long prose.366. Build for implementation, not just approval.377. Never fabricate baselines, evidence, partner commitments, or donor fit.388. Never output citations without retrievable source metadata (title/organization, URL or document origin, and date).3940## Evidence & Source Policy (Mandatory)4142### Confidence Labels43- `[HIGH]` — verified with retrievable source44- `[MEDIUM]` — plausible but incomplete evidence45- `[UNVERIFIED]` — claim needs manual verification4647### Source Requirements48For each source in an Evidence Note, include:49- source title or organization,50- URL (or explicit non-URL origin provided by user),51- publication/access date,52- confidence label.5354### Source-Limited Mode (Fallback)55If reliable retrieval is unavailable (no web/tool access and no user-provided sources):561. Do **not** invent sources or links.572. Replace Evidence Note with `Evidence Needed`.583. Mark unsupported claims as `[UNVERIFIED]`.594. Add `owner + due date` for each verification item.6061## Decision-Grade Additions (standard/deep mode)62631. Add Evidence Note with 3–8 sources **only when source requirements are met**.642. For any budget line >10% of total, provide unit-cost assumptions (quantity × unit rate) + rationale.653. Add Compliance Gates: `Go / Conditional Go / No-Go` before submission.664. Separate verified baselines from placeholders.675. Add a 2-week validation sprint (data checks, partner confirmations, budget checks, stop/go trigger).6869## Workflow70711. **Parse and scope**: location, target group, problem, impact, budget, duration, partners, donor, output type.722. **Strategic context**: drivers, stakeholders, risks, assumptions, donor-fit extraction from CFP (if provided).733. **Program logic**: RBM chain, ToC, logframe, SMART indicators, assumptions, baselines/targets.744. **MEAL + GESI + SDG**: accountability loop, inclusion analysis, SDG mapping.755. **Safeguarding/Do No Harm**: PSEA, conflict sensitivity, privacy, consent, environmental screening.766. **Budget logic**: personnel/travel/equipment/training/ops/contingency/co-financing + red-flag checks.777. **Draft/adapt**: donor-aligned framing, structure, language.788. **Readiness check**: risk matrix, scenarios, compliance score, confidence report, verification plan.7980## Default Delivery Package818200. Elevator Pitch 8301. Executive Summary 8402. Concept Note (if requested) 8503. Strategic Context 8604. Stakeholder Mapping 8705. GESI Analysis 8806. Safeguarding / Do No Harm Checklist 8907. RBM Chain 9008. Theory of Change 9109. Logframe Matrix 9210. MEAL Plan 9311. SDG Alignment 9412. Budget Table 9513. Co-financing Summary 9614. Sustainability / Exit Strategy 9715. Partnership Structure 9816. Donor Adaptation Notes 9917. Risk Matrix and Scenarios 10018. Human Impact Narrative 10119. Compliance Score 10220. Confidence Report 10321. Sources / Traceability (or `Evidence Needed` in source-limited mode) 10422. JSON Export Block105106## Compliance Score Format107108```text109Compliance Score: XX/100110✅ GESI indicators present111✅ SDG alignment mapped112⚠️ Sustainability needs strengthening113❌ Partner MoU missing114```115116## JSON Output Skeleton117118```json119{120 "project": {},121 "executive_summary": "",122 "concept_note": "",123 "strategic_context": {},124 "stakeholders": [],125 "rbm_chain": {},126 "theory_of_change": {},127 "logframe": [],128 "meal_plan": [],129 "gesi_analysis": {},130 "safeguarding": {},131 "budget": {},132 "co_financing": {},133 "sustainability": {},134 "partnerships": {},135 "donor_adaptation": {},136 "risks": [],137 "scenarios": [],138 "sdg_alignment": [],139 "narrative": "",140 "compliance_score": {},141 "confidence_report": {},142 "sources": []143}144```145146## Limits147148Do not:149- guarantee donor approval,150- replace legal/financial review,151- fabricate data, baselines, citations, or partner commitments.152153If data is weak, explicitly flag uncertainty and define verification steps.154155## Author156157Vassiliy Lakhonin