forcedotcom/sf-skills / plugins/builder/experience-cms/skills/experience-cms-content-generate
experience-cms-content-generate
VerifiedCreates, edits, and publishes Salesforce CMS content of any kind — any domain, any topic. Single and bulk: create many in parallel, edit one or many, publish all or a subset. Use this skill ANY TIME a user asks to create, generate, write, draft, author, or add content, OR to update, edit, or revise a content record, OR to publish it, OR to delete/remove a content record. Triggers like "create a <thing> about X", "create 5 <things>", "update content <id>", "publish content <id>", "publish the record <id>", "make <id> live", "delete content <id>" — where <thing> is any user-named content type. Activates FIRST whenever content authoring, editing, publishing, or deletion is mentioned, regardless of subject. Handles the full workflow: finding the content type, resolving the workspace, creating content, editing or publishing it — including a record identified by its variantId. Does not apply to defining a content type / schema (use experience-cms-content-type-generate), cloning, versioning, workspaces, or media.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 23.5 KB |
| assets/display-formats.md | markdown | 2.6 KB |
| assets/payloads/create-content-bulk.json | config | 657 B |
| assets/payloads/create-content-single.json | config | 437 B |
| assets/payloads/publish-content.json | config | 651 B |
| assets/payloads/update-content.json | config | 421 B |
| assets/questions.md | markdown | 12.9 KB |
| examples/create-content-call.md | markdown | 4.1 KB |
| references/bulk-batching.md | markdown | 4.3 KB |
| references/content-type-classification.md | markdown | 10.3 KB |
| references/content-write-tool.md | markdown | 7.0 KB |
| references/delegation-protocol.md | markdown | 5.5 KB |
| references/edit-publish-workflow.md | markdown | 9.2 KB |
| references/error-recovery.md | markdown | 13.8 KB |
| references/identifier-resolution.md | markdown | 2.4 KB |
| references/intent-routing.md | markdown | 8.6 KB |
| references/principles.md | markdown | 7.6 KB |
| references/ux-rules.md | markdown | 4.5 KB |
| references/workspace-resolution.md | markdown | 5.9 KB |
examples/create-content-call.md
View on GitHub# Example `create_cms_content` payload
> **Read this first.** `sfdc_cms__article` and `0ZuKZ00000XXXXXXXX` below are **shape illustrations**, not defaults. The `contentType` FQN must come from `experience-cms-content-type-generate` against the live org — never copy the FQN from this file. The `contentSpaceOrFolderId` value comes from the user's answer to the Step 3 workspace question — never from a local file. A workspace will reject any type it isn't configured to support, so picking an FQN from training data or this example will fail with `"These content type(s) X are not supported by this space"`.
The `experience-cms-content-generate` skill dispatches `create_cms_content` with the user's goal on the **`prompt` channel**. The server-side pipeline (Vibes MC content pipeline) generates and validates the body against the type's schema. The agent generates only the `title` and shapes the payload.
## Example
User asked: *"Draft an article announcing our Q4 product launch — make it about the new analytics dashboard. Cover the problem it solves, three headline features (real-time KPIs, drill-down by segment, export to spreadsheet), availability date, and a call-to-action linking to the product page."*
Assume `experience-cms-content-type-generate` returned `contentTypeFqn: sfdc_cms__article`.
Agent generates only a title from `[USER GOAL]`:
- **Title:** `Q4 Launch — Analytics Dashboard`
Payload:
```json
{
"inputs": [
{
"contentType": "sfdc_cms__article",
"contentSpaceOrFolderId": "0ZuKZ00000XXXXXXXX",
"title": "Q4 Launch — Analytics Dashboard",
"prompt": "Draft an article announcing our Q4 product launch — make it about the new analytics dashboard. Cover the problem it solves, three headline features (real-time KPIs, drill-down by segment, export to spreadsheet), availability date, and a call-to-action linking to the product page."
}
]
}
```
Notes:
- **`title` reflects `[USER GOAL]`.** Not the user's message verbatim — the message was an authoring instruction, not a title.
- **`prompt` is `[USER GOAL]` verbatim.** Do not paraphrase, trim, or reformat — the server-side pipeline parses it directly.
- **No `contentBody` field.** `prompt` and `contentBody` are mutually exclusive; sending both fails. This skill never sends `contentBody`.
- **No client-side pre-flight validation.** The server owns validation.
- Single-element `inputs` array — the skill creates one record per element. **Bulk creation dispatches N separate `create_cms_content` calls in parallel, each with a 1-element `inputs` array** — one call per item is the hard rule (never combine items into a multi-element `inputs` array). See SKILL.md Step 5b and `references/bulk-batching.md`.
### Optional fields
These pass through only when the user explicitly named them:
```json
{
"inputs": [
{
"contentType": "<from-sibling>",
"contentSpaceOrFolderId": "<from-user-step-3>",
"title": "<agent-generated>",
"prompt": "<[USER GOAL] verbatim>",
"urlName": "q4-launch-analytics-dashboard"
}
]
}
```
### Successful response (abridged)
```json
{
"outputs": [
{
"managedContentId": "20YKZ00000XXXXXXXX",
"managedContentVersionId": "20XKZ00000XXXXXXXX",
"managedContentVariantId": "20ZKZ00000XXXXXXXX",
"contentKey": "MCRT_a1B2c3D4",
"contentFqn": "sfdc_cms__article",
"title": "Q4 Launch — Analytics Dashboard",
"urlName": "q4-launch-analytics-dashboard",
"apiName": "Q4_Launch_Analytics_Dashboard",
"contentSpace": { "id": "0ZuKZ00000XXXXXXXX", "label": "Marketing" },
"createdBy": { "id": "005KZ00000XXXXXXXX", "name": "Jane Doe" },
"createdDate": "2026-11-01T17:42:08.000Z",
"contentBody": { "title": "Q4 Launch — Analytics Dashboard", "body": "<h2>…</h2>", "excerpt": "…" }
}
]
}
```
The skill surfaces (at minimum) `title`, `contentKey`, `managedContentId`, `contentFqn`, and `contentSpace.label` — those are what the user needs to find the record again. Response latency is server-side-generation dependent — not guaranteed sub-second like a pure persist path.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |