Agent skill · software engineering · jeremylongshore
salesforce-hello-world
Verify a Salesforce org connection with version discovery, identity evidence, and a read-only resource probe before previewing any mutation. Use when running first connections and smoke tests. Trigger with "test Salesforce safely".
Why this skill is useful
Provides specific SOQL query patterns and CRUD operations for Salesforce that the AI wouldn't reliably generate on its own.
What it needs
Requires jsforce 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 Read-Only Capability Proof Overview Prove the selected principal, org, API version, object entitlement, and field visibility before any record mutation is considered. Prerequisites An authorized non-production org and secret reference Expected org identity, principal, object, fields, and business owner Current REST API and authorization 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 The REST Versions resource lets a client discover versions instead of hard-coding one. Resources, objects, fields, CRUD, sharing, and limits remain org- and principal-specific. Authentication Use the approved OAuth client and principal from the onboarding decision. Keep access and refresh tokens out of commands, files, prompts, logs, screenshots, and receipts. Instructions 1. Record the expected org, environment, principal, My Domain, object, fields, and success criteria. 2. Resolve credentials only through the approved secret mechanism and verify the returned org identity. 3. List supported REST versions and select a supported version allowed by the customer contract. 4. Discover available resources, then inspect object metadata and field accessibility for the intended read. 5. Run one bounded read-only query with non-sensitive fields and an explicit row limit. 6. Preview any proposed create or update with validation, duplicate, automation, ownership, and rollback effects. 7. Return a redacted receipt and request separate approval before executing a mutation. Approval Boundaries Do not create, update, delete, undelete, merge, or expose records during the proof. Any mutation requires object-owner approval and a recoverable test case. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesforce-hello-world--f701de