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 |
references/bulk-batching.md
View on GitHub# Bulk Dispatch Rules — `create_cms_content` / `update_cms_content_variant`
Single source of truth for how bulk operations are dispatched. Referenced from SKILL.md Step 5b.
## The rule in one sentence — HARD RULE
**Dispatch exactly ONE `create_cms_content` call per item, with a 1-element `inputs` array, and fan out all N calls in parallel in a single turn.** No exceptions, no thresholds, no batching, no grouping.
This applies for every N ≥ 1. Single content (N=1) is one call; bulk (N ≥ 2) is N calls, dispatched in parallel.
## Why one-call-per-item
- **Matches the server-side generation model.** Each `create_cms_content` runs the Vibes MC content pipeline for one record; keeping calls 1:1 with records means one server-side generation per wire call, which is how the pipeline is tuned.
- **Bounded blast radius = 1.** A dropped connection loses exactly one record. Retry is trivial — the same 1-element payload, redispatched.
- **Trivial partial-failure handling.** Each call's success or failure is independent and known individually. No need to walk an `outputs` array or reconcile which sub-item failed.
- **Simpler mental model for the skill.** No batch-size math, no balancing, no re-batching on retry.
## Do NOT
- **Do NOT put more than one element in `inputs`.** Even for N=2, do NOT send one `create_cms_content` with a 2-element `inputs` array. Every call is exactly one element.
- **Do NOT serialize.** For N ≥ 2, dispatch all N calls in the same turn in parallel — do not dispatch call 1, await, then dispatch call 2. Serialization defeats the parallelism this rule enables.
- **Do NOT batch on retry.** If items 3 and 7 failed, retry them as two separate parallel 1-element calls — never combine into a single 2-element `inputs` array.
- **Do NOT mention dispatch mechanics to the user.** The user asked for N content items — they see "N items." Do NOT mention parallel calls, `create_cms_content`, or the tool id. Say `Ready to create 7 items` — NOT `Ready to dispatch 7 parallel create_cms_content calls`.
- **Do NOT narrate tool preparation.** If the runtime lazy-loads `create_cms_content` at dispatch time, do the tool-schema fetch inside the same turn as 5b — no `"Let me load the content creation tool"`, no `"Loading tool schema"`, no `"Fetching create_cms_content"`. The user should see the dispatched results, not the plumbing that got you there.
## Same shape applies to `update_cms_content_variant`
Bulk edits (Step 8d) follow the same rule: one `update_cms_content_variant` call per selected item, 1-element `inputs`, all N dispatched in parallel. Each call carries its own `variantId` + its own `prompt`.
## Bulk topic generation + approval (Step 4, quantity > 1)
Referenced from SKILL.md Step 4 "Bulk Content". Runs before the parallel dispatch above.
**4.B.1. Generate topic prompts.** Generate N distinct topic prompts (N = explicit count, or 4–5 if unspecified), each a unique angle within the user's domain.
**4.B.2. Present topics for approval — TWO-PART output.**
Part 1 — print the topic list as formatted chat text (markdown) so line breaks and numbering render:
```markdown
I'll create **<N>** content items of type `<FQN>`. Here are the topics:
1. **<short title 1>** — <topic prompt 1>
2. **<short title 2>** — <topic prompt 2>
3. **<short title 3>** — <topic prompt 3>
You can approve as-is, remove items by number, add new topics, or rewrite any prompt.
```
Part 2 — immediately after the text, dispatch the Step 4.B.2 approval prompt from `assets/questions.md`. Never put the full topic list inside the `ask_user_tool` question (see `references/ux-rules.md`).
**4.B.3. Handle response.**
- `Looks good, create them` → proceed to 4.B.4 with the listed prompts.
- `Let me adjust` → wait for the user's modifications (remove / add / rewrite), then re-present the final list for a single confirmation. Do NOT loop more than once — after the second presentation, proceed with whatever the user confirms.
**4.B.4. Prepare N single-item payloads.** Use `assets/payloads/create-content-bulk.json` as the per-call shape — build N independent 1-element `inputs` payloads (one per approved topic). All share the same `contentType` and `contentSpaceOrFolderId`; each carries its own `title` (agent-generated for that topic) and `prompt` (that topic's approved prompt verbatim). Step 5b dispatches those N calls in parallel per the HARD RULE above.
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 |