Agent skill · software engineering · jeremylongshore
salesforce-install-auth
Select and document a supported Salesforce authorization path using an External Client App or an approved existing Connected App. Use when onboarding or repairing API access. Trigger with "configure Salesforce authentication".
Why this skill is useful
Provides specific commands and configurations for Salesforce SDK/CLI authentication that the AI wouldn't reliably generate on its own.
What it needs
Requires node, npm, pip, python installed locally. Requires salesforce account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Salesforce API Authorization and Client-App Onboarding Overview Choose the app and OAuth model, establish least privilege, and prove read-only access without defaulting to legacy username-password automation. Prerequisites Target org, edition, domain, environment, integration purpose, and data classes Identity, security, Salesforce administration, application, and support owners Current org policy and first-party OAuth documentation Tool Discipline Use Read, Glob, and Grep to inspect approved repository and evidence files, WebFetch to re-check current first-party Salesforce documentation, and Write or Edit only for secretless plans, fixtures, configuration, and redacted receipts. Current Contract Salesforce REST API supports OAuth through External Client Apps or Connected Apps. Creating Connected Apps is restricted as of Spring '26; existing Connected Apps can continue, while Salesforce recommends External Client Apps for new integrations. Authentication Select an OAuth flow from current Salesforce documentation for the workload and client type. Never copy browser sessions, use a human password in automation, log tokens, or assume that one flow, scope set, or login host fits every org. Instructions 1. Record the org, My Domain, edition, environment, workload, required resources, and accountable owners. 2. Determine whether the org requires an External Client App or has an approved existing Connected App. 3. Map the selected OAuth flow, scopes, policies, principal, certificate or secret custody, expiry, rotation, and revocation. 4. Inspect the repository for password flows, unpinned login hosts, broad scopes, plaintext keys, and mixed-org aliases. 5. Present app creation, policy, permission-set assignment, pre-authorization, and credential issuance for explicit approval. 6. After provisioning, discover supported API versions and run the smallest documented read-only identity or resource check. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesforce-install-auth--2def25