forcedotcom/sf-skills / plugins/builder/integration/skills/integration-connectivity-generate
integration-connectivity-generate
VerifiedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use integration-connectivity-connected-app-configure), Apex-only logic (use platform-apex-generate), data import/export (use platform-data-manage), or CDC channel-membership metadata such as PlatformEventChannel, PlatformEventChannelMember, or EnrichedField (use integration-eventing-cdc-configure).
assets/external-credentials/oauth-external-credential.externalCredential-meta.xml
View on GitHub<?xml version="1.0" encoding="UTF-8"?>
<!--
External Credential Template: OAuth 2.0 (API 61+)
Use Case: Modern OAuth 2.0 with Named Principal or Per-User authentication
- New integrations (recommended over legacy Named Credentials)
- APIs requiring per-user context
- Fine-grained permission control via Permission Sets
API Version: 61.0+ (Spring '24+) REQUIRED
Key Concepts:
- External Credential: Defines auth protocol and parameters
- Named Principal: Shared service account identity
- Per-User Principal: Individual user authentication
- Permission Set: Controls access to principals
Setup Steps:
1. Replace all {{placeholder}} values
2. Deploy to org
3. Create Named Credential referencing this External Credential
4. Assign Permission Set to users
File Location: force-app/main/default/externalCredentials/{{CredentialName}}.externalCredential-meta.xml
-->
<ExternalCredential xmlns="http://soap.sforce.com/2006/04/metadata">
<label>{{CredentialLabel}}</label>
<!-- Authentication Protocol: Oauth, Custom, NoAuth, JWT, JwtExchange -->
<authenticationProtocol>Oauth</authenticationProtocol>
<!--
OAuth Parameters
These define how Salesforce obtains and refreshes tokens
-->
<externalCredentialParameters>
<parameterName>clientId</parameterName>
<parameterType>AuthProviderClientId</parameterType>
<parameterValue>{{ClientId}}</parameterValue>
</externalCredentialParameters>
<externalCredentialParameters>
<parameterName>clientSecret</parameterName>
<parameterType>AuthProviderClientSecret</parameterType>
<!-- Value entered via UI for security -->
</externalCredentialParameters>
<externalCredentialParameters>
<parameterName>scope</parameterName>
<parameterType>AuthProviderScope</parameterType>
<parameterValue>{{Scopes}}</parameterValue>
</externalCredentialParameters>
<externalCredentialParameters>
<parameterName>tokenEndpoint</parameterName>
<parameterType>AuthProviderTokenEndpoint</parameterType>
<parameterValue>{{TokenEndpoint}}</parameterValue>
</externalCredentialParameters>
<!--
Named Principal Configuration
Shared service account for all users with permission
-->
<principals>
<principalName>{{PrincipalName}}</principalName>
<principalType>NamedPrincipal</principalType>
<sequenceNumber>1</sequenceNumber>
</principals>
<!--
Optional: Per-User Principal
Each user authenticates individually
<principals>
<principalName>PerUserPrincipal</principalName>
<principalType>PerUserPrincipal</principalType>
<sequenceNumber>2</sequenceNumber>
</principals>
-->
<!--
Permission Set Integration:
After deployment, create Permission Set with:
- External Credential Principal Access: {{PrincipalName}}
- Assign to users who need API access
-->
</ExternalCredential>
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |