jaganpro/sf-skills/sf-industry-commoncore-callable-apex
Claude Code and agent skill by jaganpro/sf-skills
- community
Checking that the SKILL.md file is still in the repository.
Salesforce Industries Common Core (OmniStudio/Vlocity) Apex callable generation and review with 120-point scoring. TRIGGER when: user creates or reviews System.Callable classes, migrates `VlocityOpenInterface` / `VlocityOpenInterface2`, or builds Industries callable extensions used by OmniStudio, Integration Procedures, or DataRaptors. DO NOT TRIGGER when: generic Apex classes/triggers (use sf-apex), building Integration Procedures (use sf-industry-commoncore-integration-procedure), authoring OmniScripts (use sf-industry-commoncore-omniscript), configuring Data Mappers (use sf-industry-commoncore-datamapper), or analyzing namespace/dependency issues (use sf-industry-commoncore-omnistudio-analyze).
Install
npx vskill@latest install jaganpro/sf-skills/sf-industry-commoncore-callable-apexSKILL.md
sf-industry-commoncore-callable-apex: Callable Apex for Salesforce Industries Common Core
Specialist for Salesforce Industries Common Core callable Apex implementations. Produce secure, deterministic, and configurable Apex that cleanly integrates with OmniStudio and Industries extension points.
Core Responsibilities
- Callable Generation: Build
System.Callableclasses with safe action dispatch - Callable Review: Audit existing callable implementations for correctness and risks
- Validation & Scoring: Evaluate against the 120-point rubric
- Industries Fit: Ensure compatibility with OmniStudio/Industries extension points
Workflow (4-Phase Pattern)
Phase 1: Requirements Gathering
Ask for:
- Entry point (OmniScript, Integration Procedure, DataRaptor, or other Industries hook)
- Action names (strings passed into
call) - Input/output contract (required keys, types, and response shape)
- Data access needs (objects/fields, CRUD/FLS rules)
- Side effects (DML, callouts, async requirements)
Then:
- Scan for existing callable classes:
Glob: **/*Callable*.cls - Identify shared utilities or base classes used for Industries extensions
- Create a task list
Phase 2: Design & Contract Definition
Define the callable contract:
- Action list (explicit, versioned strings)
- Input schema (required keys + types)
- Output schema (consistent response envelope)
Recommended response envelope:
Action dispatch rules:
- Use
switch on action - Default case throws a typed exception
- No dynamic method invocation or reflection
VlocityOpenInterface / VlocityOpenInterface2 contract mapping:
When designing for legacy Open Interface extensions (or dual Callable + Open Interface support), map the signature:
| Parameter | Role | Callable equivalent | |
|---|---|---|---|
methodName | Action selector (same semantics as action) | action in call(action, args) | |
inputMap | Primary input data (required keys, types) | args.get('inputMap') | |
outputMap | Mutable map where results are written (out-by-reference) | Return value; Callable returns envelope instead | |
options | Additional context (parent DataRaptor/OmniScript context, invocation metadata) | args.get('options') |
Design rules for Open Interface contracts:
- Treat
inputMapandoptionsas the combined input schema - Define what keys must be written to
outputMapper action (success and error cases) - Preserve
methodNamestrings so they align with Callableactionstrings - Document whether
optionsis required, optional, or unused for each action
Phase 3: Implementation Pattern
Vanilla System.Callable (flat args, no Open Interface coupling):
Use the vanilla pattern when callers pass flat args and no VlocityOpenInterface integration is required.
Callable skeleton (same inputs as VlocityOpenInterface):
Use inputMap and options keys in args when integrating with Open Interface or when callers pass that structure:
Input format: Callers pass args as { 'inputMap' => Map<String, Object>, 'options' => Map<String, Object> }. For backward compatibility with flat callers, if args lacks 'inputMap', treat args itself as inputMap and use an empty map for options.
Implementation rules:
- Keep
call()thin; delegate to private methods or service classes - Validate and coerce input types early (null-safe)
- Enforce CRUD/FLS and sharing (
with sharing,Security.stripInaccessible()) - Bulkify when args include record collections
- Use
WITH USER_MODEfor SOQL when appropriate
VlocityOpenInterface / VlocityOpenInterface2 implementation:
When implementing omnistudio.VlocityOpenInterface or omnistudio.VlocityOpenInterface2, use the signature:
Open Interface skeleton:
Open Interface implementation rules:
- Write results into
outputMapviaputAll()or individualput()calls; do not return the envelope frominvokeMethod - Return
truefor success,falsefor unsupported or failed actions - Use the same internal private methods as the Callable (same
inputMapandoptionsparameters); only the entry point differs - Populate
outputMapwith the same envelope shape (success,data,errors) for consistency
Both Callable and Open Interface accept the same inputs (inputMap, options) and delegate to identical private method signatures for shared logic.
Phase 4: Testing & Validation
Minimum tests:
- Positive: Supported action executes successfully
- Negative: Unsupported action throws expected exception
- Contract: Missing/invalid inputs return error envelope
- Bulk: Handles list inputs without hitting limits
Example test class:
Migration: VlocityOpenInterface to System.Callable
When modernizing Industries extensions, move VlocityOpenInterface or VlocityOpenInterface2 implementations to System.Callable and keep the action contract stable. Use the Salesforce guidance as the source of truth. Salesforce Help
Guidance:
- Preserve action names (
methodName) asactionstrings incall() - Pass
inputMapandoptionsas keys inargs:{ 'inputMap' => inputMap, 'options' => options } - Return a consistent response envelope instead of mutating
outMap - Keep
call()thin; delegate to the same internal methods with(inputMap, options)signature - Add tests for each action and unsupported action
Example migration (pattern):
Best Practices (120-Point Scoring)
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/sf-industry-commoncore-callable-apex/SKILL.md
Popularity
- Repository stars
- 401
- Repository forks
- 88
- 7-day trend score
- 30
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 29 Apr 2026, 6 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/jaganpro/sf-skills/sf-industry-commoncore-callable-apex)