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

Sales Call Scoring Configure

by forcedotcom in forcedotcom/sf-skills

Configure, set up, or repair AI Call Scoring (a.k.a. An agent skill from forcedotcom/sf-skills.

Apache-2.0Auto-check passedSales & Support

Install Sales Call Scoring Configure

skills CLI
$ npx skills add forcedotcom/sf-skills --skill sales-call-scoring-configure -a claude-code

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

GitHub CLI
$ gh skill install forcedotcom/sf-skills sales-call-scoring-configure --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/forcedotcom/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sales-call-scoring-configure .claude/skills/sales-call-scoring-configure && 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
sales-call-scoring-configure
GitHub stars
1.1k
Token cost
~4.8k tokens
SKILL.md length
2,094 words
Files
22 (incl. scripts, references, assets)
Skills in repo
252
Repo updated
First seen
Licence
Apache-2.0

At a glance

Configure, set up, or repair AI Call Scoring (a.k.a. An agent skill from forcedotcom/sf-skills.

  • Works in 7 steps: Auth → ECI purchase gate → State detection → …
  • : user wants to turn on AI Call Scoring
  • SKILL.md covers Scope, Prerequisites, Clarifying Questions and Admin Communication Guidelines, plus 7 more sections
  • Runs Shell scripts from its folder; calls sf; needs ACCESS_TOKEN

What it does

Sales Call Scoring Configure is an agent skill from forcedotcom/sf-skills. Configure, set up, or repair AI Call Scoring (a.k.a. Call Coaching / Coaching Competencies) on an ECI-enabled Salesforce org. Flips ECICallScoringEnabled via SOAP Metadata API, enables Einstein Generative AI Platform if off, and manages Coaching Competency records (EnablementCompetencyDef Tooling API): install the 6 OOTB set, the 7 Momentum best-practice prompts, or conversationally author/edit/activate/deactivate custom competencies (8-active + 16000/255-char caps). TRIGGER when: user wants to turn on AI Call…

Its SKILL.md is about 4.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 25 other files, including scripts, reference files and assets (for example `assets/best-practice-competencies.json`, `assets/ootb-competencies.json` and `references/admin-communication.md`).

It sits in Sales & Support, covering CRM management. It works with Salesforce. The repository describes itself as: Salesforce's curated collection of agent skills for building applications. Optimized for Agentforce Vibes, compatible with all AI tools. The licence is Apache-2.0.

When your agent uses it

  • : user wants to turn on AI Call Scoring
  • Best-practice competencies
  • Create/edit custom competencies
  • Re-enable after sandbox refresh

Example prompts

  • “/sales-call-scoring-configure”

Requirements

  • A Bash shell
  • A credential in ACCESS_TOKEN

Workflow steps

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

  1. Auth
  2. ECI purchase gate
  3. State detection
  4. Route by state
  5. Prerequisite enablement (State 2 only)
  6. Enable Call Coaching (State 2 only)
  7. Verify (State 2 only)

What it can do on your machine

Read from SKILL.md and the folder at commit 4bbae5c. 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

    Ships 12 files in scripts/ (Shell, from the files we listed), which the agent can run.

    Shell commands in SKILL.md call:

    • sf

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

  • Network

    No URLs in SKILL.md.

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

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • ACCESS_TOKEN

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

Context cost

Sales Call Scoring Configure loads about 4.8k tokens when it runs, and up to ~9.9k if it reads all its reference files. Until then it costs about 250 tokens; SKILL.md has 2,094 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

The full file from forcedotcom/sf-skills at commit 4bbae5c, republished under its Apache-2.0 licence (© forcedotcom). 2,094 words, ~4,824 tokens.

Download SKILL.mdSave it as .claude/skills/sales-call-scoring-configure/SKILL.md (or your agent's skills folder). This skill also uses 21 other files; get the full folder from GitHub.
name
sales-call-scoring-configure
description
Configure, set up, or repair AI Call Scoring (a.k.a. Call Coaching / Coaching Competencies) on an ECI-enabled Salesforce org. Flips ECICallScoringEnabled via SOAP Metadata API, enables Einstein Generative AI Platform if off, and manages Coaching Competency records (EnablementCompetencyDef Tooling API): install the 6 OOTB set, the 7 Momentum best-practice prompts, or conversationally author/edit/activate/deactivate custom competencies (8-active + 16000/255-char caps). TRIGGER when: user wants to turn on AI Call Scoring or Call Coaching, install OOTB or best-practice competencies, create/edit custom competencies, re-enable after sandbox refresh, or verify/repair partial Call Coaching setup on a 68+ ECI org. DO NOT TRIGGER when: no ECI license (direct to Agentforce for Sales), user wants to enable ECI/Momentum themselves (out of scope — Setup), Pipeline Management (use sales-agentforce-pipeline-management-configure), or custom agent (use agentforce-generate).
metadata.version
1.0
metadata.domains
Sales
metadata.minApiVersion
68.0
metadata.relatedSkills
sales-agentforce-pipeline-management-configure, agentforce-generate

Sales Call Scoring — Configure

Configure Call Coaching (a.k.a. AI Call Scoring / Coaching Competencies) on a Salesforce org. Detects the org's current state, enables dependent features it is authorized to enable, and flips the ECICallScoringEnabled org preference via the SOAP Metadata API.

Scope

In scope

  • ECI-enabled orgs only. The skill supports orgs on the ECI (Einstein Conversation Insights) arm (spike scope: ECI-only for MVP).
  • Detect which of the 4 PRD-scoped org states the org is in.
  • Enable Einstein Generative AI Platform if off (PRD-authorized dependency).
  • Flip enableECICallScoring to true via SOAP Metadata API v68.
  • Verify the change took effect.
  • Idempotent — clean exit on states 3 and 4 (already enabled).

Out of scope

  • River Rush / Momentum detection. Deferred until that arm goes live — see Key Considerations. A Momentum-only org today is not distinguished from any other ECI-off org; it gets the generic "ECI is not enabled" message from Phase 3, not a Momentum-specific one.
  • Enabling ECI or Momentum themselves. PRD-explicit out-of-scope; the skill detects and messages the admin to enable ECI via Setup.
  • License provisioning. Missing base licenses (Agentforce for Sales, ECI license) require an account-team ticket.
  • Competency CRUD. Handled by sibling scripts in this same skill — see "Competency CRUD workflow" below (§S3-§S10) and the "Execution sequence" matrix.

Prerequisites

  1. sf CLI authenticated — sf org login web --alias <org-alias>.
  2. ECI arm licensed and enabled: ConversationPilot org permission (Phase 0 purchase gate) and enableCallCoaching pref (Phase 1, the ConversationPilotPref preference). (River Rush/Momentum is a separate arm covered by the same server-side gate but not checked by this skill yet — see Key Considerations.)
  3. Site gate com.salesforce.eci.callScoringEnabled open on the org's pod (RelEng-controlled; not admin-toggleable).

Einstein GenAI Platform is a soft prerequisite — the skill enables it automatically when off.

Clarifying Questions

Ask the admin: target org alias? Sandbox refresh scenario? (The pref has disableOnSandboxCopy=true, so it must be re-flipped after every refresh — that's normal, not a failure.)

Admin Communication Guidelines

CRITICAL: This skill serves admin users, not developers. The full 13-rule spec with rationale for each rule lives in references/admin-communication.md — consult it before your first response in this skill. Summary of the load-bearing rules:

  1. Run all bash commands in background (run_in_background: true).
  2. Speak admin language, not entity language — "Call Coaching", "Coaching Competency", "active/inactive". Never EnablementCompetencyDef, enableECICallScoring, EvaluationInstructions, SourceCompetencyTemplate in primary chat text.
  3. Hide technical details — no record Ids, DeveloperNames, Template enum keys, HTTP codes, SOAP responses, curl/jq internals, script paths, or phase numbers. Exception: the S9 verify markdown table (see references/competency-crud.md §S9).
  4. Chain automatically — when a script prints Next: <script>, run it in the same turn without asking. Exception: State 3 → rule #13.
  5. Ask OOTB-vs-custom once — on first-time competency setup (State 3, unqualified intent), render install-ootb-competencies.sh --list and let the admin choose. Only checkpoint in this skill where Claude asks before writing.
  6. Idempotency is silent — if already on/installed, say so briefly and move on.

See references/admin-communication.md for the full 13-rule spec, including error-surfacing, outcome-vs-steps reporting, and the S9 carve-out rationale.

Workflow

Phase 0 — Auth

Resolves org auth via the shared scripts/shared/auth.sh helper (resolve_org_auth "$ORG_ALIAS"), which every script in this skill sources: validate the alias format, call sf org display for instanceUrl and accessToken (falling back to sf org auth show-access-token when the CLI redacts the token), refuse a non-HTTPS instance URL, and fail closed with an explicit sf org login web --alias <alias> instruction if the org isn't reachable or no token can be extracted. If ACCESS_TOKEN/INSTANCE_URL are already exported for the same alias — e.g. a parent shell already resolved auth and is chaining multiple of these scripts in one session — resolution is skipped and the cached values are reused. orgId is not part of this helper; enable-call-scoring.sh fetches it separately (via its own sf org display) purely for the status banner.

Phase 0 — ECI purchase gate

Before any state detection, query the ConversationPilot OrgPermission via Tooling API (OrganizationSettingsDetail, same pattern as the ECICallScoringAI gate in Phase 3). This is a license/purchase check, distinct from enableCallCoaching below (the admin's Setup toggle for an org that's already licensed):

  • Not enabled: exit with: "Call Coaching couldn't be turned on because this org doesn't have Einstein Conversation Insights, which is required to use Call Coaching. To proceed, an admin can go to Setup → Salesforce Go → Einstein Conversation Insights, or contact their sales representative, to understand how to purchase ECI." Non-zero exit.
  • Enabled: proceed to Phase 1's enableCallCoaching check.
Phase 1 — State detection

SOAP readMetadata at /services/Soap/m/68.0 against two settings types:

  1. ConversationalIntelligenceSettings → read enableCallCoaching (ECI arm) and enableECICallScoring (current Call Coaching state).
  2. EinsteinGptSettings → read enableEinsteinGptPlatform.

(RiverRushSettings/riverRushEnabled — Momentum — is NOT read. That detection is deferred until the River Rush arm goes live; see Key Considerations for where to re-add it.)

Query existing competencies via Tooling API: SELECT COUNT() FROM EnablementCompetencyDef.

Classify the org into one of 4 states:

StateDetection
1a. Not available (no ECI license)Cannot read ConversationalIntelligenceSettings
2. Available, not enabledenableCallCoaching=true AND enableECICallScoring=false
3. Enabled, no competenciesenableECICallScoring=true AND count = 0
4. Enabled, with competenciesenableECICallScoring=true AND count > 0
Phase 2 — Route by state
  • State 1a: Exit with PRD-verbatim message: "AI call coaching is not available in this org and they need Agentforce for Sales." Non-zero exit.
  • State 3 / State 4: Exit 0 with a ready-for-competency-setup message.
  • State 2: Proceed.
Phase 3 — Prerequisite enablement (State 2 only)
  • License gate (checked first): query OrganizationSettingsDetail (Tooling API) for the ECICallScoringAI OrgPermission. If it isn't true, exit with: "AI call coaching is not available in this org and org requires Agentforce for Sales license." Non-zero exit. This runs even when enableCallCoaching/enableECICallScoring already read favorably, since those settings don't by themselves confirm the org is licensed. Must run before the ECI-off check below — a genuinely unlicensed org and a licensed-but-toggled-off org both read enableCallCoaching=false, so checking ECI first would misdiagnose a licensing gap as a self-serve Setup toggle (the regression the NoLicense eval dataset guards against).
  • If ECI is off: refuse with a Setup pointer, exit non-zero. This skill does NOT enable ECI (PRD explicit). (A Momentum-only org lands here too, since Momentum isn't detected separately — it gets this same generic message, not a Momentum-specific one.)
  • If Einstein GenAI off: SOAP updateMetadata on EinsteinGptSettings with enableEinsteinGptPlatform=true. PRD explicitly authorizes this. If it's already on, skip the updateMetadata call and tell the admin it's already enabled. If the update fails because the org isn't licensed for EinsteinGptSettings (or is explicitly refused with no fault): tell the admin they need Agentforce for Sales to enable AI Call Scoring, and that without it they can still set up manual call scoring via Salesforce Go setup. A distinct auth/permission or network/timeout failure gets its own message (check CLI session / retry) rather than the licensing message, since those aren't licensing gaps.
Phase 4 — Enable Call Coaching (State 2 only)

If enableECICallScoring already reads true (e.g. it changed out-of-band between Phase 1's read and here), skip the update and tell the admin it's already enabled. Otherwise SOAP updateMetadata on ConversationalIntelligenceSettings with enableECICallScoring=true. Require <success>true</success>.

Phase 5 — Verify (State 2 only)

Re-read enableECICallScoring. Require true. Print SOAP response on failure.

Show full SKILL.md (922 more words)Show less

Key Considerations

  • API version is v68.0, not v64.0. enableECICallScoring is not present in the ConversationalIntelligenceSettings schema at lower API versions on some builds — v68 is the safe minimum. The Pipeline skill uses v64 because its target field (SalesDealAgentSettings.enableDealAgent) is present there; Call Scoring is not.
  • Do NOT use sf mdapi deploy for this pref. It has a silent failure mode where the CLI reports success but the pref doesn't flip. Use raw SOAP updateMetadata — the response's <success> boolean is authoritative.
  • The server-side gate is broader than this skill's scope. The orgHasCallScoring access check allows the ECI arm OR the River Rush (Momentum) arm — see CoachingCompetenciesFeature.isFeatureAvailableInOrg(). This skill deliberately narrows to the ECI arm (MVP scope per the spike).
  • River Rush (Momentum) detection is deliberately absent right now, not an oversight — the arm isn't live yet. enable-call-scoring.sh used to read RiverRushSettings.riverRushEnabled and refuse Momentum-only orgs with a distinct "State 1b" message / emit a Momentum-available-but-off advisory; both were removed. Re-add them (the read, the State 1b branch, and the Phase 3 advisory) once River Rush ships — the removed code is recoverable from git history on this file.
  • disableOnSandboxCopy=true — every sandbox refresh disables this pref. Admins re-running the skill after a refresh is the expected pattern; the idempotency check makes that safe.
  • Site switch com.salesforce.eci.callScoringEnabled must be open on the org's pod. It's not admin-toggleable and not readable via SOAP. If closed, updateMetadata returns a well-formed response with <success>false</success> and an <errors><statusCode>…</statusCode></errors> block — it does NOT emit a SOAP <Fault>. parse_soap_response extracts the statusCode and surfaces it via the WRITE_ERROR:… classification.
  • ECI provisioning is asynchronous. For a short window after enableCallCoaching flips on, the dependent enableECICallScoring field is server-side read-only and updateMetadata returns INSUFFICIENT_ACCESS_OR_READONLY. enable-call-scoring.sh maps this to a transient "still finishing turning on — wait a few minutes and re-run" message rather than a terminal failure (W-23968462).
  • Every SOAP call is bounded by a 30s timeout (CURL_TIMEOUT in enable-call-scoring.sh, matching the only existing timeout precedent in this repo — the Pipeline skill's setup-all.sh) and classified via shared/soap.sh's parse_soap_response into true / false / AUTH_ERROR:... / TYPE_UNAVAILABLE:... / WRITE_ERROR:… / NETWORK_ERROR. This distinguishes "org isn't licensed for this setting" from "auth/permission fault" from "server refused the write with a specific statusCode" from "network/timeout error" — instead of collapsing them into an empty string or dumping raw SOAP XML at the admin.
  • enable-call-scoring.sh uses raw SOAP, not sf api request rest. Every other script in this skill uses sf api request rest so the CLI manages auth end-to-end. enable-call-scoring.sh is the sole exception: it calls the SOAP Metadata API (readMetadata/updateMetadata) directly, because no non-beta Salesforce CLI command exposes SOAP Metadata reads/ writes for ConversationalIntelligenceSettings et al., and sf mdapi deploy has the silent-failure mode noted above for this exact field. This is a deliberate, scoped exception, not an oversight.

References

  • Reference skill (canonical single-OrgPref pattern): skills/sales-agentforce-pipeline-management-configure/
  • SOAP helpers: scripts/shared/soap.sh (copied from the Pipeline skill — redact_token, parse_soap_response)
  • Server-side gate (declarative access check): core/conversation-udd/java/resources/udd/conversation-udd/ConversationalIntelligence.accessChecks.xml — orgHasCallScoring = ECI arm OR River Rush arm; orgHasECICallScoringWithAI adds Einstein GenAI + ECICallScoringAI license perm on top.
  • Pref declaration: core/conversation-udd/java/resources/udd/conversation-udd/ConversationalIntelligence.settings.xml — <orgPreference name="ECICallScoringEnabled" mdApiName="enableECICallScoring" ...>
  • Java feature registration (would be the entry point if a SetupDiscoveryService REST/MCP wrapper existed): core/conversation-impl/java/src/conversation/features/CoachingCompetenciesFeature.java

Competency CRUD workflow

Once Phase 5 confirms Call Coaching is enabled (or Phase 1 detects State 3/4), Claude runs the Next: script directly, in the same turn. Records are managed via Tooling API on EnablementCompetencyDef (setup entity, keyPrefix 1nA, module conversation-udd). Cap: 8 simultaneously active per org (CoachingCompetenciesFeature.MAX_ACTIVE_COMPETENCIES).

All scripts share shared/auth.sh / resolve_org_auth — token propagates across chained invocations, no re-auth. Tooling API writes go through sf api request rest where practical; a subset (custom-CRUD variants, best-practice installer) drops to raw curl for finer request shape.

Scripts fall into two parallel families:

  • Generic — {create,edit,toggle,get}-competency.sh — works on any competency.
  • Custom-CRUD variants — *-custom-competency.sh — harden the write path with SpecificCallsOnly filter JSON and richer validation.

Prefer custom variants when the admin's intent is unambiguously custom (S5-created); fall back to generic on OOTB or unknown-provenance records.

Full spec — S3 through S10 script contracts, S5's Q1-Q4 conversational drafting sequence, the admin-intent × org-state execution matrix, and chaining checkpoints — is in references/competency-crud.md. Consult it whenever the admin's ask touches competency records (list, install, create/edit, activate, verify, delete).

Standalone Scripts (summary)

ScriptPurpose
enable-call-scoring.sh <alias>Detect state, enable Einstein GenAI if off, flip the Call Coaching pref (Phase 0-5).
list-competencies.sh <alias> [--verbose|--json]List all competencies + status. Admin-safe by default; --verbose adds Ids/DeveloperNames; --json for the calling agent only.
install-ootb-competencies.sh <alias> [--dry-run]Install the 6 PRD-canonical OOTB competencies.
install-best-practice-competencies.sh <alias> [--dry-run] [--only "Name1,Name2"]Install the 7 Momentum best-practice reference prompts. --only filters by MasterLabel.
create-competency.sh <alias> <payload.json>Create one competency (generic — usable on OOTB or custom).
create-custom-competency.sh <alias> <payload.json>Create one custom competency (hardened variant — prefer for S5).
edit-competency.sh <alias> <ident> ...Edit description / instructions (generic).
edit-custom-competency.sh <alias> <ident> ...Edit description / instructions (custom-CRUD variant).
toggle-competency.sh <alias> <ident> <activate|deactivate>Activate / deactivate (generic).
toggle-custom-competency.sh <alias> <ident> <activate|deactivate>Activate / deactivate (custom-CRUD variant).
get-competency.sh <alias> <ident> [--field <f>]Fetch a record or single field (generic).
get-custom-competency.sh <alias> <ident> [--field <f>]Fetch a record or single field (custom-CRUD variant).
verify-ootb-competencies.sh <alias> ["Name" ...]Confirm expected competencies exist and are active — outputs the S9 admin-visible markdown table.
no delete script (yet)Use sf data delete record --sobject EnablementCompetencyDef --record-id <Id> --use-tooling-api — see §S10.

Admin Verification

After a successful run, the admin can independently verify:

Via UI — Salesforce Go → Coaching Competencies should now be reachable and show the feature as enabled with the configured competencies.

Via CLI — two Tooling API queries:

bash
# Feature enabled?
sf data query --target-org <alias> --use-tooling-api \
  --query "SELECT IsEciCallScoringEnabled FROM ConversationalIntelligenceSettings"

# Competencies configured?
sf data query --target-org <alias> --use-tooling-api \
  --query "SELECT MasterLabel, IsActive, SourceCompetencyTemplate FROM EnablementCompetencyDef ORDER BY MasterLabel"

Assets

  • assets/ootb-competencies.json — 6 PRD-canonical OOTB prompt bodies (installed by install-ootb-competencies.sh).
  • assets/best-practice-competencies.json — 7 Momentum best-practice prompt bodies (S5 authoring reference; also installable via create-competency.sh).

© forcedotcom, Apache-2.0. 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 21 other files (scripts, references, assets) in skills/sales-call-scoring-configure of forcedotcom/sf-skills.

  • SKILL.md
  • assets/best-practice-competencies.json
  • assets/ootb-competencies.json
  • references/admin-communication.md
  • references/competency-crud.md
  • scripts/create-competency.sh
  • scripts/create-custom-competency.sh
  • scripts/edit-competency.sh
  • scripts/edit-custom-competency.sh
  • scripts/enable-call-scoring.sh
  • scripts/get-competency.sh
  • scripts/get-custom-competency.sh
  • scripts/install-best-practice-competencies.sh
  • scripts/install-ootb-competencies.sh
  • scripts/list-competencies.sh
  • scripts/shared/auth.sh
  • scripts/shared/cap.sh
  • … and 5 more

Open the folder on GitHubat commit 4bbae5c

Compare with similar skills

Sales Call Scoring Configure 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.

Sales Call Scoring Configure compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sales Call Scoring Configure this skillforcedotcom/sf-skills1.1k—~4.8kAutomated safety check: PassApache-2.0
Soql Lib Query Builderbeyond-the-cloud-dev/soql-lib154—~4.3kAutomated safety check: PassMIT
Sf DatacloudJaganpro/sf-skills424—~2.7kAutomated 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
Sf FlowJaganpro/sf-skills424—~1.8kAutomated safety check: PassMIT

Similar skills

  • 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 7 days ago
    Sales & SupportAuto-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
    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 7 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

  • Sf Flow

    Jaganpro/sf-skills

    Creates and validates Salesforce Flows with 110-point scoring.

    424 GitHub stars~1.8k tokensUpdated 5 mo ago
    Sales & SupportAuto-check passed

  • Google Maps Export

    gmapsscraper/google-maps-agent-skills

    Export Google Maps business data to CSV, JSON, or CRM format (HubSpot, Pipedrive, Salesforce).

    132 GitHub stars~1.2k tokensUpdated 4 mo ago
    Sales & SupportAuto-check passed

More from forcedotcom/sf-skills

All 252 skills in this repo

  • Agentforce Architecture Analyze

    forcedotcom/sf-skills

    Declared architecture snapshot for one Agentforce agent: planner, topics, actions, flows, Apex, prompt templates, and NGA plugins.

    1.1k GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed

  • Agentforce D360 Analyze

    forcedotcom/sf-skills

    Data Cloud 360° view of a single Agentforce session. An agent skill from forcedotcom/sf-skills.

    1.1k GitHub stars~3.4k tokensUpdated yesterday
    Auto-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
    Auto-check: notes

  • 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.4k tokensUpdated yesterday
    Auto-check: notes

  • Design Systems Slds Apply

    forcedotcom/sf-skills

    Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons.

    1.1k GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed

  • Experience Lwc Generate

    forcedotcom/sf-skills

    Lightning Web Components with PICKLES methodology and 165-point scoring.

    1.1k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Sales Call Scoring Configure

What does Sales Call Scoring Configure do?

Configure, set up, or repair AI Call Scoring (a.k.a. An agent skill from forcedotcom/sf-skills. Sales Call Scoring Configure is an agent skill from forcedotcom/sf-skills.a.

When should I use Sales Call Scoring Configure?

Sales Call Scoring Configure fits situations like: : user wants to turn on AI Call Scoring; best-practice competencies; create/edit custom competencies; re-enable after sandbox refresh.

How do I install Sales Call Scoring Configure in Claude Code?

Run `npx skills add forcedotcom/sf-skills --skill sales-call-scoring-configure -a claude-code`. Or copy the skill folder (skills/sales-call-scoring-configure in forcedotcom/sf-skills) into .claude/skills/sales-call-scoring-configure in your project. Claude Code loads it when a task matches its description.

How do I install Sales Call Scoring Configure in Codex?

Run `npx skills add forcedotcom/sf-skills --skill sales-call-scoring-configure -a codex`. Or copy the skill folder (skills/sales-call-scoring-configure in forcedotcom/sf-skills) into .agents/skills/sales-call-scoring-configure in your project. Codex loads it when a task matches its description.

Can I use Sales Call Scoring Configure 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 forcedotcom/sf-skills --skill sales-call-scoring-configure -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sales-call-scoring-configure, .gemini/skills/sales-call-scoring-configure, .github/skills/sales-call-scoring-configure and .opencode/skills/sales-call-scoring-configure in your project.

What does Sales Call Scoring Configure need to run?

Going by SKILL.md and its folder, Sales Call Scoring Configure needs a shell for the scripts in its folder, the command-line tools its instructions call (sf) and credentials named ACCESS_TOKEN. Our summary lists: A Bash shell; A credential in ACCESS_TOKEN.

Does Sales Call Scoring Configure access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Sales Call Scoring Configure 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Sales Call Scoring Configure use?

Sales Call Scoring Configure is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sales Call Scoring Configure use?

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

What are the alternatives to Sales Call Scoring Configure?

Skills that share tags, products or a category with Sales Call Scoring Configure: Soql Lib Query Builder (beyond-the-cloud-dev/soql-lib, 154 stars), Sf Datacloud (Jaganpro/sf-skills, 424 stars), Soql Lib Selector (beyond-the-cloud-dev/soql-lib, 154 stars) and Dev Setup (Portwood-Global-Solutions/Portwood, 126 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sales Call Scoring Configure?

forcedotcom (a GitHub organization) maintains it in forcedotcom/sf-skills, which has 1,067 GitHub stars. The repository holds 252 skills in this directory. The repository was last updated on October 9, 2026.

Source: forcedotcom/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.