New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Sf Industry Cme Epc Model

by Jaganpro in Jaganpro/sf-skills

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation.

MITAuto-check passedSales & Support

Install Sf Industry Cme Epc Model

skills CLI
$ npx skills add Jaganpro/sf-skills --skill sf-industry-cme-epc-model -a claude-code

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

GitHub CLI
$ gh skill install Jaganpro/sf-skills sf-industry-cme-epc-model --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-cme-epc-model .claude/skills/sf-industry-cme-epc-model && 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-cme-epc-model
GitHub stars
424
Token cost
~4.3k tokens
SKILL.md length
1,364 words
Files
74 (incl. references, assets)
Skills in repo
36
Repo updated
First seen
Licence
MIT

At a glance

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation.

  • Works in 11 steps: Identify Catalog Intent → Build Product2 Backbone → Add Attributes → …
  • Creating EPC products
  • SKILL.md covers Quick Reference, Asset Template Set, Core Responsibilities and Invocation Rules (Mandatory), plus 9 more sections
  • Calls sf

What it does

Sf Industry Cme Epc Model is an agent skill from Jaganpro/sf-skills. Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration…

Its SKILL.md is about 4.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 76 other files, including reference files and assets (for example `CREDITS.md`, `README.md` and `assets/attribute-assignment-template.json`).

It sits in Sales & Support, covering CRM management and CI/CD. It works with Salesforce. 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

  • Creating EPC products
  • Configuring product attributes
  • Building offer bundles with Product Child Items
  • Reviewing EPC DataPack JSON metadata for product catalog changes

Example prompts

  • “/sf-industry-cme-epc-model”

Workflow steps

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

  1. Identify Catalog Intent
  2. Build Product2 Backbone
  3. Add Attributes
  4. Build Offer Bundles
  5. Validate and Handoff
  6. Catalog Identity and Naming (20)
  7. EPC Product Structure (20)
  8. Attribute Modeling (25)
  9. Offer Bundle Composition (25)
  10. DataPack Integrity (15)
  11. Documentation and Handoff (15)

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):

    • 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 Cme Epc Model loads about 4.3k tokens when it runs, and up to ~5.6k if it reads all its reference files. Until then it costs about 175 tokens; SKILL.md has 1,364 words of instructions outside code blocks.

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

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,364 words, ~4,258 tokens.

Download SKILL.mdSave it as .claude/skills/sf-industry-cme-epc-model/SKILL.md (or your agent's skills folder). This skill also uses 73 other files; get the full folder from GitHub.
name
sf-industry-cme-epc-model
description
Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use sf-industry-commoncore-* skills), implementing Apex business logic (use sf-apex), or troubleshooting deployment pipelines (use sf-deploy).
license
MIT
metadata.version
1.0.0
metadata.author
Shreyas Dhond (ShreyasD)
metadata.scoring
120 points across 6 categories

sf-industry-cme-epc-model: CME EPC Product and Offer Modeling

Expert Salesforce Industries CME EPC modeler for creating Product2-based catalog entries, assigning configurable attributes, and building offer bundles through Product Child Item relationships.

This skill is optimized for DataPack-style metadata authoring. Use the canonical template set in assets/:

  • assets/product2-offer-template.json
  • assets/attribute-assignment-template.json
  • assets/product-child-item-template.json
  • assets/pricebook-entries-template.json
  • assets/price-list-entries-template.json
  • assets/object-field-attributes-template.json
  • assets/orchestration-scenarios-template.json
  • assets/decomposition-relationships-template.json
  • assets/compiled-attribute-overrides-template.json
  • assets/override-definitions-template.json
  • assets/parent-keys-template.json

Additional packaged examples are available under assets/examples/ with one folder per bundle/simple-offer sample. The root assets/ folder contains the canonical baseline template set for bundle authoring.

Quick Reference

  • Primary object: Product2 (EPC product and offer records)
  • Attribute data: %vlocity_namespace%__AttributeMetadata__c, %vlocity_namespace%__AttributeDefaultValues__c, and %vlocity_namespace%__AttributeAssignment__c
  • Offer bundle composition: %vlocity_namespace%__ProductChildItem__c
  • Offer marker: %vlocity_namespace%__SpecificationType__c = "Offer" and %vlocity_namespace%__SpecificationSubType__c = "Bundle"
  • Companion bundle artifacts: pricebook entries, price list entries, object field attributes, orchestration scenarios, decomposition relationships, compiled attribute overrides, override definitions, and parent keys

Scoring: 120 points across 6 categories.
Thresholds: >= 95 Deploy-ready | 70-94 Needs review | < 70 Block and fix.

Asset Template Set

Use the root assets/ templates when creating a bundle payload:

  • product2-offer-template.json
  • attribute-assignment-template.json
  • product-child-item-template.json
  • pricebook-entries-template.json
  • price-list-entries-template.json
  • object-field-attributes-template.json
  • orchestration-scenarios-template.json
  • decomposition-relationships-template.json
  • compiled-attribute-overrides-template.json
  • override-definitions-template.json
  • parent-keys-template.json

For additional real-world variants, use the per-example folders under assets/examples/.

Core Responsibilities

  1. Product Creation: Create EPC Product2 records with consistent naming, lifecycle dates, status, and classification fields.
  2. Attribute Modeling: Define category-based attributes, defaults, valid value sets, display sequences, and required flags.
  3. Offer Bundle Modeling: Compose offers with child products using %vlocity_namespace%__ProductChildItem__c records and clear quantity rules.
  4. Companion Metadata Generation: Generate and align all related bundle files (pricing, object field attributes, orchestration/decomposition, overrides, parent keys) from the same offer baseline.
  5. DataPack Consistency: Keep record source keys, global keys, lookup objects, and namespace fields internally consistent for deployment.

Invocation Rules (Mandatory)

Route to this skill whenever the prompt intent matches either of these:

  1. Create a product bundle:

    • User asks to create/build/generate/model an EPC offer bundle.
    • User asks for Product2 offer setup with Product Child Items.
    • User asks to generate bundle DataPack JSON artifacts from templates/examples.

  2. Score or review an existing product bundle:

    • User asks to score/assess/validate/audit an existing EPC bundle.
    • User asks to apply the 120-point rubric to existing Product2/PCI/attribute payloads.
    • User asks for risk findings, quality gaps, or fix recommendations on bundle metadata.

Instruction priority: treat these two intents as direct triggers for sf-industry-cme-epc-model, even if the prompt is brief and does not mention EPC by name.

Workflow (Create/Review)

Phase 1: Identify Catalog Intent

Ask for:

  • Product type: spec product or offer bundle
  • Domain taxonomy: Family, Type/SubType, category path, and channel
  • Attribute requirements: required/optional, picklist values, default values
  • Bundle composition: child products, quantity constraints, optional vs required
  • Target org namespace model: %vlocity_namespace%, vlocity_cmt, or Core
Phase 1A: Clarifying Questions for Complete Bundle (Mandatory)

Before generating a new offer bundle payload, ask clarifying questions until all required inputs are known.

Required clarification checklist:

  1. Offer identity
    • What is the offer name and ProductCode?
    • Is this net-new or an update to an existing Product2 offer?
  2. Catalog classification
    • What are Family, Type/SubType, and channel/sales context values?
    • Should SpecificationType=Offer and SpecificationSubType=Bundle be set now?
  3. Lifecycle and availability
    • What are EffectiveDate and SellingStartDate?
    • Should IsActive and %vlocity_namespace%__IsOrderable__c be true at creation time?
  4. Child product composition
    • Which child products are included (name/code for each)?
    • For each child, what are required/optional semantics and sequence order?
  5. Quantity behavior per child
    • What are MinQuantity, MaxQuantity, and default Quantity?
    • Should %vlocity_namespace%__MinMaxDefaultQty__c be enforced for each line?
  6. Attribute model
    • Which attributes are required vs optional?
    • What are valid values, defaults, display types, and display sequences?
  7. Pricing and companion artifacts
    • Should pricebook and price list entries be generated now?
    • Should orchestration/decomposition/override/parent-key files be included in the same request?
  8. Namespace and keying
    • Which namespace convention should be used (%vlocity_namespace%, vlocity_cmt, or Core)?
    • Are there existing global keys/source keys to preserve?

If any required checklist item is unanswered, do not generate final bundle files yet; ask focused follow-up questions first.

Phase 2: Build Product2 Backbone

For every new EPC record, define:

  • Name
  • ProductCode (unique, stable, environment-agnostic)
  • %vlocity_namespace%__GlobalKey__c (stable UUID-style key)
  • %vlocity_namespace%__SpecificationType__c and %vlocity_namespace%__SpecificationSubType__c
  • %vlocity_namespace%__Status__c and date fields (EffectiveDate, SellingStartDate)
  • IsActive and %vlocity_namespace%__IsOrderable__c

Use assets/product2-offer-template.json as baseline structure.

Phase 3: Add Attributes

When attributes are required:

  1. Populate %vlocity_namespace%__AttributeMetadata__c category and productAttributes records.
  2. Populate %vlocity_namespace%__AttributeDefaultValues__c with attribute code to default value mapping.
  3. Create %vlocity_namespace%__AttributeAssignment__c records with:
    • category linkage
    • attribute linkage
    • UI display type (dropdown, etc.)
    • valid values and default marker

Use assets/attribute-assignment-template.json as the assignment baseline.

Phase 4: Build Offer Bundles

For offers:

  1. Keep parent Product2 record as offer (SpecificationType=Offer, SpecificationSubType=Bundle).
  2. Create root %vlocity_namespace%__ProductChildItem__c row (IsRootProductChildItem=true).
  3. Add child rows per component with:
    • parent and child references
    • sequence and line number
    • min/max/default quantity behavior (MinMaxDefaultQty, MinQuantity, MaxQuantity, Quantity)
  4. Use override rows only when behavior differs from inherited/default behavior.

Use assets/product-child-item-template.json for child relationship structure.

For complete bundle payloads, also align and include:

  • assets/pricebook-entries-template.json
  • assets/price-list-entries-template.json
  • assets/object-field-attributes-template.json
  • assets/orchestration-scenarios-template.json
  • assets/decomposition-relationships-template.json
  • assets/compiled-attribute-overrides-template.json
  • assets/override-definitions-template.json
  • assets/parent-keys-template.json
Show full SKILL.md (559 more words)Show less
Phase 4B: Generate Companion Metadata Files

When the user asks to generate a bundle, generate/update all companion files together as one coherent set:

  1. pricebook-entries-template.json and price-list-entries-template.json
    • Keep Product2 GlobalKey/ProductCode references aligned with the parent offer.
  2. object-field-attributes-template.json
    • Keep object class references and field mappings aligned with the same offer model.
  3. orchestration-scenarios-template.json and decomposition-relationships-template.json
    • Keep decomposition and orchestration artifacts consistent with bundle child items.
  4. compiled-attribute-overrides-template.json and override-definitions-template.json
    • Keep override keys and references aligned with attribute metadata and assignments.
  5. parent-keys-template.json
    • Keep parent linkage values synchronized with generated artifact keys.

Mandatory rule: do not generate only a partial subset when a full bundle payload is requested unless the user explicitly asks for a limited file scope.

Phase 5: Validate and Handoff

Provide a completion block:

text
EPC Model Complete: <Name>
Type: <Spec Product|Offer Bundle>
ProductCode: <code>
Attributes: <count>
Bundle Children: <count>
Companion Metadata Files: <count generated>
Validation Score: <score>/120
Risks: <none|list>

Generation Guardrails (Mandatory)

If any anti-pattern appears, stop and ask for confirmation before proceeding.

Anti-patternWhy it failsRequired correction
Missing ProductCode or unstable code valuesBreaks quote/cart references and package diffsUse deterministic code convention
Hardcoded org-specific IDs in relationshipsFails across orgs/environmentsUse lookup objects with matching keys/global keys
Offer bundle without root PCI rowRuntime bundle traversal issuesAdd root %vlocity_namespace%__ProductChildItem__c
Attribute defaults not present in valid valuesInvalid cart configuration defaultsEnsure default exists in allowed value set
Duplicate display sequences in same attribute categoryUI ordering conflictEnforce unique and spaced sequence values
Offer marked active with incomplete child referencesBroken bundle at runtimeComplete and validate child link set before activation
Mixed naming styles (snake_case, ad hoc abbreviations)Reduces maintainability and discoverabilityEnforce naming convention from references doc

Scoring Model (120 Points)

1) Catalog Identity and Naming (20)
  • Product name clarity and uniqueness
  • ProductCode convention quality
  • Type/SubType/Family coherence
  • Stable keying (GlobalKey, source key integrity)
2) EPC Product Structure (20)
  • Required Product2 + EPC fields present
  • Lifecycle dates and status alignment
  • Orderable/active flags are coherent
  • Record type and classification consistency
3) Attribute Modeling (25)
  • Category and attribute grouping quality
  • Valid values + default alignment
  • Required/read-only/filterable semantics
  • Display sequence and UX consistency
4) Offer Bundle Composition (25)
  • Root PCI presence and correctness
  • Child references and sequencing integrity
  • Quantity constraints correctness
  • Optional/required semantics reflected in min/max/defaults
5) DataPack Integrity (15)
  • Namespace placeholder correctness
  • Lookup object key integrity
  • No environment-specific brittle fields
6) Documentation and Handoff (15)
  • Clear explanation of modeled intent
  • Testing checklist included
  • Risks and assumptions explicitly called out

CLI and Validation Commands

bash
# Query candidate EPC products
sf data query -q "SELECT Id,Name,ProductCode,Family,IsActive FROM Product2 ORDER BY LastModifiedDate DESC" -o <org>

# Query Product Child Items for an offer
sf data query -q "SELECT Id,Name,%vlocity_namespace%__ParentProductName__c,%vlocity_namespace%__ChildProductName__c,%vlocity_namespace%__MinMaxDefaultQty__c FROM %vlocity_namespace%__ProductChildItem__c WHERE %vlocity_namespace%__ParentProductName__c='<Offer Name>'" -o <org>

# Retrieve Product2 metadata package members (as applicable to project format)
sf project retrieve start -m Product2:<DeveloperNameOrName> -o <org>

# Validate deployment in dry-run mode
sf project deploy start -x manifest/package.xml --dry-run -o <org>

Sample Skill Invocation Commands

Use these examples to invoke this skill from your agent/CLI workflow:

bash
# Create a new EPC offer bundle with full companion metadata
cursor-agent "Create a Product2 offer bundle named Business Internet Plus with ProductCode BIZ-INT-PLUS-01, 3 child products, and generate all companion DataPack JSON files from the assets templates."

# Add configurable attributes to an existing EPC Product2 record
cursor-agent "Update Product2 Business Internet Essential with attribute metadata/defaults/assignments for Bandwidth, ContractTerm, and StaticIPCount, including valid values and defaults."

# Build ProductChildItem relationships for an offer
cursor-agent "Create root and child %vlocity_namespace%__ProductChildItem__c records for offer Business Internet Essential VPL with min/max/default quantity rules."

# Review an existing DataPack for EPC modeling quality
cursor-agent "Review the Product2 bundle JSON files under skills/sf-industry-cme-epc-model/examples/business-internet-plus-bundle/, score against the 120-point rubric, and return risks plus required fixes."

# Convert a spec product into a bundle-ready offer payload
cursor-agent "Transform Product2 Dedicated Fiber 1G from spec product to offer bundle (SpecificationType=Offer, SpecificationSubType=Bundle) and generate aligned PCI + pricing artifacts."

If your environment uses a different command wrapper, keep the quoted instruction text and replace cursor-agent with your local agent command.

Cross-Skill Integration

From SkillTo sf-industry-cme-epc-modelWhen
sf-industry-commoncore-omnistudio-analyze-> sf-industry-cme-epc-modelNeed current dependency and namespace inventory first
sf-metadata-> sf-industry-cme-epc-modelNeed object or field readiness before EPC modeling
sf-soql-> sf-industry-cme-epc-modelNeed existing catalog query analysis
From sf-industry-cme-epc-modelTo SkillWhen
sf-industry-cme-epc-model-> sf-industry-commoncore-omniscriptConfigure guided selling UX using the modeled catalog
sf-industry-cme-epc-model-> sf-industry-commoncore-integration-procedureBuild server-side orchestration over product and pricing payloads
sf-industry-cme-epc-model-> sf-deployDeploy validated catalog metadata

External References

Additional local references:

Notes

  • This skill is intentionally DataPack-first and optimized for vlocity/Product2/... artifact authoring.
  • Keep %vlocity_namespace% placeholders intact in templates to preserve portability.
  • Prefer creating reusable spec products first, then assemble offers via child relationships.

License

MIT License.

© 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 73 other files (references, assets) in skills/sf-industry-cme-epc-model of Jaganpro/sf-skills.

  • SKILL.md
  • CREDITS.md
  • LICENSE
  • README.md
  • assets/attribute-assignment-template.json
  • assets/compiled-attribute-overrides-template.json
  • assets/decomposition-relationships-template.json
  • assets/examples/business-internet-premium-fttc-simple-offer/Business-Internet-Premium-FTTC_AttributeAssignments.json
  • assets/examples/business-internet-premium-fttc-simple-offer/Business-Internet-Premium-FTTC_CompiledAttributeOverrides.json
  • assets/examples/business-internet-premium-fttc-simple-offer/Business-Internet-Premium-FTTC_DataPack.json
  • assets/examples/business-internet-premium-fttc-simple-offer/Business-Internet-Premium-FTTC_DecompositionRelationships.json
  • assets/examples/business-internet-premium-fttc-simple-offer/Business-Internet-Premium-FTTC_ObjectFieldAttributes.json
  • assets/examples/business-internet-premium-fttc-simple-offer/Business-Internet-Premium-FTTC_OrchestrationScenarios.json
  • assets/examples/business-internet-premium-fttc-simple-offer/Business-Internet-Premium-FTTC_OverrideDefinitions.json
  • assets/examples/business-internet-premium-fttc-simple-offer/Business-Internet-Premium-FTTC_ParentKeys.json
  • assets/examples/business-internet-premium-fttc-simple-offer/Business-Internet-Premium-FTTC_PriceListEntries.json
  • assets/examples/business-internet-premium-fttc-simple-offer/Business-Internet-Premium-FTTC_PricebookEntries.json
  • assets/examples/business-internet-premium-fttc-simple-offer/Business-Internet-Premium-FTTC_ProductChildItems.json
  • … and 56 more

Open the folder on GitHubat commit 53c9956

Compare with similar skills

Sf Industry Cme Epc Model 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 Cme Epc Model compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sf Industry Cme Epc Model this skillJaganpro/sf-skills424—~4.3kAutomated safety check: PassMIT
Omnistudio Epc Catalog Generateforcedotcom/sf-skills1.1k—~5.5kAutomated safety check: PassApache-2.0
Dx Devops Pipeline Manageforcedotcom/sf-skills1.1k—~4.9kAutomated safety check: PassApache-2.0
Soql Lib Query Builderbeyond-the-cloud-dev/soql-lib154—~4.3kAutomated safety check: PassMIT
Soql Lib Selectorbeyond-the-cloud-dev/soql-lib154—~2kAutomated safety check: PassMIT
Dev SetupPortwood-Global-Solutions/Portwood126—~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • Omnistudio Epc Catalog Generate

    forcedotcom/sf-skills

    Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation.

    1.1k GitHub stars~5.5k tokensUpdated yesterday
    Sales & SupportAuto-check passed

  • Dx Devops Pipeline Manage

    forcedotcom/sf-skills

    A skill your agent uses to manage the full lifecycle of a DevOps Center pipeline — list all pipelines, get a single pipeline's details, create a new pipeline linked to a Git repository, add or…

    1.1k GitHub stars~4.9k tokensUpdated yesterday
    Sales & SupportAuto-check passed

  • Soql Lib Query Builder

    beyond-the-cloud-dev/soql-lib

    Builds Salesforce SOQL queries using the SOQL Lib fluent builder API (SOQL.cls).

    154 GitHub stars~4.3k tokensUpdated 8 days ago
    Sales & SupportAuto-check passed

  • Soql Lib Selector

    beyond-the-cloud-dev/soql-lib

    Creates Salesforce Apex selector classes using the SOQL Lib selector pattern.

    154 GitHub stars~2k tokensUpdated 8 days ago
    Sales & SupportAuto-check passed

  • Dev Setup

    Portwood-Global-Solutions/Portwood

    Get from a fresh clone of Portwood to a working, fully-tested Salesforce org.

    126 GitHub stars~1.1k tokensUpdated yesterday
    Sales & SupportAuto-check passed

  • Automation Sandbox Post Copy Configure

    forcedotcom/sf-skills

    Apply a Salesforce sandbox post-copy automation JSON config against a target org.

    1.1k GitHub stars~5.3k tokensUpdated yesterday
    Sales & SupportAuto-check: notes

More from Jaganpro/sf-skills

All 36 skills in this repo

  • Sf AI Agentforce Observability

    Jaganpro/sf-skills

    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

Works with

Categories

Questions about Sf Industry Cme Epc Model

What does Sf Industry Cme Epc Model do?

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Sf Industry Cme Epc Model is an agent skill from Jaganpro/sf-skills. Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation.

When should I use Sf Industry Cme Epc Model?

Sf Industry Cme Epc Model fits situations like: creating EPC products; configuring product attributes; building offer bundles with Product Child Items; reviewing EPC DataPack JSON metadata for product catalog changes.

How do I install Sf Industry Cme Epc Model in Claude Code?

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

How do I install Sf Industry Cme Epc Model in Codex?

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

Can I use Sf Industry Cme Epc Model 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-cme-epc-model -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-cme-epc-model, .gemini/skills/sf-industry-cme-epc-model, .github/skills/sf-industry-cme-epc-model and .opencode/skills/sf-industry-cme-epc-model in your project.

What does Sf Industry Cme Epc Model need to run?

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

Does Sf Industry Cme Epc Model access the network?

SKILL.md names 1 domain. As links in the text: help.salesforce.com. This is read from the text; nothing was executed.

Is Sf Industry Cme Epc Model 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 Cme Epc Model use?

Sf Industry Cme Epc Model 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 Cme Epc Model use?

About 4.3k tokens (SKILL.md is roughly 17k 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 1.3k tokens, read only when the agent opens those files.

What are the alternatives to Sf Industry Cme Epc Model?

Skills that share tags, products or a category with Sf Industry Cme Epc Model: Omnistudio Epc Catalog Generate (forcedotcom/sf-skills, 1.1k stars), Dx Devops Pipeline Manage (forcedotcom/sf-skills, 1.1k stars), Soql Lib Query Builder (beyond-the-cloud-dev/soql-lib, 154 stars) and Soql Lib Selector (beyond-the-cloud-dev/soql-lib, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sf Industry Cme Epc Model?

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.