forcedotcom/sf-skills / plugins/builder/education-cloud/skills/education-cloud-student-recruitment-agent-configure
education-cloud-student-recruitment-agent-configure
VerifiedUse 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).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 21.4 KB |
| references/agent-and-subagents.md | markdown | 34.0 KB |
| references/customer-narration.md | markdown | 7.9 KB |
| references/execution-model.md | markdown | 11.1 KB |
| references/flows.md | markdown | 13.2 KB |
| references/grounding.md | markdown | 39.5 KB |
| references/permissions.md | markdown | 32.1 KB |
| references/platform-enablement.md | markdown | 13.2 KB |
| references/prerequisites.md | markdown | 24.1 KB |
| references/routing.md | markdown | 23.7 KB |
references/execution-model.md
View on GitHub# Execution model — the three-tier fallback ladder
Read this whenever a step's tier or a route/allowlist question is unclear. SKILL.md "How this skill runs" is the summary; this file is the full detail. Every org-changing step follows the **same ladder, in order**: try tier 1; on failure or when the type has no tier-1 path, drop to tier 2; if that runtime isn't available, tier 3. Always finish with a verify.
> **CRITICAL: The ladder resets at every step — a lower tier never becomes the new default.** Landing on tier 2 or tier 3 for one step (because that type has no tier-1 path, or a route failed) says nothing about the next step. Re-attempt tier 1 first on the very next org-changing action even if the previous one dropped to `sf` or the UI — don't keep reaching for `sf`/UI on later steps just because the last one needed it. A whole run landing mostly on tier 2/3 is a coincidence of which types were involved, never evidence tier 1 stopped being worth trying.
## API version policy — always use the org's current version, full stop
**Every call in this skill uses the org's current API version — the highest the org supports — never a lower, hardcoded number.** `vXX` in these reference files is a placeholder for that current version, substituted fresh at call time; any concrete `vNN.0` you see elsewhere in these files is illustrative of a past example, never a value to actually send. The resolution itself happens once, at **Step 0** (`SKILL.md`), before anything else in the run — this section is the rationale for that action, not a second place to run it.
**Why it matters, beyond avoiding an error:** a stale/lower version doesn't just fail loudly — it can silently omit a real entity or feature from a schema-catalog read (absent from `EntityDefinition`, `INVALID_TYPE`, etc.), which reads as "doesn't exist in this org" when it's actually just not exposed below that version. Treat any such absence as a version question first, before concluding the org lacks the thing. There is no upper ceiling to work around.
Three surfaces have a documented **minimum** — a floor that a current-version call usually already clears, kept here to explain a failure on a very old/downgraded org, or on a surface where the resolved current version is genuinely below the floor:
| Surface | Minimum | Why |
|---|---|---|
| Next-Gen Authoring `/services/data/vXX/nextgen-authoring/*` (no `/connect/` segment) | v67.0+ | The NGA bundle surface lands at v67.0. |
| Flow verify `/query` (`FlowDefinitionView`) | v62.0+ | Minimum for the `IsActive`/`ApiName` projection. |
| Data Cloud Simple Start `/services/data/vXX/ssot/simple-start/*` (`sobject-recommendations`, `auto-map-dlos`) | v67.0+ | 404s (`NOT_FOUND`) below this version. |
> **WARNING: Never send `v67.0` or `v62.0` literally just because they appear in this table.** They're floors, not a version to default to. Resolve the org's current version first and use it — **unless the resolved current version is below the floor for the specific surface you're calling**, in which case use that surface's floor, not the resolved current version and not a value in between. Don't discover a floor by trial-and-error (retrying versions until one works) when it's already listed here.
> **WARNING: Two different failure signatures on `/ssot/simple-start/*` mean two different things — don't conflate them.** A gateway-level `ROUTE_NOT_FOUND` means the **wrong dispatcher** (a write sent on `dispatch_readonly` instead of `dispatch`) — never a version issue; resend on the write `dispatch`. An endpoint-level `404`/`NOT_FOUND` in the response body (dispatcher was already correct) means the call landed **below this surface's v67.0+ floor** — use the floor per the table above, not a retry at some other guessed version.
## Tier 1 — Headless MCP dispatch
The *only* tier a hosted-MCP customer without a shell can use. Reads: `dispatch_readonly`. Writes: the write-enabled `dispatch`. Both are synchronous REST — never a raw token/`curl`.
- **Component & settings metadata CRUD → `POST/PUT/GET /services/data/vXX/headless/metadata`**, a **per-type-allowlisted** surface. The **verb determines the operation** (POST=create, PUT=update, GET=read). A type not on the allowlist returns **`400 UNSUPPORTED_OPERATION`** — that is the signal to drop to tier 2, not an error to retry.
- **On the `/headless/metadata` allowlist:** `PermissionSet`, `PermissionSetGroup`, `Profile` (CRUD); `IndustriesSettings`, `OmniChannelSettings`, `CustomPreferencePageSettings` (R,U — settings files; `OmniChannelSettings` PUT flips `<enableOmniChannel>`, fullName `OmniChannel`); `Group`, `Role`, `RestrictionRule`, `CustomPermission`, `SharingSet`, `ApiNamedQuery`, `UserAccessPolicy`, `AccountSettings`; **`CustomObject` (the OWD `sharingModel`) and `StandardValueSet` (the Campaign `Type` picklist) — both tier-1 via `/headless/metadata`**. **`RecordType` is tier-1 via a different surface** — `POST /tooling/sobjects/RecordType` (nested `{FullName,Metadata}`), not `/headless/metadata`. **Not on this allowlist:** `Flow`, sharing rules (`SharingCriteriaRule`/`SharingOwnerRule` — CREATE unsupported through ANY MDAPI path). **WARNING:** Off the `/headless/metadata` allowlist ≠ no tier-1 path: **flow clone/author/activate has its own tier-1 surface** — the `/flowbuilder/*` Connect REST endpoints (see `flows.md`); only a `Flow` *MDAPI async deploy* has no tier-1 route. **Sharing-rule CREATE genuinely has no tier-1 path** → tier 3 UI.
- Attempt an allowlisted type at tier 1; on `ROUTE_NOT_FOUND` or `500 METADATA_CRUD_ERROR`, drop to tier 2. A `500 METADATA_CRUD_ERROR` can also mean a missing perm precondition — `FileBasedMetadataCrud` **and** `Headless360HostedMcpServer` must both be granted.
- **WARNING: `OWD (CustomObject sharingModel)` has one exception:** `ActionPlanTemplate` is tier-3-UI-only; the other 5 objects deploy at tier 1. See `permissions.md` Step 5 for the per-object rule.
- **Other synchronous REST also routes over dispatch** (not just metadata): sObject REST (incl. `/composite/sobjects`), Connect REST, Tooling REST (read AND write-by-Id, e.g. `POST /tooling/sobjects/RecordType`, `POST /tooling/sobjects/ApplicationRecordTypeConfig`). Use these for perm-set clone + *assignment*, record-type create, article publishing, grounding wiring.
- **The async Metadata API deploy (`/services/data/vXX/metadata/deployRequest` + SOAP) is NOT routed over dispatch** — it returns `ROUTE_NOT_FOUND` at the gateway. There is no headless async-deploy escape hatch — that is exactly why the genuinely-off-allowlist types (`Flow`, sharing rules) need tier 2/3.
- **SOQL `/query` AND `/tooling/query` route over `dispatch_readonly` (tier 1)** — including existence / aggregate (`GROUP BY`) / WHERE-filter reads with no known Id. **Route each read to the most specific tool that answers it — this is not a linear failover, and `/query` is not a last resort:**
1. **Schema questions** (does a RecordType/field/picklist exist, its values) → **`describe`** (`GET /sobjects/<Type>/describe`). The most reliable read surface and the direct answer for schema — first *when applicable*.
2. **A specific record whose Id you already hold** (create response, known DurableId) → **GET by Id** (`/sobjects/<Type>/<id>`). Direct confirm of the persisted record.
3. **Discovery / existence / WHERE-filter / aggregate reads with no known Id** → **`/query`** (tier 1 over `dispatch_readonly` — the normal, correct path for these), `sf data query` (tier 2) as fallback, UI last.
4. **On a `/query` outage** (see caveat below) that blocks a discovery read → **ask the user to supply the Id, then GET by Id.** Degraded mode only, never a preference over `/query`.
- **WARNING: `/query` can hit transient outage windows** where the whole query family (`/query`, `/tooling/query`, `/queryAll`) 404s across **all** API versions for a period, then self-recovers. This is transient, NOT version-gated (it clears across all API versions at once) and NOT a permanent regression — do not treat `/query` as unreliable, just **never make a verify hard-depend on a SOQL filter succeeding**; keep the GET-by-Id / ask-user fallback ready.
- **WARNING: Before concluding it's an outage, check the call shape — on `/query` OR `/tooling/query`, and whether the error reads as a `404` or a `400 ROUTE_NOT_FOUND`.** Both surfaces, both error shapes, trace to the same self-inflicted **query-string encoding** bug: the SOQL got hand-appended as `?q=...` directly onto `url` (often with a stray trailing slash, e.g. `/tooling/query/?q=SELECT...`) instead of passed as a separate `queryParams` object — the gateway rejects that literal path before the query ever runs. Fix: `url: "/services/data/vXX/tooling/query"` (no trailing slash, no `?q=`) with `queryParams: {"q": "<SOQL>"}`. Retry with that shape before treating it as a real outage.
- Nuances: (a) `/tooling/query FROM GenAiPlugin` returns `INVALID_TYPE` (that type isn't exposed to the query surface — consistent, not intermittent) — query **`GenAiPluginDefinition`** instead; (b) tooling-only entities (`EntityDefinition`, `ApplicationRecordTypeConfig`) need `/tooling/query`, not data `/query`; (c) `RecordType.DeveloperName` needs **data** `/query` (tooling `/query` returns `400 INVALID_FIELD`); (d) `EntityDefinition` rejects `OR` disjunctions — use `IN (...)`. Read **by known record Id / DurableId** and sObject **GET by Id** also route. (sObject GET does not accept `?fields=` — the router treats it as an external-id path segment.)
## Tier 2 — `sf` CLI (MDAPI deploy of local source)
Requires a **shell** — available to a customer who has the CLI configured, **not** to a pure hosted-MCP runtime. It is the **fallback** for the tier-1 writes above (OWD `sharingModel`, `RecordType`, Campaign `StandardValueSet`) when tier 1 isn't reachable. Use `sf project deploy start` (component metadata), `sf org assign permset`, and `sf data query` (verify fallback only — `/query` is tier-1-routable, see the read-routing ladder above; `sf data query` is the tier-2 fallback for a discovery read during a `/query` outage window). Generate-then-deploy prior art exists as sibling skills the reference files name: OWD via `platform-sharing-owd-configure`, record types + picklist scoping via `platform-custom-field-generate`.
**WARNING: Sharing-rule create is NOT a tier-2 escape** — it fails identically at `sf`-deploy as at tier 1, a genuine tier-3 UI gap. See `permissions.md` Step 6b for the exact error and why the sibling deploy skills can't help.
> **Grounding (Learning Program / Data Cloud) has no tier-2 path** — the async index/embedding build has no supported public API and can only be triggered from the Setup UI. Treat grounding as **tier-1 Connect-REST attempt → tier-3 UI**; do NOT present a tier-2 `sf`-deploy path. See `grounding.md` for the specific types and why.
## Tier 3 — Manual Setup-UI steps
When neither runtime tier works, hand the user the exact Setup path, wait for confirmation, then run the verify (tier-1 read-by-Id if possible, else the tier-2 `sf` / UI check). Every step ends in a concrete verify so the agent confirms org state rather than assuming the human's UI action succeeded.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 119k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |