Agent skill

Sf Industry Commoncore Flexcard

by Jaganpro in Jaganpro/sf-skills

OmniStudio FlexCard creation and validation with 130-point scoring.

MITAuto-check passedFrontend & Design

Install Sf Industry Commoncore Flexcard

skills CLI
$ npx skills add Jaganpro/sf-skills --skill sf-industry-commoncore-flexcard -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Jaganpro/sf-skills sf-industry-commoncore-flexcard --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sf-industry-commoncore-flexcard .claude/skills/sf-industry-commoncore-flexcard && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
sf-industry-commoncore-flexcard
GitHub stars
424
Token cost
~4.7k tokens
SKILL.md length
1,909 words
Files
6 (incl. references, assets)
Skills in repo
36
Repo updated
First seen
Licence
MIT

At a glance

OmniStudio FlexCard creation and validation with 130-point scoring.

  • Works in 5 steps: Requirements Gathering → Design & Layout → Generation & Validation → …
  • Building at-a-glance UI cards
  • SKILL.md covers Core Responsibilities, Document Map, CRITICAL: Orchestration Order and Key Insights, plus 11 more sections
  • Calls sf

What it does

Sf Industry Commoncore Flexcard is an agent skill from Jaganpro/sf-skills. OmniStudio 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…

Its SKILL.md is about 4.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files and assets (for example `CREDITS.md`, `assets/omni-ui-card.json` and `references/best-practices.md`).

It sits in Frontend & Design, covering Accessibility. The repository describes itself as: [ARCHIVED — migrated to forcedotcom/afv-library] Salesforce Skills for Agentic Coding Tools — Apex, Flow, LWC, SOQL, Agentforce, Data Cloud, OmniStudio. Read-only archive; active… The licence is MIT.

When your agent uses it

  • Building at-a-glance UI cards
  • Configuring data source bindings to Integration Procedures
  • Reviewing existing FlexCard definitions for accessibility and performance
  • : user creates FlexCards

Example prompts

  • “/sf-industry-commoncore-flexcard”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Requirements Gathering
  2. Design & Layout
  3. Generation & Validation
  4. Deployment
  5. Testing

What it can do on your machine

Read from SKILL.md and the folder at commit 53c9956. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • sf

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • trailhead.salesforce.com
    • developer.salesforce.com
    • help.salesforce.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sf Industry Commoncore Flexcard loads about 4.7k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 160 tokens; SKILL.md has 1,909 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~160
When it runs · the whole SKILL.md, loaded when a task matches
~4.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~11k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Jaganpro/sf-skills at commit 53c9956, republished under its MIT licence (© Jaganpro). 1,909 words, ~4,703 tokens.

Download SKILL.mdSave it as .claude/skills/sf-industry-commoncore-flexcard/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
sf-industry-commoncore-flexcard
description
OmniStudio 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).
license
MIT
metadata.version
1.0.0
metadata.author
David Ryan (weytani)
metadata.scoring
130 points across 7 categories

sf-industry-commoncore-flexcard: OmniStudio FlexCard Creation and Validation

Expert OmniStudio engineer specializing in FlexCard UI components for Salesforce Industries. Generate production-ready FlexCard definitions that display at-a-glance information with declarative data binding, Integration Procedure data sources, conditional rendering, and proper SLDS styling. All FlexCards are validated against a 130-point scoring rubric across 7 categories.

Core Responsibilities

  1. FlexCard Authoring: Design and build FlexCard definitions with proper layout, states, and field mappings
  2. Data Source Binding: Configure Integration Procedure data sources with correct field mapping and error handling
  3. Test Generation: Validate cards against multiple data states (populated, empty, error, multi-record)
  4. Documentation: Produce deployment-ready documentation with data source lineage and action mappings

Document Map

NeedDocumentDescription
Best practicesreferences/best-practices.mdLayout patterns, SLDS, accessibility, performance
Data bindingreferences/data-binding-guide.mdIP sources, field mapping, conditional rendering

CRITICAL: Orchestration Order

FlexCards sit at the presentation layer of the OmniStudio stack. Ensure upstream components exist before building a FlexCard that depends on them.

sf-industry-commoncore-omnistudio-analyze → sf-industry-commoncore-datamapper → sf-industry-commoncore-integration-procedure → sf-industry-commoncore-omniscript → sf-industry-commoncore-flexcard (you are here)

FlexCards consume data from Integration Procedures and can launch OmniScripts. Build the data layer first, then the presentation layer.


Key Insights

InsightDetail
Configuration fieldsOmniUiCard uses DataSourceConfig for data source bindings and PropertySetConfig for card layout, states, and actions. There is NO Definition field on OmniUiCard in Core namespace.
Data source bindingData sources bind to Integration Procedures for live data; the IP must be active and deployed before the FlexCard can retrieve data
Child card embeddingFlexCards can embed other FlexCards as child cards, enabling composite layouts with shared or independent data sources
OmniScript launchingFlexCards can launch OmniScripts via action buttons, passing context data from the card's data source into the OmniScript's input
Designer virtual objectThe FlexCard Designer uses OmniFlexCardView as a virtual list object (/lightning/o/OmniFlexCardView/home), separate from the OmniUiCard sObject where card records are stored. Cards created via API may not appear in "Recently Viewed" until opened in the Designer.

Workflow (5-Phase Pattern)

Phase 1: Requirements Gathering

Before building, clarify these with the stakeholder:

QuestionWhy It Matters
What is the card's purpose?Determines layout type and data density
Which data sources are needed?Identifies required Integration Procedures
What object context does it run in?Determines record-level vs. list-level display
What actions should the card expose?Drives button/link configuration and OmniScript integration
What layout best fits the use case?Single card, list, tabbed, or flyout
Are there conditional display rules?Fields or sections that appear/hide based on data values
Phase 2: Design & Layout
Card Layout Options
Layout TypeUse CaseDescription
Single CardRecord summaryOne card displaying fields from a single record
Card ListRelated recordsRepeating cards bound to an array data source
Tabbed CardMulti-contextMultiple states displayed as tabs within one card
Flyout CardDetail on demandExpandable detail panel triggered from a summary card
Data Source Configuration

Each FlexCard data source connects to an Integration Procedure (or other source type) and maps response fields to display elements.

FlexCard → Data Source (type: IntegrationProcedure)
         → IP Name + Input Mapping
         → Response Field Mapping → Card Elements
  • Map IP response fields to card display elements using {datasource.fieldName} merge syntax
  • Configure input parameters to pass record context (e.g., {recordId}) to the IP
  • Set data source order when multiple sources feed the same card
Action Button Design
Action TypePurposeConfiguration
Launch OmniScriptStart a guided processOmniScript Type + SubType, pass context params
NavigateGo to record or URLRecord ID or URL template with merge fields
Custom ActionPlatform event, LWC, etc.Custom action handler with payload mapping
Conditional Visibility
  • Show/hide fields based on data values using visibility conditions
  • Show/hide entire card states based on data source results
  • Display empty-state messaging when data source returns no records
Phase 3: Generation & Validation
  1. Generate the FlexCard definition JSON
  2. Validate all data source references resolve to active Integration Procedures
  3. Run the 130-point scoring rubric (see Scoring section below)
  4. Verify merge field syntax matches IP response structure
  5. Check accessibility attributes on all interactive elements
Phase 4: Deployment
  1. Ensure all upstream Integration Procedures are deployed and active
  2. Deploy the FlexCard metadata (OmniUiCard)
  3. Activate the FlexCard in the target org
  4. Embed the FlexCard in the target Lightning page, OmniScript, or parent FlexCard
Phase 5: Testing

Test each FlexCard against multiple data scenarios:

ScenarioWhat to Verify
Populated dataAll fields render correctly, merge fields resolve
Empty dataEmpty-state message displays, no broken merge fields
Error stateGraceful handling when IP returns an error or times out
Multi-recordCard list renders correct number of items, pagination works
Action buttonsOmniScript launches with correct pre-populated data
Conditional fieldsVisibility rules toggle correctly based on data values
MobileCard layout adapts to smaller viewport widths

Generation Guardrails

Avoid these patterns when generating FlexCard definitions:

Anti-PatternWhy It's WrongCorrect Approach
Referencing non-existent IP data sourcesCard fails to load data at runtimeVerify IP exists and is active before binding
Hardcoded colors in stylesBreaks SLDS theming and dark modeUse SLDS design tokens and CSS custom properties
Missing accessibility attributesFails WCAG complianceAdd aria-label, role, and keyboard handlers
Excessive nested child cardsPerformance degrades with deep nestingLimit to 2 levels of nesting; flatten where possible
Ignoring empty statesBroken UI when data source returns no recordsConfigure explicit empty-state messaging
Hardcoded record IDsCard breaks across environmentsUse merge fields and context-driven parameters

Scoring Rubric (130 Points)

All FlexCards are validated against 7 categories. Thresholds: ✅ 90+ (Deploy) | ⚠️ 67-89 (Review) | ❌ <67 (Block - fix required)

CategoryPointsCriteria
Design & Layout25Appropriate layout type, logical field grouping, responsive design, consistent spacing, clear visual hierarchy
Data Binding20Correct IP references, proper merge field syntax, input parameter mapping, multi-source coordination
Actions & Navigation20Action buttons configured correctly, OmniScript launch params mapped, navigation targets valid, action labels descriptive
Styling20SLDS tokens used (no hardcoded colors), consistent typography, proper use of card/tile patterns, dark mode compatible
Accessibility15aria-label on interactive elements, keyboard navigable actions, sufficient color contrast, screen reader friendly field labels
Testing15Verified with populated data, empty state, error state, multi-record scenario, and mobile viewport
Performance15Data source calls minimized, child card nesting limited (max 2 levels), no redundant IP calls, lazy loading for non-visible states
Scoring Breakdown Detail
Design & Layout (25 points)
CriterionPointsDescription
Layout type matches use case5Single, list, tabbed, or flyout chosen appropriately
Field grouping is logical5Related fields are visually grouped together
Responsive behavior5Card adapts to different viewport widths
Consistent spacing5Margins and padding follow SLDS spacing scale
Visual hierarchy5Primary information is prominent, secondary is de-emphasized
Data Binding (20 points)
CriterionPointsDescription
IP references are valid5All referenced IPs exist and are active
Merge field syntax correct5{datasource.field} paths resolve to actual IP response fields
Input parameters mapped5Record context passed correctly to IP inputs
Multi-source coordination5Multiple data sources load in correct order without conflicts
Show full SKILL.md (777 more words)Show less
Actions & Navigation (20 points)
CriterionPointsDescription
Action buttons functional5All buttons trigger their configured actions
OmniScript params mapped5Context data flows correctly into launched OmniScripts
Navigation targets valid5Record and URL navigation resolves correctly
Labels are descriptive5Action labels clearly communicate what the action does
Styling (20 points)
CriterionPointsDescription
SLDS tokens used5Colors, fonts, spacing via design tokens
Consistent typography5Text sizes follow SLDS type scale
Card pattern compliance5Uses standard SLDS card or tile patterns
Dark mode compatible5No hardcoded colors; works with SLDS dark theme
Accessibility (15 points)
CriterionPointsDescription
ARIA labels on interactive elements5Buttons, links, and inputs have accessible names
Keyboard navigable5All actions reachable via Tab, activated via Enter/Space
Color contrast sufficient5Meets WCAG 2.1 AA contrast ratio (4.5:1 for text)
Testing (15 points)
CriterionPointsDescription
Populated data verified3Card renders correctly with full data
Empty state verified3Empty-state message displays properly
Error state verified3Graceful handling of IP errors
Multi-record verified3Card list renders correct items
Mobile viewport verified3Layout adapts to small screens
Performance (15 points)
CriterionPointsDescription
Data source calls minimized5No redundant or duplicate IP invocations
Child card nesting limited5Maximum 2 levels of nested child cards
Lazy loading for hidden states5Non-visible tabs/flyouts load on demand

CLI Commands

bash
# Query active FlexCards in the org
sf data query -q "SELECT Id,Name,DataSourceConfig,PropertySetConfig,IsActive FROM OmniUiCard WHERE IsActive=true" -o <org>

# Retrieve a specific FlexCard by name
sf project retrieve start -m OmniUiCard:<Name> -o <org>

# Deploy a FlexCard to the target org
sf project deploy start -m OmniUiCard:<Name> -o <org>

# Retrieve all FlexCards
sf project retrieve start -m OmniUiCard -o <org>

# Deploy all OmniStudio metadata (FlexCards + dependencies)
sf project deploy start -m OmniUiCard -m OmniIntegrationProcedure -m OmniScript -o <org>

Data Source Binding

FlexCard Data Source Configuration

The DataSourceConfig field on OmniUiCard contains the data source bindings as JSON. The PropertySetConfig field contains the card layout, states, and field definitions.

IMPORTANT: There is NO Definition field on OmniUiCard in Core namespace. Use DataSourceConfig for data sources and PropertySetConfig for layout.

json
{
  "dataSource": {
    "type": "IntegrationProcedures",
    "value": {
      "ipMethod": "Type_SubType",
      "vlocityAsync": false,
      "inputMap": {
        "recordId": "{recordId}"
      },
      "resultVar": ""
    },
    "orderBy": {
      "name": "",
      "isReverse": ""
    },
    "contextVariables": []
  }
}
Data Source Types
TypedataSource.typeWhen to Use
Integration ProcedureIntegrationProcedures (plural, capital P)Primary pattern; calls an IP for live data
SOQLSOQLDirect query (use sparingly; prefer IP for abstraction)
Apex RemoteApexRemoteCustom Apex class invocation
RESTRESTExternal API call via Named Credential
CustomCustomCustom data provider (pass JSON body directly)
Field Mapping from IP Response

Map IP response fields to card display elements using merge field syntax:

IP Response:                    FlexCard Merge Field:
─────────────                   ─────────────────────
{ "Name": "Acme Corp" }   →    {Name}
{ "Account": {            →    {Account.Name}
    "Name": "Acme Corp"
  }
}
{ "records": [             →    {records[0].Name}  (single)
    { "Name": "Acme" }          or iterate with Card List layout
  ]
}
Input Parameter Mapping

Pass context from the hosting page into the IP data source:

Context VariableSourceExample
{recordId}Current record pagePass to IP to query related data
{userId}Running userFilter data by current user
{param.customKey}URL parameter or parent cardPass from parent FlexCard or URL

Cross-Skill Integration

SkillRelationship to sf-industry-commoncore-flexcard
sf-industry-commoncore-integration-procedureBuild the IP data sources that FlexCards consume
sf-industry-commoncore-omniscriptBuild the OmniScripts that FlexCard action buttons launch
sf-industry-commoncore-datamapperBuild DataRaptors/DataMappers that IPs use under the hood
sf-industry-commoncore-omnistudio-analyzeAnalyze dependency chains across FlexCards, IPs, and OmniScripts
sf-deployDeploy FlexCard metadata along with upstream dependencies
sf-lwcBuild custom LWC components embedded within FlexCards

Edge Cases

ScenarioHandling
Empty dataConfigure an explicit empty-state with a user-friendly message; do not show raw "No data" or blank card
Error statesDisplay a meaningful error message when the IP data source fails; log the error for debugging
Mobile responsivenessUse single-column layout for mobile; avoid horizontal scrolling; test at 320px viewport width
Long text valuesTruncate with ellipsis and provide a flyout or tooltip for full text
Large record setsUse card list with pagination; limit initial load to 10-25 records
Null field valuesUse conditional visibility to hide fields with null values rather than showing empty labels
Mixed data freshnessWhen multiple data sources have different refresh rates, display a "last updated" indicator

FlexCard vs LWC Decision Guide

FactorFlexCardLWC
Build methodDeclarative (drag-and-drop)Code (JS, HTML, CSS)
Data bindingIntegration Procedure merge fieldsWire service, Apex, GraphQL
Best forAt-a-glance information displayComplex interactive UIs
TestingManual + data state verificationJest unit tests + manual
CustomizationLimited to OmniStudio frameworkFull platform flexibility
ReuseEmbed as child cardsImport as child components
When to chooseStandard card layouts with IP dataCustom behavior, animations, complex state

Dependencies

Required: Target org with OmniStudio (Industries Cloud) license, sf CLI authenticated For Data Sources: Active Integration Procedures deployed to the target org For Actions: Active OmniScripts deployed (if action buttons launch OmniScripts) Scoring: Block deployment if score < 67

Creating FlexCards programmatically: Use REST API (sf api request rest --method POST --body @file.json). Required fields: Name, VersionNumber, OmniUiCardType (e.g., Child). Set DataSourceConfig (JSON string) for data source bindings and PropertySetConfig (JSON string) for card layout. The sf data create record --values flag cannot handle JSON in textarea fields. Activate by updating IsActive=true after creation.


External References


License

MIT License. Copyright (c) 2026 David Ryan (weytani)

© Jaganpro, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references, assets) in skills/sf-industry-commoncore-flexcard of Jaganpro/sf-skills.

  • SKILL.md
  • CREDITS.md
  • LICENSE
  • assets/omni-ui-card.json
  • references/best-practices.md
  • references/data-binding-guide.md

Open the folder on GitHubat commit 53c9956

Compare with similar skills

Sf Industry Commoncore Flexcard next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sf Industry Commoncore Flexcard compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sf Industry Commoncore Flexcard this skillJaganpro/sf-skills424—~4.7kAutomated safety check: PassMIT
Web Interface Guidelines Reviewervercel-labs/openreview1.7k97 repos~308Automated safety check: PassNone
Accessibility Reviewmarkmead/hyperui12k1 repos~1.1kAutomated safety check: PassMIT
Web Animation DesignbaptisteArno/typebot.io11k2 repos~2.7kAutomated safety check: PassCustom licence
Accessibility Fixeribelick/ui-skills9.6k4 repos~1.2kAutomated safety check: PassMIT
Wcag Audit PatternsvmDeshpande/ai-agent-automation17811 repos~610Automated safety check: PassApache-2.0

Similar skills

  • Web Interface Guidelines Reviewer

    vercel-labs/openreview

    Official

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…

    1.7k GitHub starsUsed in 97 repos~308 tokens
    Frontend & DesignAuto-check passed
  • Accessibility Review

    markmead/hyperui

    Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.

    12k GitHub starsUsed in 1 repo~1.1k tokens
    Frontend & DesignAuto-check passed
  • Web Animation Design

    baptisteArno/typebot.io

    Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.

    11k GitHub starsUsed in 2 repos~2.7k tokens
    Frontend & DesignAuto-check passed
  • Accessibility Fixer

    ibelick/ui-skills

    Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.

    9.6k GitHub starsUsed in 4 repos~1.2k tokens
    Frontend & DesignAuto-check passed
  • Wcag Audit Patterns

    vmDeshpande/ai-agent-automation

    Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.

    178 GitHub starsUsed in 11 repos~610 tokens
    Frontend & DesignAuto-check passed
  • Baseline UI

    ibelick/ui-skills

    Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.

    9.6k GitHub starsUsed in 8 repos~855 tokens
    Frontend & DesignAuto-check passed

More from Jaganpro/sf-skills

All 36 skills in this repo
  • Agentforce session tracing extraction and analysis. An agent skill from Jaganpro/sf-skills.

    424 GitHub stars~1.8k tokensUpdated 5 mo ago
    Auto-check passed
  • Sf AI Agentscript

    Jaganpro/sf-skills

    Agent Script DSL for deterministic Agentforce agents. An agent skill from Jaganpro/sf-skills.

    424 GitHub stars~3.8k tokensUpdated 5 mo ago
    Auto-check passed
  • Sf Datacloud

    Jaganpro/sf-skills

    Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows.

    424 GitHub stars~2.7k tokensUpdated 5 mo ago
    Auto-check passed
  • Sf Diagram Mermaid

    Jaganpro/sf-skills

    Salesforce architecture diagrams using Mermaid with ASCII fallback.

    424 GitHub stars~1.4k tokensUpdated 5 mo ago
    Auto-check passed
  • Sf Diagram Nanobananapro

    Jaganpro/sf-skills

    AI-powered image generation for Salesforce visuals via Nano Banana Pro.

    424 GitHub stars~1.6k tokensUpdated 5 mo ago
    Auto-check passed
  • Sf Flow

    Jaganpro/sf-skills

    Creates and validates Salesforce Flows with 110-point scoring.

    424 GitHub stars~1.8k tokensUpdated 5 mo ago
    Auto-check passed

Questions about Sf Industry Commoncore Flexcard

What does Sf Industry Commoncore Flexcard do?

OmniStudio FlexCard creation and validation with 130-point scoring. Sf Industry Commoncore Flexcard is an agent skill from Jaganpro/sf-skills. OmniStudio FlexCard creation and validation with 130-point scoring.

When should I use Sf Industry Commoncore Flexcard?

Sf Industry Commoncore Flexcard fits situations like: building at-a-glance UI cards; configuring data source bindings to Integration Procedures; reviewing existing FlexCard definitions for accessibility and performance; : user creates FlexCards.

How do I install Sf Industry Commoncore Flexcard in Claude Code?

Run `npx skills add Jaganpro/sf-skills --skill sf-industry-commoncore-flexcard -a claude-code`. Or copy the skill folder (skills/sf-industry-commoncore-flexcard in Jaganpro/sf-skills) into .claude/skills/sf-industry-commoncore-flexcard in your project. Claude Code loads it when a task matches its description.

How do I install Sf Industry Commoncore Flexcard in Codex?

Run `npx skills add Jaganpro/sf-skills --skill sf-industry-commoncore-flexcard -a codex`. Or copy the skill folder (skills/sf-industry-commoncore-flexcard in Jaganpro/sf-skills) into .agents/skills/sf-industry-commoncore-flexcard in your project. Codex loads it when a task matches its description.

Can I use Sf Industry Commoncore Flexcard in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Jaganpro/sf-skills --skill sf-industry-commoncore-flexcard -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sf-industry-commoncore-flexcard, .gemini/skills/sf-industry-commoncore-flexcard, .github/skills/sf-industry-commoncore-flexcard and .opencode/skills/sf-industry-commoncore-flexcard in your project.

What does Sf Industry Commoncore Flexcard need to run?

Going by SKILL.md and its folder, Sf Industry Commoncore Flexcard needs the command-line tools its instructions call (sf).

Does Sf Industry Commoncore Flexcard access the network?

SKILL.md names 3 domains. As links in the text: trailhead.salesforce.com, developer.salesforce.com and help.salesforce.com. This is read from the text; nothing was executed.

Is Sf Industry Commoncore Flexcard safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Sf Industry Commoncore Flexcard use?

Sf Industry Commoncore Flexcard is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sf Industry Commoncore Flexcard use?

About 4.7k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.8k tokens, read only when the agent opens those files.

What are the alternatives to Sf Industry Commoncore Flexcard?

Skills that share tags, products or a category with Sf Industry Commoncore Flexcard: Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Accessibility Review (markmead/hyperui, 12k stars), Web Animation Design (baptisteArno/typebot.io, 11k stars) and Accessibility Fixer (ibelick/ui-skills, 9.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sf Industry Commoncore Flexcard?

Jaganpro (a GitHub user) maintains it in Jaganpro/sf-skills, which has 424 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on April 27, 2026.

Source: Jaganpro/sf-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.