Skip to content

forcedotcom/sf-skills / skills/service-de-headless-channel-configure

service-de-headless-channel-configure

Verified

Top-level orchestrator: given a messaging channel type and its inputs, produces an activated Enhanced `MessagingChannel` in the target org — without the Meta/LINE/Apple setup popups. Prompts for `{MESSAGE_TYPE}` if not supplied, then sequences insert → route → consent → activate → requested settings (auto-responses, keywords, session inactivity) via the type-agnostic dispatcher (`service-de-channel-create`) plus the shared routing/settings/activation leaves, and reports every requested setting as configured, not applicable, or failed. Resumes from partial state on re-run. Use to set up an Enhanced channel (WhatsApp, Facebook, LINE, Apple, SMS) end-to-end, bypassing in-org setup popups. Do not use for a single stage of an already-inserted channel — use the matching leaf skill (`service-de-channel-activate`, `service-de-channel-settings-configure`, `service-de-channel-routing-configure`) instead.

references/partial-success.md

View on GitHub
---
name: service-de-headless-channel-configure-partial-success
description: "Load when the orchestrator fails mid-way through Stage 2-4 and you need to render the partial-success/resume message to the user. Covers the stateSoFar rendering template showing which of insert/route/consent/activate landed before the failure and the retry instructions. DO NOT load for the success-path Stage 5 final summary or the terms-not-accepted envelope."
metadata:
  version: "1.0"
  related-skills: service-de-headless-channel-configure
---

# Partial-success and resume reporting

If the orchestrator fails mid-way, the envelope always includes `stateSoFar` describing what landed. Render as:

```text
Error: Step {N} of 4 ({stepName}) failed: {leafEnvelope.kind} — {leafEnvelope.message or hint}

   What's already in place:
   - Channel inserted: {channelId ? "yes — " + channelId : "no"}
   - Routing configured: {sessionHandlerId ? "yes — " + queueName : "no"}
   - Consent configured: {(stepsRun.includes("consent") || (stepsSkipped || []).includes("consent")) ? "yes" : "no"}
   - Activation: {isActive ? "yes" : "no"}
   - Requested settings: not attempted — {each REQUESTED_SETTINGS item}   (only when any were requested)

   To retry: fix the issue above, then re-run this skill with the same
   inputs. The orchestrator will skip completed steps.
```
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 323kUpdated Claude CodeCodexVerifiedInstall