sf-connected-apps

Use this skill when the user needs OAuth app configuration in Salesforce: Connected Apps, External Client Apps (ECAs), JWT bearer setup, PKCE decisions, scope design, or migration from older Connected App patterns to newer ECA patterns. Use sf-connected-apps when the work involves: Delegate elsewhere when the user is: Default guidance: Ask for or infer: Decide whether a Connected App or ECA is the better long-term fit. Use the provided assets instead of building from scratch: If you need source-controlled ECA OAuth security metadata, retrieve it from an org first and treat the retrieved file as the schema source of truth: Favor: Before handoff, confirm: Avoid these anti-patterns: Default fix direction: Usually lives under: Current source-supported ECA metadata uses multiple top-level source directories, not a single externalClientApps/ folder: Important file-name gotchas: When finishing, report in this order: Suggested shape: - .connectedApp-meta.xml or .eca-meta.xml files - OAuth flow selection and callback / scope setup - JWT bearer auth, device flow, client credentials, or auth-code decisions - Connected App vs External Client App architecture choices - consumer-key / secret / certificate handling strategy - configuring Named Credentials or runtime callouts → sf-integration - analyzing access / permission policy assignments → sf-permissions - writing Apex token-handling...