forcedotcom/sf-skills / skills/nonprofit-volunteer-management-structure-generate
nonprofit-volunteer-management-structure-generate
VerifiedUse this skill to plan a Salesforce Nonprofit Cloud Volunteer Management (VM) program before anything is created: it interviews the user about their programs, sites, volunteer roles, requirements, and shift schedules, checks the org read-only for records to reuse, and presents a plan of the records the program needs. It never writes; on the user's yes it hands the plan to nonprofit-volunteer-management-records-create. TRIGGER when a user wants to plan, design, or structure a VM program, or asks "what records do we need" or "how should we model this program". DO NOT TRIGGER to explain what a VM object or field is for (use nonprofit-volunteer-management-model-get), to write records (use nonprofit-volunteer-management-records-create), to enable Volunteer Management in an org, for per-person records (JobPositionAssignment, PersonLocationAvailability, PersonCompetency / PersonExamination, ConstituentRole), or for NPSP / Volunteers for Salesforce (V4S), which is unsupported.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.7 KB |
| references/configuration-decisions.md | markdown | 8.3 KB |
| references/discovery-interview.md | markdown | 5.0 KB |
| references/edge-cases.md | markdown | 2.6 KB |
| references/mcp-invocation.md | markdown | 4.8 KB |
| references/plan-output.md | markdown | 9.0 KB |
references/edge-cases.md
View on GitHub# Edge Cases
**When to load:** any step, when a situation doesn't fit the standard flow.
**Purpose:** hybrid programs, existing records, contradictions, several programs, and an unsure user.
---
## Hybrid programs ("sometimes shifts, sometimes flexible")
Plan both under the same Volunteer Initiative: Job Positions with shifts for the scheduled work, Job Positions without shifts for the flexible work. Don't force the program into one model. Adding shifts to a Job Position later is easy.
---
## Existing records in the org
Assume the org may already hold relevant records, and check every session (Workflow step 5).
- Show what you find and ask before planning anything new: "You already have a Location called 'Eastside Pantry' and a Competency called 'Food Safety'. Should I use these, or plan new ones?"
- Locations, Competencies, Examinations and Positions are meant to be shared. A "Food Safety" Competency planned for one program should be reused for the next.
- If the user wants shifts for a Job Position that already exists, plan the schedule they want. records-create checks which of those shifts already exist and creates only the missing ones.
- If an existing record looks incomplete or misconfigured, say what's missing. This skill doesn't change it.
---
## User contradicts themselves
Example: "No qualifications needed", then later "oh, drivers need a license". Or: "no shifts", then "we need 5 volunteers every Saturday at 9", which is a shift.
Raise it gently and let the user choose: "Earlier you said X, but now it sounds like Y. Which is right?" Don't pick the later answer silently, and don't run the reuse checks for the affected records until it's settled.
---
## Several programs
Get the full list first, then plan one program at a time.
- Reuse a Location when the same site serves several programs, and reuse Competencies across programs.
- Each program gets its own Volunteer Initiative and Job Positions, and possibly its own Position templates.
- For later programs, offer the earlier decisions: "You put qualifications on the Position for the first program. Same approach here?" Configure each program for its own needs.
---
## User is unsure about a parent Volunteer Initiative
Recommend no parent: "When in doubt, start without one. You can add a parent later without changing anything already set up."
If the user describes four or more related programs with shared reporting but still hesitates, ask one question: "Would it help to see combined numbers across all of them, or do you manage each one separately?" If they're still unsure, plan no parent.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |