# Salesforce Capabilities Catalog

> Canonical Salesforce capability taxonomy with acronyms, domains, and baseline definitions for enterprise architecture mapping. Use when the user asks to classify, normalize, map, or compare Salesforce business capabilities.

- Skill: `afisher-salesforce/salesforce-capabilities-catalog` (Agent Skill)
- Install (CLI): `npx skillmds@latest add afisher-salesforce/salesforce-capabilities-catalog`
- Raw SKILL.md: https://api.skillmd.com/api/skills/afisher-salesforce/salesforce-capabilities-catalog/raw
- Safety review: pending (external: skill-scanner PASS, skillspector CAUTION)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: afisher-salesforce (https://skillmd.com/u/afisher-salesforce)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/afisher-salesforce/salesforce-capabilities-catalog

---


# Salesforce Capabilities Catalog

Use this skill as the reusable knowledge layer for Salesforce capability mapping.

## Deterministic Data Source

Use `reference/capabilities.json` as the primary lookup source.

Lookup order:

1. Exact acronym match in `capabilities`.
2. Exact capability name match in `capabilities`.
3. Alias normalization via `aliases`, then domain-filtered name match.

If no match is found, return `UNMAPPED` and suggest the nearest capability as an assumption.

## What this skill provides

1. Normalized capability naming by domain.
2. Acronym-based lookup (for example `IEI`, `FPM`, `ARI`, `DAG`).
3. A practical domain model that blends base V1.3 cards with expert additions.

## Domain Model

Use these domains as the default grouping:

- Analytics & Reporting
- Billing
- Collaboration
- Configure-Price-Quote (CPQ)
- Data & AI
- Field Service
- Industry Solutions
- Integration
- Marketing
- Order Management
- Partner Management
- Platform & Governance
- Sales
- Service

## High-value Capability Anchors

Use these as common reference capabilities in planning outputs:

- Integration: `IEI` Enterprise Integration, `IEP` Enterprise Platform Connectors, `IAF` Agent-to-Agent Orchestration
- Field Service: `FPM` Install Base & Preventative Maintenance, `FSM` Operational Schedule Management
- Analytics: `ABI` Embedded BI & Dashboards, `ARI` Revenue Intelligence
- Data & AI: `DAG` Agentic AI / Autonomous Agents, `DDH` Data Harmonization, `DVS` Vector Search & RAG Grounding, `DEL` Einstein Trust Layer
- Collaboration: `CAF` Agentforce in Slack, `CSC` Slack Connect / External Collaboration
- Industry: `ICR` Industry Rules Engine, `IDI` Digital Engagement & Self-Service

## Output Rules

When asked to map capabilities:

1. Always output `Domain`, `Acronym`, `Capability Name`, and a one-line business outcome.
2. Preserve acronym case and exact spelling.
3. Prefer `reference/capabilities.json` terms over ad-hoc synonyms.
4. If a requested capability is unknown, return `UNMAPPED`, then propose the nearest mapped capability and flag it as an assumption.

## Additional Resource

For source provenance and planning context, read:

- `reference/capabilities.json`
- `reference/capabilities-source-notes.md`

For interaction design and UX behavior (including the floating search results card pattern), defer to:

- `salesforce-capabilities-strategy`