agentleFS
forcedotcomforcedotcom/salesforcedx-vscode/.claude/skills/core-extension-api/SKILL.md

core-extension-api

Skill1k starsChanged 25 days agoBSD-3-ClauseView on GitHub

Public API exported by salesforcedx-vscode-core activate(). Use when modifying SalesforceVSCodeCoreApi, the api object in activate(), exports from core index.ts, services sub-object, or evaluating whether a change to core is breaking. Also use when someone asks "does anything use X" for a core export.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about forcedotcom/salesforcedx-vscode

The biggest 5 of 52 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 52

Talked about on GitHub and Stack Overflow (52 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Remove field from SalesforceVSCodeCoreApi

    line 26
  2. Distinctive:

    Non-breaking: add new fields.

    line 32
  3. Very specific:

    Read private repos: gh api repos/forcedotcom/REPO/contents/PATH --jq '.content' | base64 -d

    line 75
  4. Very specific:

    Call .getInstance(extensionName) on services classes

    line 84

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Core Extension Public API

packages/salesforcedx-vscode-core/src/index.ts — activate() returns SalesforceVSCodeCoreApi.

Consumers access via:

const ext = vscode.extensions.getExtension<SalesforceVSCodeCoreApi>(
  'salesforce.salesforcedx-vscode-core'
);
const api = ext.exports;

Also consumed indirectly via @salesforce/vscode-service-provider.

Public API — external consumers depend on this

See external-consumers for full list and search commands.

Breaking (check consumers first):

  • Remove field from SalesforceVSCodeCoreApi
  • Change field type
  • Change behavior (even same signature)
  • Change static methods on services.* classes (.getInstance())
  • Rename/restructure services sub-object

Non-breaking: add new fields.

API surface

Top-level (instances/functions)

workspaceContextUtils

WorkspaceContext is only services.WorkspaceContext, not a top-level activate() field.

Note: the top-level channelService field was removed (W-23348840). Consumers must use services.ChannelService.

Note: the top-level telemetryService field was removed (W-24265117). Callers use services.TelemetryService.getInstance or sf.vscode.core.get.telemetry.

Note: the top-level getUserId field was removed (W-24265117). No API replacement.

services (class constructors with static methods)

ChannelService (.getInstance(name)),
TelemetryService (.getInstance(name)),
WorkspaceContext (.getInstance()), CommandEventDispatcher (.getInstance())

External consumers predominantly use services.*. The .getInstance() signatures are public contract.

Before changing

  1. Read external-consumers
  2. Grep monorepo: \.exports\.MEMBER — catches direct access outside wrapper files
  3. Search org:
    gh api -X GET "search/code?q=SYMBOL+org:forcedotcom&per_page=30" \
      --jq '.items[] | "\(.repository.name): \(.path)"'
    # also search salesforcecli org
    gh api -X GET "search/code?q=SYMBOL+org:salesforcecli&per_page=30" \
      --jq '.items[] | "\(.repository.name): \(.path)"'
    # also search for exports.SYMBOL (direct access pattern)
    gh api -X GET "search/code?q=exports.SYMBOL+org:forcedotcom&per_page=30" \
      --jq '.items[] | "\(.repository.name): \(.path)"'
  4. Read private repos: gh api repos/forcedotcom/REPO/contents/PATH --jq '.content' | base64 -d
  5. Removing something unused in monorepo? Confirm unused externally too
  6. Changing behavior? Check consumer version gates and minimum versions

Consumer patterns

  • extensionDependencies: ["salesforce.salesforcedx-vscode-core"]
  • Version-check core (semver.satisfies(version, '>=X.Y.Z'))
  • Define own minimal type (don't import SalesforceVSCodeCoreApi directly)
  • Call .getInstance(extensionName) on services classes
  • Graceful degradation if core missing/outdated

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.