agentleFS
Sign inStart free
iblaiiblai/higher-education-agents/skills/blackbaud-raisers-edge/SKILL.md

blackbaud-raisers-edge

Skill14 starsChanged 5 months agoMITView on GitHub

Blackbaud Raiser's Edge NXT — lets an agent query alumni constituent records, giving history, pledge tracking, and wealth screening scores for advancement workflows.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do-not-contact and do-not-solicit flags must be checked on every constituent before any outreach action is taken.

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Blackbaud Raiser's Edge NXT

What it is

Blackbaud Raiser's Edge NXT is the most widely used fundraising CRM in higher education advancement offices. It stores constituent profiles, lifetime giving history, pledge schedules, event attendance, volunteer records, and wealth screening data. The alumni agent relies on it to personalize donor outreach, track engagement, and support gift officer workflows.

When to use this skill

  • Retrieving an alumnus's giving history, pledge status, and engagement score
  • Checking do-not-contact flags and preferred communication channels before outreach
  • Logging an interaction record after an alumni outreach touchpoint
  • Pulling wealth screening scores to inform solicitation strategy (for gift officers only)
  • Surfacing event attendance history to personalize reunion or campaign messaging

Credentials

This skill authenticates using env vars declared in the frontmatter metadata field. Set these in ~/.openclaw/.env (template: .env.example):

  • RAISERS_EDGE_BASE_URL - Raiser's Edge NXT API base URL (e.g. https://api.sky.blackbaud.com)
  • RAISERS_EDGE_API_KEY - Blackbaud SKY API subscription key from developer portal
  • RAISERS_EDGE_CLIENT_ID - OAuth 2.0 client ID from Blackbaud developer app registration
  • RAISERS_EDGE_CLIENT_SECRET - OAuth 2.0 client secret
  • RAISERS_EDGE_REDIRECT_URI - OAuth redirect URI for authorization code flow

Key operations

  • GET /constituent/v1/constituents/:id — full constituent profile with bio and contact data
  • GET /gift/v1/gifts?constituent_id= — giving history with amounts, dates, and designations
  • GET /constituent/v1/constituents/:id/ratings — wealth screening scores and capacity ratings
  • POST /constituent/v1/interactions — log an interaction record (call, email, visit)
  • GET /event/v1/eventattendees?constituent_id= — event attendance history

Notes

  • Raiser's Edge NXT uses Blackbaud's SKY API platform; access requires both a subscription key (header Bb-Api-Subscription-Key) and an OAuth 2.0 bearer token.
  • Wealth screening data is highly sensitive; restrict access to authenticated gift officer profiles only — never surface capacity ratings to the constituent directly.
  • Do-not-contact and do-not-solicit flags must be checked on every constituent before any outreach action is taken.
  • API rate limit: 300 requests per minute per subscription key across all endpoints.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free