claudemods

Sourcesforcedotcom/sf-skills

forcedotcom/sf-skills Indexed

Salesforce's curated collection of agent skills for building applications. Optimized for Agentforce Vibes, compatible with all AI tools.

Open upstream repository

Indexed The index holds package records for this repository. The package count is historical registry records; it does not mean those packages are available now.

Repository

Canonical name
forcedotcom/sf-skills
GitHub repository ID
1091890109
Package records
256 (historical registry records, not current availability)

Discovery and queue

First recorded source
marketplace:anthropics/claude-plugins-official
Discovered
Queue state
ok
Recorded errors
0
Last settled processing
Next-check eligibility
Eligible from

The first recorded source is what the queue stored first, not the full discovery history. The error count increases when processing ends in the error state and resets after a successful settlement; it is not a count of all attempts. “Last settled processing” is when it finished, not when it started.

Eligibility is calculated as of . It is not a schedule: each collector run handles only a limited number of sources, and being eligible does not promise when a check happens.

Last saved scan

Repository metadata read
Scan status
complete
Scan saved
Extractor version
2
Continuation record
None

The scan record is separate from the queue state: the queue state shows processing progress, the scan record shows what was last saved. A continuation record only means unfinished state is stored; it has no remaining count.

Source-file evidence coverage

Raw counts of the pinned source files that stored package versions reference in this repository. They show what has been recorded, not how complete the repository is.

Scope and limits

Counts distinct pinned file links (repository, commit, path) across all stored versions, from any package, that name exactly this repository's canonical name. Files of packages owned by this repository are not counted unless some version links to them here. Alias names are not merged and no history is guessed from a current name.

“Known” means a regular-file identity is recorded. It does not mean a whole directory or package is covered. Links that are not valid pinned file URLs are not counted.

446 pinned source files referenced

  • 446 known
  • 0 absent at commit
  • 0 file listing truncated
  • 0 unsupported
  • 0 not recorded
  • 0 read failed

Deduplicated by repository, commit and path; the same path at two commits counts as two file identities. These are not component-group counts.

Failed source-commit reads 0

No source commit has a stored failed read for files that are still unrecorded.

Linked packages 256

Linked by verified repository identity. The count is historical registry records, not current availability.

Showing 241–256 of 256 results

  • service-omni-command-center-configureSkill

    Use to enable Command Center for Service V2 and configure its supported supervisor controls through the OmniChannel Settings Metadata API while preserving unrelated settings. Requires explicit apply consent, refuses production customer org…

  • service-omni-permission-set-assignSkill

    Assign the required Omni permission sets to provisioned agent users. TRIGGER when users ask to assign Omni permissions to agents, grant Omni-Channel access, add Omni_Agent permissions, repair missing Omni permission assignments, or prepare…

  • service-omni-presence-status-deploySkill

    Create the standard Available and Busy presence statuses needed for Omni-Channel routing. TRIGGER when users ask to deploy Omni presence statuses, configure agent availability, deploy Omni status metadata, create an Available status for Ca…

  • service-omni-presence-user-config-deploySkill

    Use to deploy an Omni PresenceUserConfig (presence configuration) as one whole-record Metadata write with the decline/ACW fields set consistently: Auto-Accept off, Decline on, Decline Reason on (with a PresenceDeclineReason deployed in the…

  • service-omni-queue-deploySkill

    Use to verify or create a Queue on a Salesforce org for a routable sObject (Case | Incident | MessagingSession | VoiceCall), discovered via its QueueSobject binding rather than by hardcoded name. Reuses whatever queue already routes the ta…

  • service-omni-queue-members-assignSkill

    Use to bind agent users into a Salesforce Queue via GroupMember Data API POSTs, with SOQL-based idempotency (safe re-run — only inserts missing bindings). Binds either the generated demo agents (agent{1..N}.<suffix>@example.com) or an expl…

  • service-omni-queue-routing-config-deploySkill

    Use to create or update a QueueRoutingConfig record on a Salesforce org via the Data API (idempotent SOQL detect + REST upsert). Naming is target-derived: Case→Case_Routing_Config, VoiceCall→Voice_Routing_Config, Incident→Incident_Routing_…

  • service-omni-routing-flow-deploySkill

    Use to deploy an Omni-Channel routing Flow for Case or VoiceCall and verify it routes work items to a queue or by skill. Supports the Case and VoiceCall steel thread with an autolaunched dryRun-gated variant and record-triggered QueueBased…

  • service-omni-service-channel-configureSkill

    Use to ensure exactly one ServiceChannel exists on a Salesforce org for a routable sObject (Case | Incident | MessagingSession | VoiceCall), reusing any standard or custom channel already bound to that sObject and only deploying a canonica…

  • service-omni-sidebar-configureSkill

    Use to enable or verify the Omni-Channel sidebar on a Lightning console app. Triggers: enable the Omni sidebar, pin Omni-Channel in a console app, configure the Omni sidebar, turn on the Omni-Channel utility region, verify the pinned Omni …

  • service-omni-skills-based-routing-configureSkill

    Use to make agents routable by Omni skills-based routing: ensure an Omni Skill exists, then assign it to each active agent through the classic Omni-Channel SkillUser junction. Idempotent — existing skills and user bindings are reused, and …

  • service-omni-supervisor-config-deploySkill

    Use to stand up a headless Omni-Channel Supervisor Configuration by deploying the classic OmniSupervisorConfig (parent plus supervisor-user and queue companions) in one atomic Metadata API deploy, idempotent via the deploy state. Requires …

  • service-omni-supervisor-permset-assignSkill

    Use to assign the Salesforce-shipped standard ContactCenterSupervisor PermissionSet (default) to N existing supervisor users via PermissionSetAssignment DML. Idempotent — SOQL detects existing (user, perm-set) pairs before POST, and DUPLIC…

  • service-omni-supervisor-surface-deploySkill

    Use to populate the Omni-Channel Supervisor action + tab surface on an existing OmniSupervisorConfig by inserting the standard OmniSupervisorConfigAction and OmniSupervisorConfigTab companion rows via the Data API, idempotent (inserts only…

  • service-omni-supervisor-users-createSkill

    Use to create N Omni-Channel supervisor users on a Salesforce org via Anonymous Apex, using the supervisor{i}.<suffix>@example.com pattern with SOQL-based idempotency (re-runs skip existing usernames). Passwords are set via System.setPassw…

  • service-omni-work-skill-routing-configureSkill

    Use to author an Omni WorkSkillRouting rule (field-based skill criteria): map a related-entity field value to a required Omni Skill (e.g. add the Voice skill when Case.Origin = Phone), deployed as one WorkSkillRouting record via the Metada…

Saved scan notes 0

No additional scan notes are stored.

Recorded aliases 0

When last recorded, these names pointed to this repository. This is a recorded resolution, not a live GitHub check; packages and metadata are never merged because of it.

No aliases pointing to this repository are recorded.

Unsupported marketplace entries 0

Entries in this repository's marketplace that this registry does not support yet. They are preserved source data and are never fetched or executed.

No unsupported entries are recorded.