sf-service-config-api-cli

Translate Service Cloud requirements into API surface and sf CLI deployment plans.

15|Updated Jan 27, 2026

Search Tags:#deployment #api #metadata #sf-cli #service-cloud

Ready to run

npx skills add https://github.com/sfdc-brendan/Demo-Lab --skill sf-service-config-api-cli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sf-service-config-api-cli
Source: https://github.com/sfdc-brendan/Demo-Lab/tree/main/Service%20Cloud/skills/sf-service-config-api-cli
Command: npx skills add https://github.com/sfdc-brendan/Demo-Lab --skill sf-service-config-api-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translating Service Cloud requirements into precise API surface definitions, deployment steps, and CLI commands can be error-prone when done manually. This Skill provides a structured approach to convert features into repeatable deployment plans, reducing misconfigurations and rework.

Core Features & Use Cases

Map each Service Cloud feature to a defined API surface type (Metadata, REST, SOAP, Tooling) and a reproducible sf CLI deployment path.
Generate an end-to-end deployment plan with ordered commands, data seeding guidance, and rollback considerations for safe releases.
Example Use Case: plan the rollout of CaseSettings and AssignmentRules across environments with validation checks and rollback hooks.

Quick Start

Translate a Service Cloud requirement into exact API surface and sf CLI deployment commands for a repeatable deployment plan.

Frequently Asked Questions about sf-service-config-api-cli

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

FAQPage Schema

How do I translate Service Cloud requirements into sf CLI deployment commands?▼

To plan CaseSettings and AssignmentRules deployment across environments, generate an end-to-end sf CLI deployment plan with ordered commands, data seeding guidance, and rollback hooks. This structured approach ensures safe releases with validation checks for Service Cloud metadata configurations.

What's the best way to generate a rollback plan for Service Cloud metadata deployments?▼

To map a Service Cloud feature to an API surface, identify whether the configuration requires Metadata, REST, SOAP, or Tooling API. This determines the exact sf CLI deployment path and required tooling to ensure reproducible releases across environments.

Can I use this approach to deploy both data and UI configurations in Service Cloud?▼

Yes, you can use this approach for Service Cloud projects without external dependencies. It provides a structured method to convert features into repeatable sf CLI deployment plans, reducing misconfigurations and rework when rolling out configurations across environments.

Why do I need a structured deployment plan for Service Cloud features?▼

You should use this approach when rolling out Service Cloud configurations like CaseSettings across multiple environments. It applies to feature-to-deploy planning across metadata, data, and UI configurations, ensuring reproducible releases with validation checks and rollback hooks.