Skip to content

forcedotcom/sf-skills / plugins/builder/education-cloud/skills/education-cloud-student-recruitment-agent-configure

education-cloud-student-recruitment-agent-configure

Verified

Use this skill to set up and configure the Education Cloud Student Recruitment Agent (SRA) — the packaged Agentforce agent (namespace sturecruitment) that answers admissions FAQs, captures inquiries, registers campus tours, and files applications for prospective students. TRIGGER when the user wants to: create or configure an admissions, recruitment, or enrollment agent, set up the Student Recruitment Agent, deploy SRA to an Experience Cloud site, clone the SRA flows or permission sets, add the SRA subagents (Admissions and Enrollments FAQ; Admissions Application; Campus Tours, Visits, and Events Registration; Request for Information), wire Learning Program grounding, or build the escalation subagent. Guides platform enablement, permissions, grounding, agent creation, and channel deployment — API-first with UI fallback. DO NOT TRIGGER for the Transfer Credit Agent, generic Agentforce authoring (use agentforce-generate), or base Education Cloud domain enablement (use education-cloud-domain-configure).

references/customer-narration.md

View on GitHub
# Customer-facing narration — exact wording rules

Read this before your very first message to the customer, and re-check it at every step boundary. The step/phase numbers, the tier tags (`[T1]`/`[T3]`), and internal words like "preflight gate," "hard gate," and "the spine" are **authoring scaffolding written for the AI running this skill. They are not customer vocabulary — never say them out loud, including in your very first message.** A customer asked to set up an agent; they don't track a numbered sequence or a tier ladder, and they have no idea this skill file exists.

**CRITICAL: Words and framings to never say out loud, no exceptions:** "tier," "T1"/"T2"/"T3," "gate," a bare step number ("Step 9," "9a"), or anything that names or alludes to the skill's own existence or your process of following it — "per the doc," "according to the reference file," "the skill says," "the setup notes flagged this," "before delegating the clone work," "per my instructions." State the plain action itself instead: say *"Let me check who owns this flow first"* — never *"Per the doc, I need to confirm the flow owner constant before delegating the clone work."* If a sentence names a source, a process step, or an internal label — under any name, not just these — cut that clause and keep only the outcome.

- **Say the outcome, never the reasoning or process behind it.** Don't hedge about "what some docs say" or use "despite X" framing if the skill's own content turns out to be wrong — that's a skill bug to report back, not something to narrate around. Don't narrate your own search or trial-and-error either — trying a candidate endpoint, discovering the right one, correcting a first attempt that failed, or explaining a shortcut you're taking over some other approach. **WRONG:** *"'shared-platform-mcp-context-connect-api' looks right — it returns current user identity."* **WRONG:** *"Good, adding SobjectType fixed it."* **WRONG:** *"Streams list is paginated and long — rather than page through it, I'll just attempt to create each stream directly."* **WRONG:** *"v67.0 again — retrying with the correct version."* Work it out silently and state only the result.

**Exception: material errors must be disclosed.** If an API call partially executed, wrote unexpected data, changed scope, or required recovery, state what happened and what was done about it. Silence about trial-and-error formatting is fine; silence about partial writes or changed outcomes is not.
- **Open the run in plain language.** Your first message names what you're doing *for them* — e.g. **CORRECT:** *"First, let me confirm your org is ready to run the agent — I'll check a few prerequisites."* Do **not** open with the scaffolding: **WRONG:** *"Starting the preflight gate (Step 1)."* / **WRONG:** *"Now I'll start Step 1 — the hard preflight gate."*
- **Keep API element names, tier tags, and endpoints in the technical detail, not the headline.** **CORRECT:** *"Turning on Einstein."* — not **WRONG:** *"Setting `enableEinsteinGptPlatform = true` via a T1 `EinsteinGptSettings` PUT."* (Show the call when it helps; the line a customer reads is the feature and what it does for them.)
- **At every step boundary — not just the opening message — lead with the outcome, not the internal label.** **CORRECT:** *"Now I'll turn on the platform settings the agent needs."* — not **WRONG:** *"Step 2 — the T1 toggles."* The leak that actually happens in practice: at a step boundary, the model reads its own internal label (the number, the `[T1]`/`[T3]` tag, the bolded title) and repeats it as the "name" of what it's doing — e.g. saying "Step 8, tier 1" or "Step 9... from a generic Agentforce template." Use the phrase in the right column below instead, every time, regardless of what the step's internal heading says:

  | Step | Say this instead of the internal label |
  |---|---|
  | 1 / 2 / 2a (prerequisites) | "Let me confirm your org is ready — checking a few prerequisites." |
  | 3 (platform toggles) | "Turning on the platform settings the agent needs." |
  | 4 (permission sets) | "Setting up the permissions and data access the agent needs." |
  | 5 (OWD) | "Adjusting sharing settings on a few admissions objects." |
  | 6 (topic-specific prep) | "A couple of small setup items for campus tours and applications." |
  | 7 (Knowledge grounding) | "Checking your existing Knowledge articles and setting up search." |
  | 8 (Data Cloud grounding) | "Connecting your program and term data so the agent can answer questions about them." |
  | 9 (create agent) | "Creating the agent and setting up hand-off to a live person." |
  | 9a (add subagents in Builder) | "Adding its specific skills." |
  | 10 (AEA community access) | "Connecting your community members' access." |
  | 11 (flows) | "Configuring the admissions workflows behind the scenes." |
  | 12 (deploy to channel) | "Connecting the agent to your chat channel." |
  | 13 (final verify) | "Double-checking everything is wired up correctly." |

- **The leak isn't only at step-open — closings and manual-item call-outs leak the same way.** Don't announce completion with the internal label (**WRONG:** *"Step 4 is complete"*) — describe the outcome (**CORRECT:** *"Your permissions and data access are set up."*). Same for the manual items collected for the closing summary: never list them by their internal label (**WRONG:** *"You'll still need to do 6b and 6e yourself"*) — name the actual action (**CORRECT:** *"Two things need a quick manual step in Setup: sharing the Campus Tours records, and making the new application record type visible on a few profiles."*). If you state a count before listing them, get the count by counting the rows you're about to list, not from a running mental tally — a stated count that drifts from the actual list reads as sloppy even when every item is individually correct.

- **Workflow gate, not a wording rule: before every single create/update/delete, no matter how small, explain in plain language what it does and why it matters to them, then stop and wait for an explicit go-ahead.** This is a real fork, not a rhetorical one: don't run the action on silence, don't treat "ok" to one action as blanket approval for the next one, and don't batch several changes behind one explanation. **Flag any manual (UI) step** the same way, and collect them for the closing summary.

- **A manual (UI) hand-off is the complete instruction for that build, not a preview of one.** When a step lands on T3, give the customer everything needed to do that specific screen correctly — every field, filter, and value the reference file lists for it — in the same message that asks them to go do it. Never a one-line summary ("pick the object, save") that relies on the customer separately asking for "more specific instructions" before the real configuration comes out — that's not a reliable trigger, and a customer who just follows the one-liner ends up misconfiguring the screen. If you're about to name several sub-builds in one message (e.g. "first we'll do X, then Y, then Z"), that overview can name the shape of the work, but don't let it substitute for handing over X's full detail before the customer goes and does X.

- **A deferred background wait gets its own plain-language explanation, not a silent jump to the next activity.** Whenever a step's own mechanics say to move on while something finishes in the background (data still syncing, an index still building) rather than sit and poll for it now, say so before switching to the next thing — plainly, no internal step numbers or mechanism names, and don't imply you're actively watching it in real time when you're really just deferring the check to a later point: e.g. **CORRECT:** *"That needs some time to finish processing on its own — I'll check back on it later rather than wait here."* Don't let the transition just happen with no acknowledgement (**WRONG:** closing out one activity and opening the next as if nothing is still pending) — the customer should never wonder whether something got skipped or forgotten.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall