sf-service-self-service-config

Package Experience Cloud metadata for self-service channel deployments.

15|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/sfdc-brendan/Demo-Lab --skill sf-service-self-service-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sf-service-self-service-config
Source: https://github.com/sfdc-brendan/Demo-Lab/tree/main/Service%20Cloud/skills/sf-service-self-service-config
Command: npx skills add https://github.com/sfdc-brendan/Demo-Lab --skill sf-service-self-service-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure Experience Cloud sites and self-service channels for Service Cloud, enabling packaging of Network, ExperienceBundle, NetworkBranding, NavigationMenu, Topics, and Audience strategy, and providing deployment sequencing for embedded service, bot, and community metadata.

Core Features & Use Cases

  • Bundling deployable metadata: plan and package Network, ExperienceBundle, NetworkBranding, NavigationMenu, TopicsForObjects, and DataCategoryGroup to enable repeatable deployments.
  • Channel and experience design: align branding, navigation, topics, and audiences across sites to support consistent customer journeys.
  • End-to-end deployment planning: define org settings, site shells, experience assets, and channel integrations with dependencies and validation steps.
  • Use Case: design a complete self-service Experience Cloud experience and deploy it across environments with proper sequencing and rollback notes.

Quick Start

Define your channel architecture and generate a deployable metadata bundle map for Experience Cloud deployments.

Frequently Asked Questions about sf-service-self-service-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I package and deploy Experience Cloud metadata for self-service sites?

To package and deploy Experience Cloud metadata, bundle Network, ExperienceBundle, NetworkBranding, NavigationMenu, and Topics components into a deployable map for repeatable releases across environments.

What metadata components do I need to configure for a self-service community deployment?

Configuring a self-service community deployment requires packaging Network, ExperienceBundle, NetworkBranding, NavigationMenu, TopicsForObjects, and DataCategoryGroup metadata to define site shells and experience assets.

How do I plan deployment sequencing for embedded service and bot metadata in Experience Cloud?

Plan deployment sequencing for embedded service and bot metadata by defining org settings, site shells, and channel integrations with dependency validation steps and rollback notes.

Can I use this approach to align branding and navigation across multiple Experience Cloud sites?

Yes, you can align branding and navigation across multiple Experience Cloud sites by orchestrating NetworkBranding, NavigationMenu, and Audience strategy to support consistent customer journeys.

What's the best way to configure topics and audience strategy for a Service Cloud self-service portal?

The best way to configure topics and audience strategy for a Service Cloud self-service portal is to bundle TopicsForObjects and DataCategoryGroup metadata with site shells to validate discoverability and support flow.

Why do my Experience Cloud site deployments fail due to missing dependency validation?

Experience Cloud deployments fail when dependency validation is missing because org settings, experience assets, and channel integrations require proper sequencing to validate discoverability and support flow.