Agent skill · forcedotcom
dx-pkg-post-install-configure
Use this skill to automate managed package post-install configuration. Package-agnostic — works with any managed package (LMA, FMA, work.com, Certinia, etc.). TRIGGER when: user installs a managed package and needs post-install configuration, mentions LMA/FMA/work.com post-install setup, asks to configure permission sets/FLS/page layouts for an installed package, says 'post-install', 'package setup', 'configure LMA', 'set up FMA', 'post-install steps'. DO NOT TRIGGER for: standalone permission set assignment (use dx-org-permission-set-assign), generating permission set metadata XML (use platform-permission-set-generate), package installation, or org switching.
What it needs
About 4k tokens when loaded.
What this skill does
When to Use This Skill Use when automating post-install configuration for any Salesforce managed package. This skill reads the package's post-install documentation, discovers available execution methods, and automates the configuration steps — including permission sets, object/field permissions, page layouts, Visualforce page access, and tab settings. Input Required: Package name (e.g., LMA, FMA, work.com) Optional: Path to post-install doc (PDF, markdown, URL) If no doc is provided, ask the user to supply it. Workflow Execute phases in order. Each phase must pass before proceeding. --- Phase 1: Discover Available Execution Methods Priority order: 1. Org-native platform MCP servers (highest — direct org access via Headless 360) 2. Claude Code external MCP servers (sf-sobject-all, sf-sobject-all-sb, etc.) 3. sf CLI fallback (always available if authenticated) Step 1A: Resolve org API version Discover the org's current API version dynamically — never hardcode a version number: From the JSON response, read result.apiVersion (e.g., "67.0"). Store this value and use it as v<apiVersion> in all subsequent REST paths. If the command fails, fall back to the minApiVersion declared in this skill's metadata (67.0). Step 1B: Check for org-native platform MCP servers Query the Tooling API for MCP server availability: Step 1C: Determine execution method Check which Claude Code MCP tools are available and authenticated. MCP tool prefixes by org type: Org Type Tool Prefix --- --- Production mcpsf-sobject-all Sandbox mcpsf-sobject-all-sb Falcon Test (pc-rnd) mcpsf-sobject-all-falcon If MCP needs auth, call the authenticate tool. If auth fails, fall back to sf CLI. --- Phase 2: Verify Authentication & Org Identity 1. Run a lightweight test query (SELECT Id, Name, IsSandbox FROM Organization) 2. If MCP auth fails, automatically fall back to sf CLI 3. Display org info and ask user to confirm before proceeding --- Phase 3: Verify Package Installation 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/dx-pkg-post-install-configure--6382d6