sf-industry-commoncore-flexcard

Creates and validates OmniStudio FlexCard definitions with Integration Procedure data binding and 130-point scoring.

1|Updated May 7, 2026
One-click install
npx skills add https://github.com/amanpraaj/sf-skill-hub --skill sf-industry-commoncore-flexcard-amanpraaj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sf-industry-commoncore-flexcard
Source: https://github.com/amanpraaj/sf-skill-hub/tree/main/skills/salesforce/sf-industry-commoncore-flexcard
Command: npx skills add https://github.com/amanpraaj/sf-skill-hub --skill sf-industry-commoncore-flexcard-amanpraaj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Building OmniStudio FlexCards for Salesforce Industries requires precise knowledge of OmniUiCard metadata structure, Integration Procedure data source binding, SLDS styling, and accessibility rules. This Skill generates production-ready FlexCard definitions and validates them against a 130-point scoring rubric across 7 quality categories, preventing broken data bindings, accessibility failures, and deployment errors. ## Core Features & Use Cases - FlexCard Authoring: Generate FlexCard definitions with single, list, tabbed, or flyout layouts, including states, field mappings, and action buttons that launch OmniScripts. - Data Source Binding: Configure Integration Procedure data sources with correct input mapping, merge field syntax, resultListPath, and multi-source coordination. - 130-Point Validation: Score cards across Design & Layout, Data Binding, Actions, Styling, Accessibility, Testing, and Performance, blocking deployment below 67 points. - Use Case: You need an account summary card on a Lightning record page that pulls data from an Integration Procedure and launches an OmniScript. The Skill generates the OmniUiCard JSON, validates the IP reference, and scores the result before deployment. ## Quick Start Ask the agent to create a FlexCard that displays account summary data from an existing Integration Procedure with an action button launching an OmniScript.

Frequently Asked Questions about sf-industry-commoncore-flexcard

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

FAQPage Schema
How do I create a FlexCard with an Integration Procedure data source?▼

Configure the OmniUiCard DataSourceConfig with type IntegrationProcedures, set ipMethod to the IP Type and SubType joined by underscore, and map input parameters like recordId. The IP must be active and deployed before the FlexCard can retrieve data.

When should I use a FlexCard instead of an LWC?▼

Use FlexCards for declarative at-a-glance information display bound to Integration Procedures. Choose LWC when you need complex interactive UIs, custom animations, Jest unit testing, or full platform flexibility beyond the OmniStudio framework.

Does OmniUiCard have a Definition field in Core namespace?▼

No. OmniUiCard in Core namespace uses DataSourceConfig for data source bindings and PropertySetConfig for card layout, states, and actions. There is no Definition field, which is a common authoring mistake.

Why is my FlexCard not loading data from the Integration Procedure?▼

Common causes include the IP not being activated, a case-sensitive mismatch in the ipMethod Type_SubType value, incorrect merge field paths, or missing user permissions. Verify IP activation and test with the OmniStudio Preview tool.

What are the limitations of FlexCard child card nesting?▼

Child card nesting should be limited to 2 levels maximum to avoid performance degradation. Pass data from parent to child via input parameters, avoid duplicate data sources between parent and child, and design children to work standalone.