forcedotcom/afv-library
107 skills61.1k installs81.6k starsGitHub
Install
npx skills add https://github.com/forcedotcom/afv-librarySkills in this repo
1Generating Apexgenerating-apex is an AFV Library skill from forcedotcom that scaffolds Salesforce Apex following a consistent abstract-base-class pattern. Generated classes define common behavior, extension points, and abstract methods subclasses must implement for specific integrations. Templates include Javadoc-style descriptions, usage examples, and callout configuration such as named credential endpoints like callout:Salesforce_API/services/data/v62.0 plus override hooks for getEndpoint and getHeaders. Developers reach for generating-apex when standing up new Salesforce integration services or backend families that should share structure instead of one-off Apex copies.1.6kinstalls2Generating Apex Testgenerating-apex-test is a Claude Code skill from forcedotcom/afv-library that scaffolds Apex test classes matching Salesforce deployment requirements. Generated tests include @TestSetup with TestDataFactory data, bulk operations using 251 or more records, positive and negative method paths, and exception-handling cases with Test.startTest and Test.stopTest boundaries. The template follows Given-When-Then structure and names methods like shouldPerformExpectedBehavior_WhenValidInput. Salesforce developers reach for generating-apex-test when adding coverage for new Apex classes, satisfying bulkification rules, or replacing hand-written test boilerplate before CI validation or org promotion.1.6kinstalls3Generating Flowgenerating-flow is a Salesforce Flow generation skill (manifest version 1.0) from forcedotcom/afv-library that drives a required three-step MCP pipeline: fetchGroundedObjectMetadata, flowElementSelection, and flowElementGeneration. It is the dedicated skill when requests mention creating flows, record-triggered before/after-save logic, daily schedules, field updates on create, or workflow-style automation phrasing. Developers reach for generating-flow instead of writing Flow XML by hand or guessing element shapes. It covers Screen, Autolaunched, Record-Triggered, and Scheduled flow types through execute_metadata_action.1.6kinstalls4Generating Custom Fieldgenerating-custom-field from forcedotcom/afv-library (version 1.0) creates and validates Salesforce Custom Field metadata XML across standard and custom objects. The skill handles roll-up summary fields, master-detail relationships, lookup relationships, formula fields, picklists, and general custom field types. Developers invoke it when creating new fields, troubleshooting deployment errors around roll-up summary format or master-detail constraints, or validating field metadata before pushing to an org. It is the designated skill for any custom field generation or field troubleshooting work in agentic Salesforce workflows.1.6kinstalls5Generating Custom Objectgenerating-custom-object is version 1.0 skill from forcedotcom/afv-library for creating, generating, and validating Salesforce Custom Object metadata. Agents produce accurate .object XML covering sharing models, name fields, Master-Detail relationships, and object-level validation rules that deploy through Metadata API or SFDX without common deployment failures. The skill triggers on phrases like "create a custom object," ".object files," or troubleshooting sharing-model and Master-Detail errors. Developers reach for generating-custom-object when bootstrapping new Salesforce data models, fixing object deployment errors, or scaffolding objects before Apex triggers and Lightning pages.1.6kinstalls6Generating Permission Setgenerating-permission-set is a forcedotcom afv-library skill at version 1.0 that writes correct, deployable Salesforce PermissionSet XML for object permissions, field-level security, tab visibility, and user access controls. The skill walks through core PermissionSet properties, FLS entries, and app permission blocks compatible with Salesforce Metadata API v60.0+. Developers reach for generating-permission-set when creating new permission sets, editing FLS for custom objects, or fixing deployment errors in permission metadata instead of hand-editing fragile XML. Output is ready for Salesforce CLI or Metadata API deploy commands.1.6kinstalls7Generating Flexipagegenerating-flexipage is a forcedotcom afv-library skill at version 1.0 for creating, modifying, and validating Salesforce Lightning FlexiPages. The skill covers RecordPage, AppPage, and HomePage types, component regions, page customization, and deployment error fixes when working with FlexiPage XML. Developers reach for generating-flexipage when adding components to record pages, generating new Lightning pages, or troubleshooting FlexiPage metadata from Salesforce CLI deploys. It triggers on any Salesforce page work—including phrases like customize the record page or generate a FlexiPage—and enforces correct component and region structures.1.6kinstalls8Developing AgentforceDeveloping-agentforce is a forcedotcom/afv-library skill for authoring Agentforce agent specs ready for implementation on Salesforce. Specs define purpose and scope, behavioral intent with guardrails and escalation rules, and a subagent map diagram routing from a start_agent router to specialized subagents including ambiguous-question handling. Backing logic types cover Apex, Flow, and Prompt Template with rules for what the agent must know before acting and what persists across subagent switches. Developers reach for this skill when scaffolding enterprise Agentforce agents instead of ad-hoc prompt drafts without routing or logic mappings.1.5kinstalls9Generating Custom TabGenerating Custom Tab is a Salesforce agent skill (version 1.0) that creates and configures Custom Tab metadata when building or extending Salesforce applications. The skill triggers on mentions of tabs, navigation tabs, object tabs, web tabs, Visualforce tabs, Lightning component tabs, app page tabs, or tab visibility and access settings. Developers reach for Generating Custom Tab to add navigation for custom objects, external web content, Visualforce pages, or Lightning pages without hand-authoring error-prone tab XML. Output covers tab creation, application navigation wiring, visibility configuration, and deployment troubleshooting guidance. Always use this skill for any custom tab work on Lightning Platform.1.5kinstalls10Generating Custom Lightning TypeGenerating Custom Lightning Type is a Salesforce-focused agent skill (version 1.0) that generates Custom Lightning Types (CLTs) for Einstein Agent actions and structured input/output schemas on the Lightning Platform. The skill triggers on mentions of CLT, Custom Lightning Types, JSON schemas for agents, lightning__objectType, or editor/renderer configurations. Developers reach for Generating Custom Lightning Type whenever CLT work is required because the metadata is complex and error-prone without guided generation. Output includes JSON Schema-based type definitions, editor configurations, and renderer setups aligned to Salesforce agent action contracts. Always use this skill for CLT work rather than improvising schema metadata.1.5kinstalls11Generating Lightning AppGenerating Lightning App is a Salesforce agent skill (version 1.0) that builds complete Lightning Experience applications from natural language descriptions of business solutions or management systems. The skill orchestrates interconnected metadata—custom objects, fields, tabs, FlexiPages, custom applications, flows, and security—in proper dependency order to produce a deployable app. Developers reach for Generating Lightning App when a request describes multiple Salesforce components rather than a single metadata type. Related skills include generating-custom-object, generating-custom-field, generating-custom-tab, generating-flexipage, generating-custom-application, generating-flow, and generating-validation. Trigger phrases include "complete app", "Lightning app", "business solution", and "management system".1.5kinstalls12Generating Custom ApplicationGenerating Custom Application is a Salesforce agent skill (version 1.0) that creates and configures tab-based Custom Applications with navigation, branding, and action overrides on Lightning Platform. The skill triggers when users mention custom apps, application metadata, app navigation, or organizing tabs into applications. Developers reach for Generating Custom Application to create focused app containers that group tabs and Lightning pages—distinct from React UI bundle apps in the App Launcher, which require generating-ui-bundle-custom-app instead. Output includes Lightning application metadata with tab organization, branding settings, and action override configuration ready for deployment.1.5kinstalls13Generating List Viewgenerating-list-view is an agent skill (version 1.0) from the Salesforce AFV library for creating and validating Salesforce List View metadata. The skill triggers when developers need filtered record lists, column configuration, visibility settings, or troubleshooting of ListView XML files. Developers reach for generating-list-view when creating object list views, setting filter criteria, defining record columns, or fixing list view deployment errors. The skill handles ListView metadata generation and validation—not general Apex, LWC, or unrelated Salesforce configuration.1.5kinstalls14Generating Validation Rulegenerating-validation-rule is an official Salesforce AFV-library agent skill for creating, modifying, and troubleshooting Salesforce Validation Rules that block invalid records at save time. Version 1.0 triggers on validation rules, field validation, formula logic, error messages, and data-quality enforcement requests. The skill generates validation rule metadata with correct formula syntax, helps update rules when business logic changes, and diagnoses validation errors users hit in production orgs. Salesforce developers reach for generating-validation-rule instead of hand-writing XML or fumbling formula editor edge cases when Apex triggers would be heavier than necessary. Use it whenever records must be rejected at the data layer—required field combinations, cross-field constraints, or stage-gated updates—before flows or UI validation alone suffice.1.5kinstalls15Building Ui Bundle Frontendbuilding-ui-bundle-frontend is a Claude Code skill from forcedotcom/afv-library for implementing UI bundle frontend components. It mandates shadcn components from `@/components/ui` for buttons, inputs, cards, alerts, tabs, tables, and labels—never raw HTML equivalents. All styling uses Tailwind utility classes and design tokens like `bg-background`, `text-foreground`, and `text-muted-foreground`; conditional classes use `cn()` from `@/lib/utils`. Components are TypeScript functional modules with typed props and optional `className`. Use building-ui-bundle-frontend when generating AFV UI that must match the design system on first pass.1.5kinstalls16Observing Agentforceobserving-agentforce is a Claude Code skill from forcedotcom/afv-library for querying the Session Trace Data Model (STDM) in Salesforce Data Cloud. Public methods include `findSessions` with date range, max rows, and optional agent name filter, plus `getConversationDetails` for conversation turns, messages, and steps. The STDM query service accepts `dataSpaceName` so no Data Space is hardcoded and is deployed once per org by the agentforce-optimize skill. Use observing-agentforce when analyzing Agentforce session failures, latency, or conversation quality from production trace data.1.5kinstalls17Testing Agentforcetesting-agentforce is a skill from forcedotcom/afv-library providing YAML test specification templates compatible with Salesforce Agentforce CLI commands. Specs are parsed by @salesforce/agents—not generic AiEvaluationDefinition—and recognize only documented fields without apiVersion, kind, metadata, or settings blocks. Developers create tests with sf agent test create --spec <file> --api-name <name> and run them via sf agent test run --api-name <Test_Name> --wait 10 --result-format json. The skill maps Testing Center topic terminology to Agent Script subagents. Teams reach for testing-agentforce when automating validation of custom Agentforce agents before deployment to Salesforce orgs.1.5kinstalls18Using Ui Bundle Salesforce Datausing-ui-bundle-salesforce-data is a skill from forcedotcom/afv-library centered on graphql-search.sh, a bash script run from an SFDX project root where schema.graphql lives. Pass one or more entity names—Account, Contact, Opportunity—or a custom schema path with -s/--schema to print per-entity sections: type definitions with fields and relationships, filter options, sort options, and mutation shapes. Developers reach for using-ui-bundle-salesforce-data when scaffolding GraphQL queries or mutations for Salesforce UI bundle React apps without manually paging through a large schema file. The script uses strict bash flags (-euo pipefail) and supports multi-entity lookups in one invocation.1.5kinstalls19Building Ui Bundle Appbuilding-ui-bundle-app is the top-level orchestrator skill from forcedotcom/afv-library for Salesforce React UI bundle applications. It must activate when a user wants to build, create, or generate a React app, SPA, or frontend—even with no existing files—or when the project contains uiBundles/*/src/ or sfdx-project.json and the prompt asks to construct a new app, site, or page from scratch. The skill coordinates scaffolding, features, data access, and sibling ui-bundle skills when a task spans more than one capability. Developers reach for building-ui-bundle-app for end-to-end UI bundle delivery from a natural language description rather than invoking individual feature skills piecemeal. Output is a deployable React UI bundle wired to Salesforce.1.5kinstalls20Generating Ui Bundle Featuresgenerating-ui-bundle-features is version 1.0 skill from forcedotcom/afv-library that adds exactly two pre-built capabilities to Salesforce UI bundle apps: authentication (login, logout, protected routes, session management) and global search across pages and content. It must activate when uiBundles/*/src/ exists and the user wants auth or search, always preferring the features CLI over custom implementations. Developers reach for generating-ui-bundle-features when extending an existing UI bundle rather than scaffolding a full app—pair with building-ui-bundle-app for greenfield work. The CLI installs tested packages into the bundle source tree, delivering production-ready routes and session handling without manual boilerplate.1.5kinstalls21Generating Ui Bundle Metadatagenerating-ui-bundle-metadata automates creation of Salesforce Content Security Policy Trusted Site metadata files at force-app/main/default/cspTrustedSites/{Name}.cspTrustedSite-meta.xml. The skill enforces naming conventions where file names match the fullName element—for example Unsplash_Images.cspTrustedSite-meta.xml for https://images.unsplash.com. Developers reach for generating-ui-bundle-metadata when LWC or Aura components fetch external APIs or images and CSP blocks those requests at deploy time. The skill covers directory placement, fullName-to-filename mapping, and domain-specific metadata patterns for common integrations like Open-Meteo and OpenStreetMap tiles.1.5kinstalls22Deploying Ui Bundledeploying-ui-bundle is a forcedotcom/afv-library agent skill (metadata version 1.0) that enforces the correct order of operations when shipping a UI bundle app to a Salesforce org. It activates when uiBundles/*/src/, *.uibundle-meta.xml, or sfdx-project.json exist and the task involves deploying, pushing, or post-deploy setup. The workflow spans org authentication, pre-deploy build, metadata deployment, permission set assignment, data import, GraphQL schema fetch, and codegen. Developers reach for deploying-ui-bundle when a UI bundle push fails from skipped steps or when onboarding a fresh org requires the full post-deploy chain. Output is a deployed org with permissions, imported data, and generated client code aligned to the fetched Graphically.1.5kinstalls23Switching Orgswitching-org is a forcedotcom/afv-library agent skill at metadata version 1.0 compatible with Salesforce CLI (sf) v2 2 and above. It sets the default target-org when developers say switch org, change default org, set my org to, use alias, or point to a specific org. The workflow identifies an orgIdentifier username or alias—or runs sf org list when none is provided—then executes sf config set target-org. Developers and coding agents reach for switching-org before deploy, retrieve, or test commands that depend on a specific Salesforce org context. Output is an updated local default org configuration so subsequent CLI operations target the intended environment.1.5kinstalls24Searching Mediasearching-media is a Claude Code skill from forcedotcom/afv-library that must activate before any media search or retrieval request involving images, logos, icons, photos, graphics, banners, thumbnails, hero images, or backgrounds. It searches Salesforce CMS, Data 360, and other configured sources while explicitly blocking direct calls to search_media_cms_channels or search_electronic_media tools—agents go through this skill first without exception. The skill takes priority whenever find, fetch, retrieve, grab, look up, or locate media appears in user intent. Developers on Salesforce-centric stacks use it to standardize asset discovery and avoid bypassing governed CMS channels during agent-assisted UI or marketing builds.1.5kinstalls25Generating Ui Bundle Sitegenerating-ui-bundle-site is a forcedotcom/afv-library template skill that produces a net-new CustomSite metadata record for Salesforce Digital Experience React sites. It writes sites/{siteName}.site-meta.xml with defaulted SOAP metadata fields—active site flag, guest payment API toggles, standard page permissions, and related CustomSite properties—intended only for initial provisioning, not editing existing sites. Developers reach for generating-ui-bundle-site when standing up a fresh Experience Cloud React site and need deployable Metadata API XML aligned with AFV library conventions before connecting UI bundles and community routes.1.5kinstalls26Uplifting Components To Slds2uplifting-components-to-slds2 is a Salesforce AFV Library skill for SLDS 2 color hook decisions when uplifting Lightning components. It requires inspecting markup in LWC .html or Aura .cmp files, then JavaScript for dynamic class insertion via classList.add or template literals, because CSS alone cannot determine the correct semantic hook. Developers reach for uplifting-components-to-slds2 when replacing hardcoded colors or resolving linter suggestions among multiple SLDS 2 hook options. The decision guide preserves theme compatibility and accessibility by matching element context—parent containers, nesting depth, ARIA attributes, and interactive roles—to the proper semantic color token.1.5kinstalls27Implementing Ui Bundle File Uploadimplementing-ui-bundle-file-upload is a version 1.0 workflow skill from forcedotcom/afv-library for Salesforce UI bundle React applications. It must activate when a project contains uiBundles/*/src/ and the task involves uploading, attaching, or dropping files. The skill provides programmatic upload() APIs with progress tracking and Salesforce ContentVersion integration only—developers build custom UI atop the API rather than using prebuilt widgets. It explicitly replaces hand-rolled FormData or XHR upload code. Follow the workflow when adding drag-drop or attachment flows to Lightning UI bundle apps while keeping Salesforce content storage compliance.1.5kinstalls28Implementing Ui Bundle Agentforce Conversation Clientimplementing-ui-bundle-agentforce-conversation-client is a forcedotcom afv-library skill that shows how to correctly resolve Agentforce Employee Agent IDs and wire them into React using AgentforceConversationClient. The skill documents an sf data query against BotVersion filtered on AgentType = 'AgentforceEmployeeAgent', returning BotDefinition.Id, DeveloperName, MasterLabel, and Status because Status lives on BotVersion rather than BotDefinition. Developers reach for this skill when building custom React UIs that must connect to active Employee Agents while excluding Service Agents. The workflow covers JSON response parsing and UI bundle integration patterns so agent IDs are resolved before client initialization.1.5kinstalls29Creating B2b Commerce StoreCreating B2B Commerce Store is a forcedotcom AFV Library skill explaining the critical distinction between Commerce Store (backend runtime data) and Storefront (customer-facing layer) in Salesforce B2B Commerce development. The Commerce Store includes store configuration, default buyer groups, entitlement policies, and pricing policies created through the Commerce app UI as non-source-controllable org data. Developers must create the Commerce Store backend before the Storefront because storefront components depend on store configuration, buyer groups, and entitlements. Engineers reach for this skill when starting Salesforce B2B Commerce projects or debugging missing product visibility and pricing issues.1.4kinstalls30Generating Lwc Componentsgenerating-lwc-components is a forcedotcom afv-library skill at version 1.1 that guides Lightning Web Components development using the PICKLES methodology and a 165-point quality scoring system. The skill triggers when developers create or edit files under lwc/**/*.js, .html, .css, or .js-meta.xml, or ask about wire service patterns, SLDS styling, Apex and GraphQL integration, and Jest LWC tests. It explicitly excludes Apex-only, Aura, and Visualforce work. Developers reach for generating-lwc-components when building Salesforce UI features that need platform best practices baked into component structure, data wiring, and test coverage. The scoring rubric gives concrete quality checkpoints beyond generic React-style component advice.541installs31Developing Datacloud Code Extensiondeveloping-datacloud-code-extension (metadata version 1.0) from forcedotcom/afv-library provides an end-to-end workflow for Salesforce Data Cloud Python code extensions. Extensions read from and write to Data Lake Objects (DLOs) and Data Model Objects (DMOs) inside custom transformation pipelines. The skill supports four SF CLI plugin operations: init, run, scan, and deploy for local testing and promotion. Developers use it when creating custom Python transformations, deploying code extensions, or validating data transforms before production Data Cloud releases. The workflow assumes Salesforce CLI tooling and Data Cloud familiarity rather than generic ETL scripting alone.539installs32Getting Datacloud Schemagetting-datacloud-schema is a Salesforce integration skill (version 1.0) from forcedotcom/afv-library that queries Data Cloud SSOT REST APIs to list all Data Lake Objects (DLOs) or Data Model Objects (DMOs) in an org, or return detailed field definitions, data types, and metadata for a named object. Developers pass an org alias and optional DLO/DMO name as parameters. Teams reach for getting-datacloud-schema when building Data Cloud integrations, writing SOQL or ingestion mappings, or debugging field-level schema mismatches during agent-assisted development. The skill keeps schema inspection inside the coding agent instead of switching to Salesforce Setup.536installs33Deploying Metadatadeploying-metadata is a version 1.1 skill from forcedotcom/afv-library that automates Salesforce DevOps with the sf CLI v2. The skill handles deployment orchestration including dry-run validation via sf project deploy, targeted org deployments, scratch org and sandbox lifecycle management, and CI/CD pipeline setup. It explicitly avoids Apex authoring, LWC generation, and SOQL queries, directing those to sibling afv-library skills. Developers reach for deploying-metadata when metadata pushes fail, scratch orgs need provisioning, or release pipelines require validated sf CLI deployment steps.534installs34Handling Sf Datahandling-sf-data is version 1.1 of the afv-library Salesforce Data Operations Expert skill. It guides create, update, delete, bulk import and export, synthetic test-data generation, and org cleanup workflows through sf CLI commands and anonymous Apex scripts, returning a 130-point scoring assessment of data-operation quality. Triggers include seeding sandboxes, bulk CSV loads, data-factory patterns for Apex tests, and sf data CLI usage. The skill excludes SOQL-only query writing (querying-soql), Apex test runs (running-apex-tests), and metadata deployment (deploying-metadata). Developers reach for handling-sf-data when org records—not code packages—need programmatic manipulation at scale during feature development and QA preparation.532installs35Generating Mermaid Diagramsgenerating-mermaid-diagrams is version 1.0 of the afv-library skill for text-based Salesforce visual documentation. It generates Mermaid flowcharts, sequence diagrams, class diagrams, and ERDs covering OAuth flows, integration sequences, data models, and Agentforce structures, with ASCII fallbacks when renderers lack Mermaid support. Triggers include requests to diagram, visualize, or draft ERD and sequence views inside Salesforce projects. The skill requires a Mermaid-capable preview environment for live rendering but ships portable source text. Developers choose it over generating-visual-diagrams when they need editable markdown diagrams rather than Nano Banana Pro PNG or SVG mockups for slides and stakeholder decks.531installs36Generating Visual Diagramsgenerating-visual-diagrams is version 1.0 of the afv-library skill for AI-rendered Salesforce visuals. It invokes Nano Banana Pro to generate high-quality PNG and SVG outputs—UI mockups, wireframes, visual ERDs, and architecture illustrations—when stakeholders need presentation-ready graphics instead of markdown diagram source. Triggers include explicit requests for PNG or SVG, mockups, wireframes, visual ERDs, or phrases like generate image and create mockup within Salesforce contexts. The skill excludes text-based Mermaid workflows handled by generating-mermaid-diagrams. Developers reach for generating-visual-diagrams when decks, reviews, or design critiques require polished raster or vector assets rather than editable diagram code.531installs37Configuring Connected Appsconfiguring-connected-apps is a skill from forcedotcom/afv-library for Salesforce Connected Apps and External Client Apps OAuth configuration with a 120-point scoring model. It triggers when developers configure OAuth flows, JWT bearer authentication, Connected Apps, or External Client Apps and when editing .connectedApp-meta.xml or .eca-meta.xml metadata files. The skill covers scope selection, callback URLs, certificate settings, and security policies while steering users away from Named Credential callouts or Apex token code covered by sibling AFV skills. Developers reach for configuring-connected-apps when standing up Salesforce as an identity provider for external applications.526installs38Building Sf Integrationsbuilding-sf-integrations is a forcedotcom/afv-library Claude Code skill for Salesforce integration architecture and runtime plumbing with a 120-point scoring rubric. The skill covers Named Credentials, External Credentials, External Services, REST and SOAP callout patterns, Platform Events, and Change Data Capture, and triggers when developers touch .namedCredential-meta.xml or set up CDC channels. It explicitly excludes Connected App OAuth configuration, Apex-only logic, standard CRM data import, and PlatformEventChannel membership metadata that belongs in sibling AFV skills. Developers reach for building-sf-integrations when standing up secure outbound callouts, event-driven integrations, or CDC subscriptions in a Salesforce org. The scoring model gives agents a concrete checklist instead of ad hoc integration advice, reducing misconfigured credentials and unsafe callout patterns in enterprise orgs.523installs39Retrieving Datacloudretrieving-datacloud is a forcedotcom/afv-library skill for the Salesforce Data Cloud Retrieve phase. It guides agents through Data Cloud SQL, describe operations, async queries, vector search, search-index workflows, and metadata introspection using the community sf data360 CLI plugin in a Data Cloud-enabled org. The skill triggers when developers run Data Cloud queries or inspect Data Cloud object metadata, and it explicitly defers standard CRM SOQL to querying-soql, segment creation to segmenting-datacloud, and STDM or parquet tracing to observing-agentforce. Developers reach for retrieving-datacloud when building retrieval pipelines, debugging Data Cloud SQL, or exploring search-index configuration during Agentforce or analytics integrations. The CLI-first workflow keeps agents on supported Data Cloud interfaces instead of guessing REST endpoints or mixing CRM and Data Cloud query languages.523installs40Harmonizing Datacloudharmonizing-datacloud is a skill from forcedotcom/afv-library for the Salesforce Data Cloud Harmonize phase. It assists developers working with Data Model Objects (DMOs), field mappings, relationships, identity resolution rules, unified profiles, data graphs, and universal IDs. The skill requires an external community sf data360 CLI plugin and a Data Cloud-enabled Salesforce org. Developers reach for harmonizing-datacloud when harmonizing customer data—not when tasks are limited to streams/DLOs, segments, insights, retrieval search, or STDM session tracing covered by sibling skills. It targets build-stage integration work for enterprise data unification on Salesforce Data Cloud.520installs41Connecting Datacloudconnecting-datacloud is the Connect phase skill in forcedotcom/afv-library for Salesforce Data Cloud integration. It guides agents through sf data360 CLI workflows to create and test source connections, inspect connector metadata, browse source objects or databases, and stage ingestion payloads before harmonization or streaming steps. The skill requires the sf data360 CLI plugin and a Data Cloud-enabled Salesforce org, and it explicitly defers data streams and DLO work to preparing-datacloud, DMO and identity resolution to harmonizing-datacloud, retrieval to retrieving-datacloud, and STDM telemetry to observing-agentforce. Developers reach for connecting-datacloud when wiring CRM, warehouse, or SaaS sources into Data Cloud and validating connector health before downstream mapping, identity resolution, or agent retrieval pipelines run.519installs42Orchestrating DatacloudOrchestrating Data Cloud is the product orchestrator skill in forcedotcom/afv-library for Salesforce Data Cloud. It walks developers through connect→prepare→harmonize→segment→act pipelines, cross-phase troubleshooting, and data space and data kit management using sf data360 workflows. Use Orchestrating Data Cloud when a task spans multiple Data Cloud phases rather than a single ingestion, mapping, or segment step. The skill defers isolated phase work to matching phase-specific skills and excludes STDM session tracing, standard CRM SOQL, and Apex-only tasks. It targets integrators building end-to-end customer data platforms inside Data Cloud-enabled orgs.519installs43Preparing DatacloudPreparing Data Cloud is the Prepare-phase skill in forcedotcom/afv-library for Salesforce Data Cloud, version 1.0. It guides creation and management of data streams, data lake objects (DLOs), transforms, and Document AI configurations that ingest source data into Data Cloud. Developers reach for Preparing Data Cloud when wiring ingestion pipelines, not when setting up connections only, harmonizing DMOs, or running segment SQL. The skill requires an external community sf data360 CLI plugin and a Data Cloud-enabled org. It pairs with connecting-datacloud for connection setup and harmonizing-datacloud for identity resolution work downstream.519installs44Segmenting DatacloudSegmenting Data Cloud is the Segment-phase skill in forcedotcom/afv-library for Salesforce Data Cloud. It guides creation and publishing of audience segments, calculated insights management, segment count inspection, and natural-language-assisted audience SQL troubleshooting. Developers use Segmenting Data Cloud when building audiences inside Data Cloud, not for DMO mapping, activation exports, or search-index retrieval tasks. The skill requires the external community sf data360 CLI plugin and a Data Cloud-enabled org. It complements harmonizing-datacloud for identity work and activating-datacloud for downstream activation while keeping segment SQL and publish workflows in one focused skill.518installs45Building Omnistudio Flexcardbuilding-omnistudio-flexcard is a Salesforce OmniStudio agent skill (version 1.0) for creating and reviewing FlexCard definitions. The skill configures data source bindings to Integration Procedures, designs card layouts, and scores existing OmniUiCard metadata against a 130-point rubric covering accessibility and performance. Developers reach for it when building new FlexCards, wiring data sources, or auditing card definitions before deployment. Use building-omnistudio-omniscript for OmniScripts and building-omnistudio-integration-procedure for Integration Procedures instead.511installs46Analyzing Omnistudio Dependenciesanalyzing-omnistudio-dependencies is a Salesforce OmniStudio analysis skill from forcedotcom/afv-library for namespace detection, dependency visualization, and change impact analysis. The skill auto-detects Core, vlocity_cmt, and vlocity_ins namespaces, then maps relationships across OmniScripts, FlexCards, Integration Procedures, and Data Mappers before edits land in production orgs. Developers invoke it when they need Mermaid dependency graphs or impact reports showing which components a change will affect. The skill complements authoring skills for individual OmniStudio artifacts by focusing on cross-cutting dependency tracing rather than building new OmniScripts or FlexCards from scratch.510installs47Building Omnistudio Callable Apexbuilding-omnistudio-callable-apex is a Salesforce Industries Common Core skill for creating, reviewing, and migrating System.Callable Apex used by OmniStudio, Integration Procedures, and DataRaptors. It applies a 120-point scoring rubric when generating or reviewing callable implementations and handles migration from VlocityOpenInterface and VlocityOpenInterface2 patterns. Developers reach for building-omnistudio-callable-apex when building Industries callable extensions that must integrate cleanly with OmniStudio orchestration rather than writing generic Apex triggers or classes.509installs48Building Omnistudio Integration Procedurebuilding-omnistudio-integration-procedure is an OmniStudio skill for building server-side Integration Procedures that combine Data Mapper actions, Apex Remote Actions, HTTP callouts, and conditional logic. It applies a 110-point scoring rubric when creating or reviewing IP configurations and explicitly defers OmniScript authoring and standalone Data Mapper work to sibling skills. Developers reach for building-omnistudio-integration-procedure when orchestrating multi-step backend processes in Salesforce Industries that must call external APIs and Apex callables within one Integration Procedure.509installs49Deploying Omnistudio Datapacksdeploying-omnistudio-datapacks is a Salesforce Industries agent skill (version 1.0) from forcedotcom/afv-library that guides Vlocity Build DataPack workflows end to end. The skill fires when developers run packDeploy, packRetry, packExport, or packGetDiffs, set up DataPack CI/CD pipelines, or debug migration failures. It separates OmniStudio DataPack automation from metadata deploys via sf project deploy and from authoring OmniScripts, FlexCards, or Integration Procedures. Developers reach for deploying-omnistudio-datapacks when Industries assets must export cleanly, deploy with retries, diff before promotion, and pass validation gates without manual CLI guesswork. The skill encodes trigger boundaries so agents route Apex/LWC work and metadata deploys to sibling afv-library skills instead.509installs50Modeling Omnistudio Epc Catalogmodeling-omnistudio-epc-catalog is a forcedotcom/afv-library agent skill for Salesforce Industries Communications Media and Energy EPC catalog work. The skill guides Product2-based product creation, attribute configuration through AttributeAssignment and AttributeMetadata payloads, AttributeDefaultValues, and offer bundles wired with ProductChildItem relationships. Developers reach for modeling-omnistudio-epc-catalog when reviewing EPC DataPack JSON for catalog changes or updating product metadata without touching OmniScript, FlexCard, or Integration Procedure authoring. Trigger boundaries route UI composition to building-omnistudio-omniscript, building-omnistudio-flexcard, and building-omnistudio-integration-procedure skills. The skill keeps catalog schema changes consistent with Industries EPC conventions so downstream OmniStudio assets bind to correct product definitions.509installs51Building Omnistudio Omniscriptbuilding-omnistudio-omniscript is a forcedotcom/afv-library skill (version 1.0) for Salesforce OmniStudio OmniScript creation, step-flow design, element configuration, and validation with a 120-point scoring rubric. The skill triggers when developers build guided forms, interactive processes, or experiences that orchestrate Integration Procedures and Data Mappers, and it explicitly defers FlexCard or standalone Integration Procedure work to sibling skills. Reach for building-omnistudio-omniscript when designing multi-step OmniScripts, reviewing element types, or validating existing OmniScript configurations in Salesforce orgs.508installs52Building Omnistudio Datamapperbuilding-omnistudio-datamapper is a skill in forcedotcom/afv-library for OmniStudio Data Mapper creation and validation with 100-point scoring across five categories: Design and Naming (20), Field Mapping (25), Data Integrity (25), Performance (15), and Documentation (15). It follows a five-phase workflow from requirements through design, generation, validation, and completion summaries for Extract, Transform, Load, and Turbo Extract types stored as OmniDataTransform metadata. Deploy thresholds are 90+ to deploy, 67-89 to review, and below 67 to block fixes. The skill enforces six mandatory anti-pattern guardrails such as unbounded Extract queries, missing lookup mappings, and hardcoded record IDs. Developers reach for it when authoring DataRaptor replacements, mapping Salesforce object fields, or reviewing OmniDataTransformItem configurations before Integration Procedures consume them.507installs53Querying Soqlquerying-soql is an agent skill that turns natural language requests into optimized SOQL and SOSL queries for Salesforce. It handles relationship queries, aggregate functions, query plan analysis, selectivity scoring on a 100-point scale, and governor-limit-aware design. The skill reads.soql files, suggests performance improvements, and flags safety issues so developers can ship reliable Salesforce data access code without guesswork. It is purpose-built for teams and developers who regularly work with Salesforce and want consistent, high-quality queries without deep SOQL memorization.494installs54Fetching Salesforce Docsfetching-salesforce-docs is an agent skill that delivers a reliable online retrieval playbook for official Salesforce documentation. It handles pages that are difficult for naive fetchers due to JavaScript rendering or complex layouts, pulling clean content from developer.salesforce.com, help.salesforce.com, architect.salesforce.com, admin.salesforce.com and lightningdesignsystem.com. Developers use it to ensure every Apex, Lightning Web Component, Agentforce or API reference answer is grounded in primary sources rather than blog summaries or outdated information. The skill includes optional extraction scripts that can be run locally to further process stubborn pages. It activates when a user explicitly asks for official Salesforce documentation and stays silent on code change or deployment tasks.491installs55Debugging Apex Logsdebugging-apex-logs is an agent skill that analyzes Salesforce debug logs to surface root causes of governor limit violations, slow queries, heap and CPU pressure, and exception stack traces. It extracts query plans, transaction context, and performance bottlenecks then returns a 100-point scoring breakdown plus a prioritized reproduction-to-fix loop. Developers working on Salesforce orgs use it after an error surfaces in production or a sandbox to turn raw log output into actionable next steps instead of manually scanning thousands of lines. The skill gathers required context such as org alias and failing transaction before starting analysis and will hand off to code-generation skills once the root cause is confirmed.486installs56Running Apex Testsrunning-apex-tests is an agent skill that executes Salesforce Apex tests, analyzes code coverage, interprets test failures, and guides developers through systematic test-fix loops. It activates automatically when the user runs Apex tests, checks coverage metrics, works with *Test.cls or *_Test.cls files, or needs to improve test quality. The skill gathers required context such as target org alias and test scope, then runs tests, scores results on a 120-point scale, highlights gaps, and iterates until the codebase meets coverage and quality standards. It is designed specifically for Apex unit testing inside Salesforce projects and does not overlap with production code generation, Agentforce agent testing, or LWC/Jest testing.485installs57Activating Datacloudactivating-datacloud is an agent skill that owns the downstream delivery portion of Salesforce Data Cloud workflows. It lets a developer or small team issue activation commands, configure activation targets, create and manage data actions, and verify that computed audiences and insights are successfully pushed into destination systems. The skill is tightly scoped: it activates only after upstream work (segment building, data ingestion, or query setup) is complete. It works by wrapping the community sf data360 CLI plugin inside a Claude-compatible agent interface so you can stay in natural language while the underlying Salesforce CLI commands execute safely against a Data Cloud-enabled org.477installs58Trigger Refactor Pipelinetrigger-refactor-pipeline is a skill from forcedotcom/afv-library with 471 installs on skills.sh (rank 39) aimed at Salesforce developers maintaining Apex triggers and record-triggered Flows. It scans for anti-patterns such as bulkification gaps, recursive trigger chains, and deprecated Flow constructs, then applies a structured refactor pipeline instead of manual one-off edits. Developers reach for trigger-refactor-pipeline before major releases or org merges when legacy automation has accumulated and runtime errors, governor limit breaches, or order-of-execution bugs are likely without systematic cleanup.475installs59Running Code AnalyzerThis AFV Library skill automates running Salesforce Code Analyzer so agents and developers can scan Apex, Lightning Web Components, and related Salesforce source for security, quality, and best-practice violations before ship. It standardizes how scans are invoked, interpreted, and fed into release review so fixes happen while context is fresh rather than after production regressions.297installs60Applying Cms BrandTeaches how to apply Salesforce CMS brand definitions—tokens, themes, typography, and color systems—to Experience Cloud and Lightning UI so customer-facing pages render with consistent, on-brand styling across components and layouts.285installs61Integrating B2b Commerce Open Code ComponentsGuides developers through integrating Salesforce B2B Commerce with Open Code components, covering API wiring, component composition, and Experience Cloud storefront patterns for enterprise buyer portals.285installs62Generating Ui Bundle Custom Appgenerating-ui-bundle-custom-app helps teams scaffold Salesforce UI bundle custom applications with navigation, branding hooks, and embedded component routes so Experience Cloud and mobile deployments get a cohesive frontend shell without manual metadata drudgery.201installs63Reviewing Lwc Mobile OfflineReviews Lightning Web Components for mobile offline readiness in forcedotcom/afv-library projects, checking sync logic, caching, connectivity edge cases, and Salesforce Mobile SDK compliance before shipping field apps.196installs64Using Mobile Native CapabilitiesTeaches how to use mobile-native capabilities inside forcedotcom/afv-library Agentforce Visual experiences, bridging Salesforce mobile containers with camera, GPS, biometrics, notifications, and offline storage while preserving AFV component conventions and enterprise security expectations.196installs65Building Mobile Appsbuilding-mobile-apps guides creation of Salesforce mobile applications: choosing mobile-ready patterns, wiring platform capabilities, and structuring UI for phones and tablets so teams can deliver field-ready SaaS apps faster with fewer platform missteps.174installs66Applying SldsSupplies theming and styling validation checks (T-series) for SLDS-authored components covering styling hooks, surface pairing, spacing, fonts, and shadows. A developer uses it when building or finalizing SLDS components to ensure hook-based styling.81installs67Investigating Agentforce D360Traces and renders a hierarchical reconstruction of one Agentforce session from Data Cloud runtime audit rows, and supports discovering sessions when no id is known. A developer uses it to inspect, summarize, or find a specific Agentforce session.81installs68Managing Managed Event SubscriptionGenerates and modifies .managedEventSubscription-meta.xml files to subscribe to platform event channels with managed replay tracking. A developer uses it to set up, update, activate, or delete managed platform event subscriptions in Salesforce.81installs69Validating SldsRuns the SLDS linter on a Lightning Web Component, adds static CSS and HTML analysis of theming hooks and accessibility attributes, and scores the findings into an overall grade. A Salesforce developer uses it to check a component's production readiness before code review or submission.81installs70Generating FragmentHandles the Data Cloud retrieve phase: sync and paginated SQL, async query workflows, table describe, vector and hybrid search, and search index operations via the sf data360 CLI. A developer uses it when querying or introspecting Data Cloud objects (not standard CRM SOQL).77installs71Investigating Agentforce ArchitectureReads design-time Agentforce metadata (BotDefinition, GenAiPlanner, GenAiPlugin, Flow, ApexClass, prompts) to produce an architecture document and Mermaid invocation graph for one agent. A developer uses it to describe, diagram, audit, or diff the architecture of a specific agent.36installs72Apex Test ClassProduces Apex test classes using @TestSetup, TestDataFactory, bulk data, HttpCalloutMock, and negative-path assertions. A developer uses it when creating or improving test coverage for Apex triggers, services, controllers, batch jobs, and integrations.16installs73Deployment Readiness CheckProvides a comprehensive pre-deployment validation checklist that verifies metadata quality, test coverage, security settings, and configuration before a Salesforce production release. A developer uses it before promoting metadata to production or higher environments.15installs74Apex ClassScaffolds well-structured Apex classes following enterprise patterns across service, selector, domain, async, and utility class types. A developer uses it when creating, refactoring, or restructuring Salesforce server-side Apex logic (excluding triggers and tests).14installs75Agentforce DevelopmentCovers the full Agent Script lifecycle for Agentforce agents: designing topic graphs, writing .agent files and AiAuthoringBundle metadata, validating, deploying, publishing, and testing. A developer uses it when building or diagnosing Agentforce agents in Salesforce.7installs76Generating Experience Lwr SiteBuilds and configures Experience Cloud Lightning Web Runtime sites through DigitalExperience metadata, covering pages, routes, theme layouts, branding, and guest sharing rules. A developer uses it when creating or modifying LWR community sites or portals in Salesforce.6installs77Building Webapp Data VisualizationAdds data visualization components (donut, pie, bar, line, area charts, and KPI stat cards) to React pages using Recharts. A developer uses it when building dashboards or analytics views in a Salesforce React web app.4installs78Configuring Webapp Csp Trusted SitesGenerates CspTrustedSite metadata for external domains a Salesforce web app references, resolving CSP violations that block images, APIs, or fonts. A developer uses it when adding a new external domain or seeing a CSP console error.4installs79Configuring Webapp MetadataDocuments WebApplication bundle rules including folder layout, matching meta XML filename, build output directory, and webapplication.json settings. A developer uses it when configuring a Salesforce web app bundle's metadata structure.4installs80Creating WebappGuides first steps for creating a Salesforce SFDX React web app, including running npm install, following the skills-first protocol, and enforcing deploy-before-schema order. A developer uses it when scaffolding a new web app in a Salesforce org.4installs81Deploying Webapp To SalesforceCodifies the canonical sequence from setup-cli.mjs for deploying metadata, assigning permission sets, and running schema fetch and codegen against a Salesforce org. A developer uses it for any deployment or org sync of webapps, LWC, Apex, or metadata.4installs82Building Webapp React ComponentsProvides patterns for editing React/TSX code in a Salesforce web app, distinguishing pages, header/footer, and components, with shadcn UI and Tailwind. A developer uses it when adding or modifying any React UI in the web application.3installs83Generating Experience React SiteGenerates the Network, CustomSite, DigitalExperienceConfig, and DigitalExperienceBundle metadata needed to serve a React app from a Salesforce Digital Experience Site. A developer uses it to set up site infrastructure for a React web application on Salesforce.2installs84Implementing Webapp File UploadGuides adding file upload to Salesforce React webapps via an API-only package that exposes upload() with onProgress and record linking, requiring you to build your own UI. A developer uses it to attach documents to Salesforce records instead of hand-rolling FormData/XHR.2installs85Installing Webapp FeaturesDrives the webapps-features-experimental CLI to find and install pre-built, tested feature packages into Salesforce React webapps before building from scratch. A developer uses it to add auth, search, navigation, GraphQL, or Agentforce UI to a webapp.2installs86Managing Webapp Agentforce Conversation ClientManages embedding and configuring the AgentforceConversationClient chat widget in React .tsx/.jsx apps, including agentId validation and styling. A developer uses it to add or restyle an Agentforce chatbot in a Salesforce web app.2installs87Using Webapp Salesforce DataProvides Salesforce data-access guidance for fetching, mutating, and querying records via the mandatory @salesforce/sdk-data Data SDK, preferring GraphQL. A developer uses it to wire React/Angular/Vue components to Salesforce standard or custom object data.2installs88Accessing Webapp DataProvides rules for fetching Salesforce data from web apps, mandating the @salesforce/sdk-data Data SDK with GraphQL as the preferred query method. A developer uses it when adding or modifying code that reads Salesforce records, Chatter, or Connect API data.1installs89Exploring Webapp Graphql SchemaGuides grep-only exploration of the ~265,000-line Salesforce GraphQL schema file, required before writing any query. A developer uses it to look up types and fields after deploying metadata and regenerating the schema.1installs90Fetching Webapp Rest ApiGuides using sdk.fetch from the Salesforce Data SDK to call REST endpoints when GraphQL is not enough, with auth, CSRF, and base URL handled by the SDK. A developer uses it to hit Chatter, Connect REST, Apex REST, UI API, or Einstein LLM APIs.1installs91Generate Permission SetProduces correct PermissionSet XML with CRUD object permissions, field-level security, tab visibility, and app permissions for the Salesforce Metadata API. A developer uses it when creating or editing permission sets to grant access.1installs92Salesforce Custom ApplicationGenerates CustomApplication (Lightning App) metadata to organize tabs and components into focused apps with Standard or Console navigation and branding. A developer uses it when creating Lightning apps or configuring app navigation and access.1installs93Salesforce Custom FieldProduces deployable CustomField metadata XML with mandatory constraints, focusing on high-failure field types like roll-up summary and master-detail relationships. A developer uses it to create fields or troubleshoot field deployment errors.1installs94Salesforce Custom Lightning TypeGenerates CustomLightningType metadata as JSON Schema-based type definitions driving Einstein Agent action inputs/outputs and editor/renderer UI. A developer uses it to define structured type schemas for Lightning Platform agent actions.1installs95Salesforce Custom ObjectProduces deployable CustomObject (.object-meta.xml) metadata with required elements like sharingModel, nameField, and visibility to avoid deployment errors. A developer uses it to create custom objects or fix object deployment issues.1installs96Salesforce Custom TabGenerates CustomTab metadata for object, web, Visualforce, or Lightning page navigation with correct motif and required properties. A developer uses it to add navigation tabs to Salesforce apps.1installs97Salesforce Experience SiteGenerates and edits Experience Cloud LWR site metadata (DigitalExperienceConfig, DigitalExperienceBundle, Network, CustomSite, CMS content) for community sites and portals. A developer uses it to build or modify LWR Experience sites with routes, views, and branding.1installs98Salesforce FlexipageGenerates FlexiPage metadata for RecordPage, AppPage, and HomePage layouts, using CLI bootstrapping for component discovery and configuration. A developer uses it to create Lightning pages or add components to flexipage-meta.xml files.1installs99Salesforce FlowGenerates Salesforce Flow metadata by running the fetchGroundedObjectMetadata, flowElementSelection, and flowElementGeneration MCP pipeline. A developer uses it to build declarative automations that trigger on record events, schedules, or user screens.1installs100Salesforce FragmentGenerates Fragment metadata as a UEM tree of blocks and regions for reusable UI that renders across Slack, Mobile, and LEX. A developer uses it to build unified experience components with data placeholders.1installs101Salesforce Lightning App BuildActs as a conductor that builds end-to-end Lightning Experience apps by invoking the specialized metadata skills in dependency order (objects, fields, UI, security, optional flows/validation). A developer uses it to turn a described business scenario into a full multi-component Salesforce app.1installs102Salesforce List ViewGenerates ListView metadata defining filters, columns, and visibility for curated record subsets on a Salesforce object. A developer uses it to create list views or fix list-view deployment errors.1installs103Salesforce Validation RuleGenerates ValidationRule metadata with formula expressions and error messages to enforce business rules at the data layer. A developer uses it to prevent invalid records from saving or to fix validation-rule deployment errors.1installs104Salesforce Web App Creating RecordsGuides implementing createRecord from @salesforce/webapp-experimental to create standard or custom Salesforce records from React apps, handling varied id response shapes. A developer uses it to wire form submissions to Salesforce record creation.1installs105Salesforce Web App FeatureGuides integrating official Salesforce feature packages into React webapps by copying source from node_modules and then adjusting imports and config. A developer uses it to add auth, search, charts, GraphQL, or Agentforce to a Salesforce web app.1installs106Salesforce Web ApplicationServes as the directory for Salesforce React BYO web-application guidance, pointing to sub-knowledges via get_expert_knowledge. A developer uses it to find the right sub-topic for adding features or working with records in a Salesforce React app.1installs107Salesforce Web App List And Create RecordsGuides building a list-and-create pattern for custom objects: query via GraphQL, create via createRecord, and refetch so the list updates without a reload. A developer uses it to build record tables with an add form in a Salesforce React app.1installs