sf-connected-apps

Automate Salesforce Connected App and External Client App creation with security scoring.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/dcinzona/folios --skill sf-connected-apps-dcinzona
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sf-connected-apps
Source: https://github.com/dcinzona/folios/tree/main/.agents/skills/sf-connected-apps
Command: npx skills add https://github.com/dcinzona/folios --skill sf-connected-apps-dcinzona

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Teams and engineers struggle to design, harden, and migrate Salesforce OAuth applications safely across orgs while respecting metadata conventions, secret handling, and modern security controls. This Skill centralizes templates, scoring, and migration guidance so integrations are deployable, auditable, and secure.

Core Features & Use Cases

  • Templates & Metadata: Ready-to-use Connected App and External Client App (ECA) XML templates for common flows including JWT, PKCE, and full OAuth configurations.
  • Security Scoring & Checklist: A 120-point validator and actionable checklist to harden scopes, callbacks, token policies, and certificate/rotation strategies.
  • Migration & Deployment Guidance: Step-by-step migration plans, file naming conventions, deploy/retrieve commands, and post-deploy verification for migrating Connected Apps → ECAs.
  • Use Case Examples: Generate CI/CD JWT apps, PKCE-enabled mobile ECAs, or review existing .connectedApp-meta.xml and .eca-meta.xml files for security remediation.

Quick Start

Use the sf-connected-apps skill to generate or review Connected App or External Client App metadata, pick an OAuth flow (e.g., PKCE or JWT), and produce deployable XML files with a security score and migration checklist.

Frequently Asked Questions about sf-connected-apps

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Salesforce Connected App metadata file for a JWT OAuth flow?

To create a Salesforce Connected App for a JWT OAuth flow, you generate a metadata-ready .connectedApp-meta.xml template configured with certificate settings and appropriate scopes. This process outputs deployable XML files aligned with Salesforce metadata conventions.

What is the best way to migrate a Salesforce Connected App to an External Client App?

Migrating a Salesforce Connected App to an External Client App involves following a step-by-step migration plan to generate .eca-meta.xml files. This provides updated metadata templates, deploy commands, and post-deployment verification steps for the new ECA format.

How do I configure PKCE for a Salesforce External Client App?

You configure PKCE for a Salesforce External Client App by selecting the authorization code flow with PKCE when generating the .eca-meta.xml template. This yields a metadata-ready configuration with secure callback URLs and scoped token policies for mobile or web clients.

Can I validate the security of my existing Salesforce .connectedApp-meta.xml files?

Yes, you can validate existing .connectedApp-meta.xml files by running a 120-point security score review. This analyzes OAuth scopes, callback URLs, and token policies to produce an actionable checklist for security remediation and hardening.

When do I need an External Client App instead of a Connected App in Salesforce?

You need an External Client App instead of a Connected App when modernizing OAuth integrations for external clients like mobile or CI/CD JWT applications. This migration provides updated metadata formats and enhanced security controls for token lifecycle management.

Does the Salesforce Connected App security scoring check OAuth token policies and certificate rotation?

Yes, the 120-point security scoring evaluates OAuth token policies, scopes, and certificate rotation strategies. This generates an actionable checklist to harden your Connected App or External Client App configuration against unauthorized access.