omnistudio-flexcard-generate

Generate and validate Salesforce OmniStudio FlexCard metadata with a 130-point scoring workflow.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG --skill omnistudio-flexcard-generate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omnistudio-flexcard-generate
Source: https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG/tree/main/.agents/skills/omnistudio-flexcard-generate
Command: npx skills add https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG --skill omnistudio-flexcard-generate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sf, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill removes the guesswork and manual effort involved in creating, validating, and deploying Salesforce OmniStudio FlexCards so teams can ship reliable UI cards faster.

Core Features & Use Cases

  • FlexCard Authoring: Generate production-ready OmniUiCard metadata with data sources, layout states, and actions.
  • Validation and Scoring: Review cards against a 130-point rubric covering layout, data binding, styling, accessibility, testing, and performance.
  • Deployment Guidance: Confirm upstream Integration Procedures are active, prepare deploy commands, and verify activation and embedding.
  • Use Case: A Salesforce developer can use this Skill to build a customer summary card, bind it to an Integration Procedure, check accessibility and empty states, and then deploy it confidently.

Quick Start

Ask the Skill to generate a FlexCard definition for your use case and validate it against the scoring rubric.

Frequently Asked Questions about omnistudio-flexcard-generate

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

FAQPage Schema
How do I generate and validate Salesforce OmniStudio FlexCard metadata?

Generate Salesforce OmniStudio FlexCard metadata by mapping OmniUiCard DataSourceConfig and PropertySetConfig, then validate it against a 130-point rubric covering layout, data binding, styling, and accessibility. This ensures production-ready UI cards with SLDS-compliant styling.

What do I need to configure FlexCard data sources and Integration Procedures?

Configuring FlexCard data sources requires active upstream Integration Procedures mapped to the OmniUiCard DataSourceConfig. You must verify these procedures are active before binding them to your card to ensure successful data retrieval and deployment.

Can I deploy FlexCards using the Salesforce CLI?

Yes. Deploy FlexCards using the Salesforce CLI by preparing deploy commands and verifying activation and embedding. The workflow confirms upstream Integration Procedures are active and validates the metadata structure before executing the deployment.

What is the best way to structure FlexCard layouts and actions for production?

Structure FlexCard layouts and actions by correctly mapping PropertySetConfig and designing layout states within the OmniUiCard metadata. Applying SLDS-compliant styling and passing the 130-point validation rubric guarantees a reliable, production-ready card.

Why does my FlexCard deployment fail when the Integration Procedure is inactive?

FlexCard deployment fails when upstream Integration Procedures are inactive because the OmniUiCard DataSourceConfig cannot bind to a non-existent data source. You must activate the Integration Procedure and verify the binding before deploying.