nonprofit-volunteer-management-records-create

Installation
SKILL.md

Nonprofit Cloud Volunteer Management — Record Creation

This skill writes Volunteer Management records to an org: a Volunteer Initiative and the Locations, Positions, Job Positions, qualifications and Job Position Shifts under it. It checks the org for records it can reuse, fills each field from references/field-guide.md, shows the user one records table per object, and writes that object only after the user confirms its table. Open every run by telling the user that this skill reads and writes their org, and that nothing is read or written without their yes.

Hard rules

  • Never delete records. No delete, rollback or cleanup of any kind. If a write fails part-way, report what was created and what wasn't; never undo it.
  • Never act on NPSP or Volunteers for Salesforce (V4S). That legacy package is unsupported here. Say so and stop.
  • No acronyms or internal labels in what the user sees. Write out Volunteer Initiative, Job Position, Job Position Shift, Job Position Assignment, Position Qualification, Job Position Qualification, Data Processing Engine, and "out of the box". Never show internal step or section labels.
  • Writes need a yes per object. Nothing is written until the user confirms that object's records table.

Mechanism

Org calls go through the connection the session has: the headless-360 tools (dispatch_readonly for reads, dispatch for writes) or an authenticated Salesforce CLI. Both return the same results at API v67.0. Tell the user which one is in use. If neither is connected, stop and ask the user to connect one; never guess an org result. The exact call for each step, in both forms, is in references/mcp-invocation.md.

Scope

  • In scope: Volunteer Initiative (including child initiatives), Location and its Address, Competency, Examination, Position, Position Qualification, Job Position, Job Position Qualification, Job Position Shift; Operating Hours and Time Slots only when the user asks for them. Reusing existing records, filling fields, detecting required custom fields, writing in dependency order, and recovering from write errors.
  • Out of scope: deciding what to build (nonprofit-volunteer-management-structure-generate); explaining what an object or field means (nonprofit-volunteer-management-model-get); turning Volunteer Management on; any per-person record — volunteer sign-ups and assignments, a volunteer's availability, a person's qualifications, marking a person as a volunteer, the person or household itself. The full list is in references/field-guide.md "Out of scope".
Installs
1
GitHub Stars
1.1K
First Seen
1 day ago