Purpose
On October 26, 2026 Anthropic released the Claude for Nonprofits plugin: skills and connectors built with
about 30 nonprofits (the Design Partner Circle). It installs automatically, at no extra cost, for nonprofits
on Team and Enterprise plans. This skill turns the announcement into a working order of operations.
Program facts are in references/program-facts.md; the workflow catalog is in
references/plugin-workflows.md.
When to use
- A nonprofit has just enabled Claude (or the plugin arrived automatically) and staff ask where to start.
- An admin must decide which connectors to allow and how to communicate data handling and AI policy.
- A development/fundraising team wants help finding funders, judging an RFP, or drafting a proposal or report.
- Operations staff need help with marketing, hiring, onboarding, or board work.
Instructions
- Admin first: access and data. Admins control which users have access and which connectors are
available. Anthropic does not train models on customer data by default; security and compliance
documents are in the Anthropic Trust Center. If the organization has no AI use policy yet, use the
Claude Academy tutorial on data handling and drafting an AI use policy.
- Map your organization (start here). The post's recommended first step: ask Claude to map where the
organization keeps its information - donor data, grant files, finances, policies. With memory on, the
map is saved per person and the other skills reuse it. Use
templates/organization-map.md to capture the result.
- Check uses against your AI policy. Staff can ask whether a given use is allowed; Claude answers from
the organization's own policy rather than a generic rule.
- Pick the workflow by focus area (details in
references/plugin-workflows.md):
- Extend your team - marketing, hiring and people, board and leadership.
- Set up Claude responsibly - organization map, AI policy check.
- Fund your mission - find funders and grants, decide what to pursue, write proposals and reports,
keep relationships warm.
- For an RFP, decide before you write. Forward the RFP and ask for an eligibility and
competitiveness breakdown; only then turn it into a requirements list and first draft. Keep the cited
sources and cited report figures Claude provides, and verify them before submission. A worksheet is in
templates/rfp-go-no-go.md.
- Build skills in people, not just tools. Point staff to the webinars and Claude Academy's nonprofit
collection; consider Claude Corps fellows or pro bono consultants (planned Taproot Foundation
partnership) and the named adoption partners in the program facts.
- Send feedback through the form Anthropic linked from the post to shape future releases.
Examples
Example 1 - day one for a small team
"Map where we keep donor records, grant files, finances, and policies." Claude produces the map; with
memory on, it is saved and later used by the proposal and donor-update skills.
Example 2 - policy question
A staff member asks: "Can I paste a donor's giving history into Claude to draft a thank-you note?" Claude
answers based on the organization's AI use policy and connector settings, not a generic rule.
Example 3 - RFP triage
The grants lead forwards a foundation RFP. Claude returns an eligibility and competitiveness breakdown; the
team decides to pursue, and Claude converts the RFP into a requirements list and a first draft with cited
figures from past reports.
Example 4 - stewardship cycle
Before a major-donor call: a pre-call brief. After: a write-up and thank-you note, then a donor update in
the organization's voice and a stewardship plan.
1---2name: nonprofit-ai-adoption3description: Set up and use Claude at a nonprofit following the Claude for Nonprofits plugin announced October 26, 2026 - map where the organization keeps its information, check uses against the organization's AI policy, then apply the plugin's three focus areas (extend your team, set up Claude responsibly, fund your mission) to marketing, hiring, board work, funder research, go/no-go decisions on RFPs, proposals, reports, and donor stewardship. Use when a nonprofit admin or staff member is starting with Claude on a Team or Enterprise nonprofit plan, or wants to know which plugin workflow fits a fundraising or operations task.4metadata:5 source: https://skillmd.com/skills/uygnoey/nonprofit-ai-adoption6---78## Purpose9On October 26, 2026 Anthropic released the Claude for Nonprofits plugin: skills and connectors built with10about 30 nonprofits (the Design Partner Circle). It installs automatically, at no extra cost, for nonprofits11on Team and Enterprise plans. This skill turns the announcement into a working order of operations.12Program facts are in [references/program-facts.md](references/program-facts.md); the workflow catalog is in13[references/plugin-workflows.md](references/plugin-workflows.md).1415## When to use16- A nonprofit has just enabled Claude (or the plugin arrived automatically) and staff ask where to start.17- An admin must decide which connectors to allow and how to communicate data handling and AI policy.18- A development/fundraising team wants help finding funders, judging an RFP, or drafting a proposal or report.19- Operations staff need help with marketing, hiring, onboarding, or board work.2021## Instructions221. **Admin first: access and data.** Admins control which users have access and which connectors are23 available. Anthropic does not train models on customer data by default; security and compliance24 documents are in the Anthropic Trust Center. If the organization has no AI use policy yet, use the25 Claude Academy tutorial on data handling and drafting an AI use policy.262. **Map your organization (start here).** The post's recommended first step: ask Claude to map where the27 organization keeps its information - donor data, grant files, finances, policies. With memory on, the28 map is saved per person and the other skills reuse it. Use29 [templates/organization-map.md](templates/organization-map.md) to capture the result.303. **Check uses against your AI policy.** Staff can ask whether a given use is allowed; Claude answers from31 the organization's own policy rather than a generic rule.324. **Pick the workflow by focus area** (details in33 [references/plugin-workflows.md](references/plugin-workflows.md)):34 - *Extend your team* - marketing, hiring and people, board and leadership.35 - *Set up Claude responsibly* - organization map, AI policy check.36 - *Fund your mission* - find funders and grants, decide what to pursue, write proposals and reports,37 keep relationships warm.385. **For an RFP, decide before you write.** Forward the RFP and ask for an eligibility and39 competitiveness breakdown; only then turn it into a requirements list and first draft. Keep the cited40 sources and cited report figures Claude provides, and verify them before submission. A worksheet is in41 [templates/rfp-go-no-go.md](templates/rfp-go-no-go.md).426. **Build skills in people, not just tools.** Point staff to the webinars and Claude Academy's nonprofit43 collection; consider Claude Corps fellows or pro bono consultants (planned Taproot Foundation44 partnership) and the named adoption partners in the program facts.457. **Send feedback** through the form Anthropic linked from the post to shape future releases.4647## Examples48**Example 1 - day one for a small team**49"Map where we keep donor records, grant files, finances, and policies." Claude produces the map; with50memory on, it is saved and later used by the proposal and donor-update skills.5152**Example 2 - policy question**53A staff member asks: "Can I paste a donor's giving history into Claude to draft a thank-you note?" Claude54answers based on the organization's AI use policy and connector settings, not a generic rule.5556**Example 3 - RFP triage**57The grants lead forwards a foundation RFP. Claude returns an eligibility and competitiveness breakdown; the58team decides to pursue, and Claude converts the RFP into a requirements list and a first draft with cited59figures from past reports.6061**Example 4 - stewardship cycle**62Before a major-donor call: a pre-call brief. After: a write-up and thank-you note, then a donor update in63the organization's voice and a stewardship plan.