# Dx Pkg Post Install Configure

Use this skill to automate managed package post-install configuration.

- Repository: https://github.com/forcedotcom/sf-skills (1134 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add forcedotcom/sf-skills --skill dx-pkg-post-install-configure -g -a claude-code -y`
Codex: `npx skills add forcedotcom/sf-skills --skill dx-pkg-post-install-configure -g -a codex -y`
Cursor: `npx skills add forcedotcom/sf-skills --skill dx-pkg-post-install-configure -g -a cursor -y`
Gemini CLI: `npx skills add forcedotcom/sf-skills --skill dx-pkg-post-install-configure -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add forcedotcom/sf-skills`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## 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:

```bash
sf org display --target-org <alias> --json
```

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:

```bash
sf api request rest "/services/data/v<apiVersion>/tooling/query?q=SELECT+Id,DeveloperName,MasterLabel+FROM+McpServerAccess" --target-org <alias>
```

#### 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 | `mcp__sf-sobject-all__` |
| Sandbox | `mcp__sf-sobject-all-sb__` |
| Falcon Test (pc-rnd) | `mcp__sf-sobject-all-falcon__` |

The rest: https://github.com/forcedotcom/sf-skills/blob/HEAD/plugins/builder/dx-org-lifecycle/skills/dx-pkg-post-install-configure/SKILL.md