@gonzih/skills-nonprofit 1.0.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 gonzih
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,49 @@
+# skills-nonprofit
+
+Claude Code skill suite for nonprofit leaders, grant writers, and development directors.
+
+## Install
+
+```bash
+npx @gonzih/skills-nonprofit
+```
+
+Or install globally:
+
+```bash
+npm install -g @gonzih/skills-nonprofit
+```
+
+Then restart Claude Code.
+
+## Skills
+
+### `/grant-proposal`
+Write a complete grant proposal: need statement, program description, goals & objectives, evaluation plan, and budget narrative.
+
+**Invoke:** `/grant-proposal [funder name or program area]`
+
+---
+
+### `/donor-report`
+Write an impact report for donors: programs funded, outcomes achieved, stories of impact, financials snapshot, and next ask.
+
+**Invoke:** `/donor-report [donor name or segment]`
+
+---
+
+### `/impact-story`
+Transform raw program data into a compelling beneficiary impact story for newsletters, social media, or fundraising appeals.
+
+**Invoke:** `/impact-story [channel: newsletter | social | appeal | annual report]`
+
+---
+
+### `/volunteer-brief`
+Write a volunteer role description and orientation brief: role purpose, responsibilities, time commitment, and training overview.
+
+**Invoke:** `/volunteer-brief [role name or program area]`
+
+## License
+
+MIT

package/install.js

@@ -0,0 +1,15 @@
+#!/usr/bin/env node
+import { copyFileSync, mkdirSync, existsSync } from 'fs';
+import { join } from 'path';
+import { homedir } from 'os';
+
+const skillsDir = join(homedir(), '.claude', 'skills');
+const skills = ['grant-proposal', 'donor-report', 'impact-story', 'volunteer-brief'];
+
+for (const skill of skills) {
+  const dest = join(skillsDir, skill);
+  if (!existsSync(dest)) mkdirSync(dest, { recursive: true });
+  copyFileSync(new URL(`./skills/${skill}/SKILL.md`, import.meta.url).pathname, join(dest, 'SKILL.md'));
+  console.log(`✓ Installed /${skill}`);
+}
+console.log('\nSkills installed! Restart Claude Code to use them.');

package/package.json

@@ -0,0 +1,29 @@
+{
+  "name": "@gonzih/skills-nonprofit",
+  "version": "1.0.0",
+  "type": "module",
+  "description": "Claude Code skill suite for nonprofit leaders, grant writers, and development directors",
+  "main": "install.js",
+  "bin": {
+    "skills-nonprofit": "install.js"
+  },
+  "scripts": {
+    "postinstall": "node install.js"
+  },
+  "keywords": [
+    "claude",
+    "claude-code",
+    "skills",
+    "nonprofit",
+    "grant-writing",
+    "fundraising",
+    "impact"
+  ],
+  "author": "gonzih",
+  "license": "MIT",
+  "files": [
+    "skills/",
+    "install.js",
+    "README.md"
+  ]
+}

package/skills/donor-report/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: donor-report
+description: Write an impact report for donors covering programs funded, outcomes achieved, stories of impact, a financials snapshot, and a next ask.
+triggers: ["write a donor report", "draft an impact report", "donor impact report for"]
+---
+
+# Donor Report
+
+## What this skill does
+Produces a compelling donor impact report that thanks the donor, shows measurable outcomes from their gift, shares a human story, provides a transparent financials snapshot, and closes with a clear and specific next ask. Suitable for individual major donors, foundations, and corporate partners.
+
+## How to invoke
+/donor-report [donor name or segment]
+
+## Workflow steps
+
+### Step 1 — Gather context
+Ask the user for: donor name and relationship to the organization, gift amount and purpose, reporting period, 3–5 key program outcomes and statistics, one or two beneficiary stories (anonymized as needed), and the desired next ask (renewal, upgrade, or new initiative).
+
+### Step 2 — Write the opening and gratitude section
+Open with a warm, specific thank-you that ties the donor's gift to real impact. Avoid generic language; reference the donor's specific interest or prior engagement.
+
+### Step 3 — Report on programs and outcomes
+Present funded programs in a readable format: brief program description, activities completed during the period, and quantitative outcomes (people served, services delivered, milestones reached). Use the donor's language and priorities where known.
+
+### Step 4 — Share a story of impact
+Write a 150–250 word beneficiary story (or program vignette) that brings the numbers to life. Protect confidentiality per the user's guidance.
+
+### Step 5 — Provide a financials snapshot and next ask
+Summarize how the gift was used (brief budget summary or pie-chart callout language). Close with a specific, confident next ask tied to an upcoming opportunity or organizational need.
+
+## Example outputs
+A 2–3 page donor report in letter or memo format, with labeled sections, outcome callout boxes, a story sidebar, and a closing paragraph with a clear call to action.

package/skills/grant-proposal/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: grant-proposal
+description: Write a complete grant proposal including need statement, program description, goals & objectives, evaluation plan, and budget narrative.
+triggers: ["write a grant proposal", "draft a grant application", "grant proposal for"]
+---
+
+# Grant Proposal
+
+## What this skill does
+Guides you through writing a complete, fundable grant proposal section by section. It collects key details about your organization, the funding opportunity, and the proposed program, then produces a polished proposal with a compelling need statement, clear program description, measurable objectives, an evaluation plan, and a justified budget narrative.
+
+## How to invoke
+/grant-proposal [funder name or program area]
+
+## Workflow steps
+
+### Step 1 — Gather context
+Ask the user for: organization name and mission, funder name and focus area, requested amount, program or project name, target population, geographic service area, and any known funder priorities or restrictions.
+
+### Step 2 — Draft the need statement
+Write a 2–4 paragraph statement of need that uses data and local context to establish the problem, demonstrates the gap in current services, and connects directly to the funder's priorities.
+
+### Step 3 — Write program description and goals
+Describe the proposed program: activities, timeline, staffing, and partnerships. State 2–4 SMART goals and 4–8 measurable objectives tied to outcomes the funder cares about.
+
+### Step 4 — Build the evaluation plan
+Outline how success will be measured: data collection methods, frequency, who is responsible, and how findings will be used for learning and reporting.
+
+### Step 5 — Write the budget narrative
+Justify each major line item (personnel, fringe, supplies, contractual, indirect) with clear rationale. Note any cost-share or matching funds. Flag items that may require funder pre-approval.
+
+## Example outputs
+A 4–6 page narrative proposal ready for final review, with clearly labeled sections, data citations placeholders, and a prose budget narrative that mirrors the line-item budget.

package/skills/impact-story/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: impact-story
+description: Transform raw program data and case notes into a compelling beneficiary impact story for newsletters, social media, or fundraising appeals.
+triggers: ["write an impact story", "turn this case data into a story", "beneficiary story for"]
+---
+
+# Impact Story
+
+## What this skill does
+Takes raw program data, case notes, survey responses, or staff observations and transforms them into a narrative-driven impact story suitable for a newsletter, social post, annual report, or direct-mail appeal. The output centers the beneficiary's experience, respects dignity and confidentiality, and connects individual change to organizational mission.
+
+## How to invoke
+/impact-story [channel: newsletter | social | appeal | annual report]
+
+## Workflow steps
+
+### Step 1 — Gather raw material
+Ask the user for: the beneficiary's situation before engaging the program (anonymized or composite), what services or supports they received, what changed in their life as a result, any direct quotes or paraphrased sentiments, confidentiality requirements (use first name only, composite character, or full name with permission), and the intended channel and word count.
+
+### Step 2 — Identify the narrative arc
+Map the classic before–struggle–intervention–transformation–hope arc onto the details provided. Identify the single most powerful moment of change to anchor the story.
+
+### Step 3 — Draft the story
+Write the story in third person (or first person if a direct quote anchors it). Lead with a scene-setting hook. Keep sentences short and concrete. Weave in one or two program outcome statistics to validate the anecdote. Close with a forward-looking statement that ties to the organization's mission.
+
+### Step 4 — Adapt for channel
+Adjust length, tone, and structure for the target channel: 600–800 words for newsletter/annual report, 150–200 words for a social caption, 300–500 words for an appeal letter insert. Add a suggested pull quote for print layouts.
+
+## Example outputs
+A polished 400–700 word impact story with a hook opening, narrative arc, embedded statistic, and mission-connected close — plus a 1–2 sentence social caption variant.

package/skills/volunteer-brief/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: volunteer-brief
+description: Write a volunteer role description and orientation brief covering role purpose, responsibilities, time commitment, and training overview.
+triggers: ["write a volunteer role description", "create a volunteer brief", "volunteer job description for"]
+---
+
+# Volunteer Brief
+
+## What this skill does
+Produces a complete volunteer role package: a public-facing role description for recruitment and a concise orientation brief for onboarding. Together they set clear expectations, attract well-matched volunteers, and reduce early attrition by ensuring volunteers know exactly what they are signing up for.
+
+## How to invoke
+/volunteer-brief [role name or program area]
+
+## Workflow steps
+
+### Step 1 — Gather role details
+Ask the user for: role title, program or department, primary purpose of the role, key responsibilities (3–6 bullets), required skills or experience, physical or schedule requirements, time commitment (hours per week/month, duration, flexibility), reporting relationship, training provided, benefits to the volunteer (skills gained, community connection, etc.), and any screening requirements (background check, references).
+
+### Step 2 — Write the role description
+Draft a 1-page public-facing role description with: a compelling role summary (2–3 sentences), a responsibilities list, qualifications and ideal skills, time commitment details, and a brief "why volunteer with us" closing. Use inclusive, action-oriented language that appeals to prospective volunteers.
+
+### Step 3 — Write the orientation brief
+Produce a 1–2 page internal orientation brief with: welcome and mission context, role purpose in the program's broader work, step-by-step onboarding checklist (paperwork, training, first-day logistics), key contacts and communication norms, policies relevant to the role (confidentiality, safety, reporting), and a 30-day milestone expectation.
+
+### Step 4 — Review and finalize
+Suggest any clarifying questions the organization should answer before publishing (e.g., stipend, parking, accessibility accommodations) and flag any legal or safety considerations based on the role type.
+
+## Example outputs
+A 1-page public role description formatted for a website or flyer, plus a 1–2 page internal orientation brief with onboarding checklist — both ready for staff review before distribution.