Sf Industry Commoncore Flexcard
Scaffold Salesforce OmniStudio FlexCard JSON wired to Integration Procedures with industry-common-core naming conventions.
Overview
sf-industry-commoncore-flexcard is an agent skill for the Build phase that templates OmniStudio FlexCard JSON bound to Integration Procedures for Salesforce Industry Cloud UIs.
Install
npx skills add https://github.com/jaganpro/sf-skills --skill sf-industry-commoncore-flexcardWhat is this skill?
- JSON skeleton for Child OmniUiCardType with Integration Procedures datasource
- Placeholder tokens for CardName, IPType, IPSubType, recordId context, and PropertySetConfig states
- DataSourceConfig pattern: ipMethod {{IPType}}_{{IPSubType}}, vlocityAsync false, inputMap recordId
- Default inactive card (IsActive false) for safe authoring before activation
- Aligned with OmniStudio MCP server patterns for validation and dependency analysis
- Default VersionNumber 1
- Single Active state block in PropertySetConfig template
Adoption & trust: 874 installs on skills.sh; 418 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need a new FlexCard hooked to an Integration Procedure but hand-rolling DataSourceConfig and PropertySetConfig JSON is error-prone and drifts from OmniStudio conventions.
Who is it for?
Salesforce developers and consultants building Industry Cloud experiences with OmniStudio FlexCards and IPs.
Skip if: Solo indie builders on vanilla React or Next.js stacks with no Salesforce org—skip unless you own OmniStudio customization.
When should I use this skill?
Authoring or extending a Salesforce OmniStudio FlexCard that calls an Integration Procedure with recordId context using industry naming patterns.
What do I get? / Deliverables
You get a filled FlexCard definition with IP method naming, recordId input map, and SLDS card state ready for org deployment or MCP validation.
- FlexCard metadata JSON with DataSourceConfig and PropertySetConfig
- Templated card title, description, and author fields
Recommended Skills
Journey fit
FlexCards are built while integrating Salesforce/Vlocity UI into a product surface, which maps to the Build phase rather than post-launch distribution work. Integrations subphase fits OmniStudio datasource binding, IP method naming, and FlexCard metadata that connects CRM records to custom UI cards.
How it compares
Salesforce metadata template skill, not a general React component generator or REST API scaffold.
Common Questions / FAQ
Who is sf-industry-commoncore-flexcard for?
Builders and admins implementing Salesforce OmniStudio FlexCards on Industry Cloud projects who want consistent IP datasource JSON.
When should I use sf-industry-commoncore-flexcard?
During Build integrations when adding or cloning a child FlexCard that loads data through a named Integration Procedure for a record context.
Is sf-industry-commoncore-flexcard safe to install?
The skill is template documentation; confirm publisher trust and review the Security Audits panel on this Prism page before use in production orgs.
SKILL.md
READMESKILL.md - Sf Industry Commoncore Flexcard
{ "Name": "{{CardName}}", "VersionNumber": 1, "OmniUiCardType": "Child", "IsActive": false, "Description": "{{Description}}", "DataSourceConfig": "{\"dataSource\":{\"type\":\"IntegrationProcedures\",\"value\":{\"ipMethod\":\"{{IPType}}_{{IPSubType}}\",\"vlocityAsync\":false,\"inputMap\":{\"recordId\":\"{recordId}\"},\"resultVar\":\"\"},\"orderBy\":{\"name\":\"\",\"isReverse\":\"\"},\"contextVariables\":[]}}", "PropertySetConfig": "{\"states\":[{\"conditions\":{\"group\":[],\"id\":\"state-condition-object\",\"operator\":\"\"},\"fields\":[],\"id\":\"state-id-0\",\"isSmartAction\":false,\"name\":\"Active\",\"smartAction\":{},\"styleObject\":{\"class\":\"slds-card\",\"container\":{\"class\":\"slds-card\"}}}],\"title\":\"{{CardTitle}}\",\"iconName\":\"\",\"theme\":\"\",\"isFlyout\":false,\"datasource\":{\"contextVariables\":[],\"orderBy\":{},\"type\":\"\"}}", "AuthorName": "{{AuthorName}}" } # Credits ## sf-industry-commoncore-flexcard Skill Primary Contributor: [David Ryan (weytani)](https://github.com/weytani) ## References & Inspiration ### Primary Inspiration - **@salesforce/omnistudio-mcp** - Official Salesforce OmniStudio MCP server for FlexCard metadata authoring and validation. This is the primary inspiration for the skill's data source binding patterns and definition structure. - **sf-explorer/omnistudio-mcp-server** - Community OmniStudio MCP server focused on dependency analysis across FlexCards, Integration Procedures, and OmniScripts. ### Official Salesforce Documentation - [OmniStudio FlexCards Trailhead](https://trailhead.salesforce.com/content/learn/modules/omnistudio-flexcards) - Official Trailhead module covering FlexCard fundamentals - [OmniStudio Developer Guide](https://developer.salesforce.com/docs/atlas.en-us.industries_reference.meta/industries_reference/omnistudio_flexcards.htm) - Technical reference for OmniUiCard metadata - [Salesforce Industries Help](https://help.salesforce.com/s/articleView?id=sf.os_flexcards.htm) - FlexCard configuration and administration guide - [OmniStudio Data Sources](https://help.salesforce.com/s/articleView?id=sf.os_flexcards_data_sources.htm) - Data source types and configuration ### Salesforce Industries Engineering - Salesforce Industries engineering team for the OmniStudio platform, FlexCard runtime, and declarative data binding framework ### Trailhead Learning Resources - [Build OmniStudio FlexCards](https://trailhead.salesforce.com/content/learn/modules/omnistudio-flexcards) - Hands-on FlexCard creation - [OmniStudio Integration Procedures](https://trailhead.salesforce.com/content/learn/modules/omnistudio-integration-procedures) - Companion module for data source IPs - [OmniStudio OmniScripts](https://trailhead.salesforce.com/content/learn/modules/omnistudio-omniscripts) - Companion module for OmniScript actions ## Key Patterns Incorporated | Pattern | Source | Description | |---------|--------|-------------| | IP Data Source Binding | @salesforce/omnistudio-mcp | Integration Procedure merge field mapping | | Dependency Analysis | sf-explorer/omnistudio-mcp-server | Cross-component dependency chain validation | | Card Layout Patterns | Salesforce Industries Docs | Single, list, tabbed, and flyout card types | | OmniScript Launch Actions | OmniStudio Trailhead | Action button configuration for guided processes | | Conditional Visibility | OmniStudio Developer Guide | Data-driven show/hide rules for fields and states | | 130-Point Scoring Rubric | David Ryan (weytani) | Validation framework across 7 quality categories | ## License MIT License - See [LICENSE](../../LICENSE) MIT License Copyright (c) 2026 David Ryan and Jag Valaiyapathy Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell co