Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/salesforce-install-auth

@820dfc8
Run it yourself

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".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/salesforce-install-auth

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈63 tokens for metadata: the name and description. ≈903 when used: this file.

Description uses 3.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈252 characters, or 3.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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. Store only secret references and a redacted receipt; test revocation and recovery in a non-production org.

Approval Boundaries

Do not create or alter a client app, grant scopes, assign permissions, issue credentials, or test production writes without the named org and security owners.

Output

Return the app-type decision, OAuth contract, access matrix, secret references, read-only verification, rotation and revocation owners, and unresolved policy questions.

Error Handling

Condition Response
New Connected App creation is unavailable Use the org-approved External Client App path or obtain Salesforce Support guidance; do not bypass the restriction.
Authorization succeeds but a resource is denied Compare scopes, permission sets, CRUD, field access, sharing, edition, and API entitlement independently.
Current OAuth contract is unknown Stop before provisioning and obtain current org-specific documentation.

Example

A redacted completion receipt might look like this:

org=sandbox; app=external-client-app; flow=org-approved; scopes=least-privilege; probe=read-only-pass; secrets=referenced

Resources

Next Steps

Run the workflow first in the lowest-risk authorized org and preserve its redacted receipt. Schedule a review against the next Salesforce seasonal release and the customer change calendar.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides a secure and standard way to configure Salesforce authentication. It follows security best practices by using environment variables for credentials, provides clear warnings against committing secrets, and utilizes well-known, legitimate SDKs and official CLI tools.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 2 months ago
What it can do
Reads files Network Edits files
Modelinherit
argument-hint
[org-alias] [integration-purpose]
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "salesforce",
  "authentication",
  "oauth",
  "external-client-app"
]
model
inherit
effort
high
compatibility
Designed for Claude Code; identity and client-app changes require Salesforce org owner and security approval

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/salesforce-install-auth