Sf Industry Commoncore Flexcard
Skill Verified ActiveOmniStudio FlexCard creation and validation with 130-point scoring. Use when building at-a-glance UI cards, configuring data source bindings to Integration Procedures, or reviewing existing FlexCard definitions for accessibility and performance. TRIGGER when: user creates FlexCards, configures data sources, designs card layouts, or asks about OmniUiCard metadata. DO NOT TRIGGER when: building OmniScripts (use sf-industry-commoncore-omniscript), creating Integration Procedures (use sf-industry-commoncore-integration-procedure), or analyzing dependencies (use sf-industry-commoncore-omnistudio-analyze).
To enable users to build robust, performant, and accessible OmniStudio FlexCards by providing expert guidance, validation scoring, and best practices for data binding and layout.
Features
- FlexCard definition generation
- 130-point scoring rubric for validation
- Detailed guidance on data source binding (IPs, SOQL, etc.)
- Configuration of card layout, states, and actions
- Workflow guidance from requirements to deployment and testing
Use Cases
- Building at-a-glance UI cards for Salesforce Industries
- Configuring data source bindings to Integration Procedures
- Reviewing existing FlexCard definitions for accessibility and performance
- Ensuring FlexCards adhere to best practices and standards
Non-Goals
- Building OmniScripts (use sf-industry-commoncore-omniscript)
- Creating Integration Procedures (use sf-industry-commoncore-integration-procedure)
- Analyzing dependencies across OmniStudio components (use sf-industry-commoncore-omnistudio-analyze)
Installation
npx skills add jaganpro/sf-skillsRuns the Vercel skills CLI (skills.sh) via npx — needs Node.js locally and at least one installed skills-compatible agent (Claude Code, Cursor, Codex, …). Assumes the repo follows the agentskills.io format.
Quality Score
VerifiedSimilar Extensions
Sf Industry Commoncore Integration Procedure
99OmniStudio Integration Procedure creation and validation with 110-point scoring. Use when building server-side process orchestrations that combine Data Mapper actions, Apex Remote Actions, HTTP callouts, and conditional logic. TRIGGER when: user creates Integration Procedures, adds Data Mapper steps, configures Remote Actions, or reviews existing IP configurations. DO NOT TRIGGER when: building OmniScripts (use sf-industry-commoncore-omniscript), creating Data Mappers directly (use sf-industry-commoncore-datamapper), or analyzing cross-component dependencies (use sf-industry-commoncore-omnistudio-analyze).
Sf Vlocity Build Deploy
98Salesforce Industries DataPack deployment automation using Vlocity Build. TRIGGER when: user deploys or validates OmniStudio/Vlocity DataPacks with vlocity commands (packDeploy/packRetry/packExport/packGetDiffs), sets up DataPack CI/CD pipelines, or troubleshoots DataPack migration errors. DO NOT TRIGGER when: deploying Salesforce metadata with sf project deploy (use sf-deploy), authoring OmniStudio artifacts (use sf-industry-commoncore-*), or writing Apex/LWC business logic (use sf-apex/sf-lwc).
Sf Industry Commoncore Omnistudio Analyze
98Cross-cutting OmniStudio analysis skill for namespace detection, dependency visualization, and impact analysis across OmniScripts, FlexCards, Integration Procedures, and Data Mappers. TRIGGER when: user asks about OmniStudio dependencies, wants namespace detection (Core vs vlocity_cmt vs vlocity_ins), needs impact analysis, or requests dependency diagrams. DO NOT TRIGGER when: authoring OmniScripts (use sf-industry-commoncore-omniscript), building FlexCards (use sf-industry-commoncore-flexcard), creating Integration Procedures (use sf-industry-commoncore-integration-procedure), or configuring Data Mappers (use sf-industry-commoncore-datamapper).
Setup Tailwind Typescript
100Configure Tailwind CSS with TypeScript in a Next.js or React project. Covers installation, configuration, custom theme extensions, component patterns, and type-safe styling utilities. Use when adding Tailwind CSS to an existing TypeScript project, customizing the Tailwind theme for a project's design system, setting up type-safe component styling patterns, or configuring Tailwind plugins and extensions.
Setup
100Use first for install/update routing — sends setup, doctor, or MCP requests to the correct OMC setup flow
Mcp Setup
100Configure popular MCP servers for enhanced agent capabilities