clientell-ai/salesforce-skills
18 skills18 installs126 starsGitHub
Install
npx skills add https://github.com/clientell-ai/salesforce-skillsSkills in this repo
1Sf Agentforcesf-agentforce is a Salesforce Agentforce reference skill for solo builders and small teams wiring autonomous service agents in org metadata. It centers on API 66.0 XML patterns: Bot definitions with active versions, context variables such as ContactId, and GenAiTopic blocks that spell scope, out-of-scope guardrails, and step-by-step instructions. Install it when you are past the idea stage and actively building on Salesforce—not when you only need a generic chatbot prompt. The value is reducing rework from invalid or incomplete agent metadata and making topic boundaries explicit before you connect flows, actions, or data lookups. It pairs with Salesforce development skills for deployment and testing but does not replace org security review or production change management.1installs2Sf Apexsf-apex is an agent skill that supplies Salesforce Apex design patterns centered on a reusable TriggerHandler framework. Solo builders and small teams customizing Salesforce orgs—or building ISV-style packages on the platform—use it when triggers grow unmaintainable or test bypass becomes ad hoc. The reference base class routes Trigger context (before/after, insert/update/delete/undelete) into overridable hooks, while static bypass helpers let tests and data jobs skip handlers safely. Concrete handlers like AccountTriggerHandler illustrate how to layer domain logic with sharing keywords. The skill is reference-oriented: it accelerates consistent trigger architecture during feature work and supports safer refactors before deployment. It does not replace Salesforce security review or governor-limit tuning but gives agents a canonical structure CRM backends expect.1installs3Sf Datasf-data is a Salesforce data operations reference skill for solo builders and small teams who must move thousands of rows into or out of an org without clicking through the UI. It walks the Bulk API 2.0 ingest lifecycle end to end: create the job, upload CSV batches, close the job, poll until processing finishes, then download success and failure artifacts. Commands use the Salesforce CLI for upsert and delete with external ID fields, while parallel REST examples show how to drive the same flow with curl when automation runs outside the CLI. The material assumes you already have org authentication, object metadata, and CSVs prepared; it does not replace data modeling or security review. Install it when you are building SaaS backends, migration scripts, or agent-driven ETL that must stay inside Salesforce governor-friendly bulk patterns instead of naive row-by-row APIs.1installs4Sf DebugSf-debug is a deep Salesforce debugging reference skill for solo developers and small teams shipping on Apex. It centralizes governor limit introspection via Limits.getX() and getLimitX() pairs, log interpretation, Execute Anonymous workflows, error-handling patterns, performance profiling, and Tooling API trace flag setup. Use it when tests pass locally but sandboxes throw LIMIT_EXCEPTION errors, when async jobs behave differently from sync transactions, or when you need to enable surgical logging without flooding org debug levels. The skill is documentation-dense rather than a single automated fix: your agent applies the tables and procedures to your repro case. It fits Clientell’s Salesforce skills bundle alongside deploy and metadata workflows. Intermediate to advanced—requires familiarity with Developer Console or VS Code, Apex execution context, and safe trace flag hygiene in shared orgs.1installs5Sf Deploysf-deploy is a Salesforce deployment patterns reference skill aimed at solo builders and small teams shipping on the Salesforce platform. It centers on a fully worked project-scratch-def.json template—org edition, feature toggles, lightning and mobile settings, security session policies, and object sharing—so scratch orgs mirror production-like capabilities before metadata deploys. Use it when you are preparing scratch orgs for feature branches, aligning enableSetPasswordInApi and community settings with integration tests, or documenting how your repo expects deploys to run. The skill is reference-heavy rather than a single-button deployer: you combine these patterns with your CLI pipeline and org authentication. It fits indie consultants and product teams who need dependable org shapes without rereading scattered Salesforce docs each sprint.1installs6Sf DiagramSf-diagram is an agent skill from the Salesforce skills pack that gives solo builders and small consultancies a diagram reference library: standard Sales Cloud ER diagrams in Mermaid, junction-object patterns, and syntax guidance for ASCII equivalents. Use it when you must explain who relates to what—accounts to opportunities, line items to price books, or custom master-detail links—before configuring flows, integrations, or security reviews. The skill accelerates documentation and alignment meetings rather than deploying metadata. It assumes you are already in a Salesforce-centric build (CRM extensions, revops tooling, or customer-facing SaaS with Salesforce as system of record). Output is diagram source code you paste into repos, Notion, or ADRs. Intermediate familiarity with Salesforce object names helps; beginners can still copy templates and learn relationship cardinality from the examples.1installs7Sf Docssf-docs is an agent skill that acts as a Salesforce documentation navigator for solo builders and small teams extending Salesforce. When you are building Apex, Lightning Web Components, Flow, Agentforce, or admin automation, the skill helps locate the right official developer.salesforce.com guides instead of hallucinating links or outdated blog posts. It encodes a structured index of major guides—Apex, SOQL/SOSL, LWC, Metadata API, REST, and related references—with when-to-use hints so the agent can answer navigation requests quickly. Install it when your agent frequently handles Salesforce questions during integration work. It complements hands-on coding skills by reducing time lost to wrong doc sections and keeps answers anchored to Salesforce’s canonical documentation structure.1installs8Sf Evalsf-eval is a Salesforce skills evaluator for builders and skill authors who need evidence that procedural SKILL.md context actually improves Apex and platform code. It runs structured benchmarks: read tasks from the bundled benchmarks JSON, generate a baseline without Salesforce skill knowledge, then generate with full skill context, and score both against a rubric covering security, governor limits, bulkification, patterns, and completeness. Activate on phrases like evaluate skills, benchmark, skill quality, run eval, or compare with/without skills. It works standalone and can optionally lean on Salesforce CLI for static analysis. Solo builders maintaining custom Salesforce skills or deciding whether to adopt Clientell-style packs use it to justify investment and catch regressions when prompts or skills change.1installs9Sf Findsf-find is an agent skill that acts as the Salesforce development catalog inside Claude Code and similar agents: when a user is unsure which specialized skill fits—Apex, tests, Flows, LWC, SOQL, security review, deploy, data migration, metadata schema, or debug log analysis—it lists each option with when-to-use guidance and the exact invoke phrase. Solo builders and tiny teams on Salesforce stacks install it to stop wasting tokens on the wrong skill and to standardize handoffs as they grow custom org complexity. It is intentionally lightweight meta tooling (read-only context, fork) rather than implementation code, so it belongs at the front of a Salesforce agent session before heavier sf-* skills run. Pair it with the specific domain skill once the task is classified.1installs10Sf Flowsf-flow is a reference agent skill for Salesforce Flow development expressed as valid Flow metadata XML. It documents elements such as Assignment with operators (Assign, Add), assignment from record fields via elementReference, and patterns for adding items to collections, each with connector hooks to the next element. Solo builders and small teams extending Salesforce for CRM, RevOps, or custom SaaS on the platform can invoke this skill when their agent must generate or review flow XML instead of hand-waving Admin UI clicks. The readme is structured as a technical cookbook rather than a business methodology, so it pairs best with an org where you deploy flows as metadata in source control.1installs11Sf IntegrationSf-integration is a reference skill in the Clientell Salesforce skills pack for solo builders and consultants who connect Salesforce orgs to external HTTP services. It supplies ready-to-adapt Named Credential metadata XML for both legacy password-style credentials and enhanced credentials backed by External Credentials, including endpoint, principal type, protocol, and safe defaults for authorization headers and merge fields. The readme draws a clear boundary: this file is configuration and metadata templates plus auth-flow and architecture guidance, while actual Apex callout implementation patterns belong in the separate sf-apex integration-patterns doc. That split helps agents generate deployable integration.xml-style artifacts without inventing insecure auth combinations. Use it when you are standing up a new middleware, payment, or legacy REST bridge and need Salesforce-side auth objects defined correctly before writing callout code.1installs12Sf Lwcsf-lwc is a patterns reference skill for solo builders and small teams building on Salesforce who need Lightning Web Components that follow platform-native data access. Instead of routing every screen through custom Apex, the skill documents how to wire getRecord with explicit schema imports, derive display values safely, and pull object metadata through getObjectInfo. It is aimed at agents and developers using Claude Code, Cursor, or Codex inside a Salesforce DX workspace who want consistent, reviewable LWC that respects field-level security patterns via optionalFields where appropriate. Use it during feature work when you are implementing record detail panels, related lookups, or metadata-driven forms and need authoritative snippets rather than outdated Aura-era examples. The content is reference-oriented: you invoke it while coding LWCs, paste-adapt the patterns, and keep your components aligned with Lightning UI APIs for maintainability and faster security review on enterprise orgs.1installs13Sf Omnistudiosf-omnistudio is a deep reference skill for solo builders and small teams extending Salesforce OmniStudio in Claude Code, Cursor, or Codex. It documents how to detect which OmniStudio namespace is installed using ordered COUNT() probes against OmniProcess or packaged OmniScript types, then translate the same concepts—OmniScript containers, elements, FlexCards, and Data Mapper bundles—across Core, vlocity_cmt, and vlocity_ins object and field names. Use it when an agent would otherwise guess wrong API names during retrieve, deploy, or integration scripts for Communications, Media, Energy, Insurance, or Health clouds. The skill does not replace official Salesforce docs; it compresses namespace detection and field-mapping tables into agent-ready guidance so implementation plans and SOQL stay aligned with the org you are actually connected to.1installs14Sf Permissionssf-permissions is a reference skill for solo and indie builders shipping on Salesforce who need accurate Permission Set metadata without guessing XML tags. It catalogs the elements you can declare in a permission set—object and field rights, tab visibility, Apex and page access, custom permissions, and related access types—so agents can generate or review security configs that match org reality. Use it when you are modeling profiles and permission sets for integrations, sandboxes, or CI-deployed metadata, not when you only need a business process diagram. The skill is documentation-forward: it anchors agent output to Salesforce’s metadata schema so access changes stay auditable and deployable. It matters because mis-modeled permissions are a common source of production surprises and failed deployments for small teams without a dedicated admin.1installs15Sf Schemasf-schema is an agent skill that equips solo builders and small teams with Salesforce Metadata API–style XML fragments for custom fields and formulas. When you extend Leads, Opportunities, or custom objects, agents often hallucinate invalid field types, wrong blank-handling, or broken cross-object syntax—this skill anchors generation to concrete patterns for text, number, and date formulas, renewal-date logic, and CASE-driven scoring. It fits builders shipping SaaS with Salesforce as system of record, RevOps automations, or sync services that must deploy metadata through CI. Use it while modeling fields in build, before packaging changes for ship, not as a substitute for org-specific validation rules or full object XML. Pair with your deployment toolchain and org documentation so generated XML matches your namespacing and API version.1installs16Sf Securitysf-security is a Salesforce security patterns reference skill for solo builders and small teams shipping on Platform who need correct CRUD and field-level security in Apex without memorizing every API variant. It documents USER_MODE for SOQL and dynamic queries, stripInaccessible before insert, update, and returning records to users, and Database DML operations with AccessLevel.USER_MODE, plus class-level with sharing versus without sharing guidance. Use it while implementing integrations and services in Build, and again in Ship when hardening code paths before production or partner review. The skill is procedural knowledge packaged as copy-pasteable Apex patterns—not a scanner—so you still run org security reviews and checkstyle rules separately. It pairs naturally with broader Salesforce skills in the same repo when you move from feature code to compliance-safe data access.1installs17Sf SoqlSf-soql is a Salesforce SOQL and SOSL reference skill for solo builders shipping SaaS or internal tools on Clientell-style Salesforce stacks. It catalogs date literals from single-day anchors through week, month, and quarter windows, each with clear start/end behavior and example queries against common CRM objects. Use it when you are wiring Apex, Flow-adjacent logic, agent-driven data pulls, or analytics exports and need literal syntax without guessing calendar boundaries. The skill reduces integration bugs from off-by-one date filters and inconsistent activity versus created date fields. It does not replace Salesforce security review or bulk API governance; it accelerates correct query authoring during backend and integration work. Intermediate familiarity with Salesforce objects helps; beginners can still lean on the literal tables as a checklist while pairing with org-specific field metadata.1installs18Sf TestSf-test is an agent skill that provides a patterns reference for Salesforce Apex testing with full, compilable examples. Solo builders and small teams shipping on Salesforce use it when implementing @future handlers, batch jobs, and similar asynchronous Apex and need tests that actually exercise async boundaries via Test.startTest() and Test.stopTest(). The readme walks through realistic classes and matching @IsTest classes, including constraints such as batch execute scope in tests and the single executeBatch call per method. Point your agent at this skill during Ship testing work to avoid hollow tests that never flush futures or batches, and to standardize assertion style. It is pattern documentation rather than a test runner or CI integration.1installs