verify-platform-capabilities

Verifies BPO entity.xml files against a 79-point Salesforce platform capabilities checklist.

Updated Aug 6, 2026
One-click install
npx skills add https://github.com/salesforce-misc/ManuAssist --skill verify-platform-capabilities-salesforce-misc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-platform-capabilities
Source: https://github.com/salesforce-misc/ManuAssist/tree/main/skills/verify-platform-capabilities
Command: npx skills add https://github.com/salesforce-misc/ManuAssist --skill verify-platform-capabilities-salesforce-misc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually auditing a Salesforce BPO (Base Platform Object) entity.xml for missing platform capabilities is error-prone and slow, since required attributes span access control, sharing, UI, licensing, and upgrade actions across many files. This Skill walks through a structured 79-point verification checklist and produces a complete gap report. ## Core Features & Use Cases - 79-Point Verification: Checks 79 capabilities grouped into 15 sections, from org/user access and FLS to related lists, UI API allowlisting, and upgrade action providers. - Top-Level vs Child Entity Logic: Distinguishes entity types via the platformEntity tag so child entities with access delegates are not falsely flagged for issues like enforcedByCRUD user access. - Three-Part Report Output: Generates a capabilities matrix, a missing capabilities analysis with priorities, and a prioritized action items list including PO-decision items. - Use Case: A Salesforce platform engineer finalizing a new module's entity.xml invokes the skill to confirm FLS, sharing model, tab registration, licensing ULD entries, and upgrade actions are all configured before release. ## Quick Start Ask the assistant to verify the platform capabilities of the entity.xml file in your UDD package directory.

Frequently Asked Questions about verify-platform-capabilities

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

FAQPage Schema
How do I verify Salesforce BPO entity platform capabilities?

Invoke this skill against the UDD package containing your entity.xml. It reads the entity file plus related settings.xml, module.xml, and Java sources, then walks through 79 checks and reports each capability as enabled, missing, partial, or N/A.

What does the entity capabilities verification report include?

The report has three parts: a platform capabilities matrix table per entity, a missing capabilities analysis with priority levels, and a consolidated action items list grouped by High, Medium, PO Decision, and Low priority.

Does the checklist handle child entities differently from top-level entities?

Yes. The skill inspects the platformEntity tag for isTopLevel and MASTERDETAIL fields. Child entities with cudAccessDelegate are expected to use enforcedByCRUD user access, which is only flagged as a revenue leakage risk on top-level entities.

Which files are checked besides entity.xml during verification?

The skill also reads settings.xml for sharing and licensing, module.xml for entity tabs, Java sources for upgrade action providers and logging, plus global configs like UI API allowlists, motif.xml, actions.xml, and licensing ULD metadata files.

Why is userAccess enforcedByCRUD flagged on some entities?

On top-level entities, userAccess set to External.enforcedByCRUD bypasses permission checks and creates a revenue leakage risk. On child entities with a cudAccessDelegate it is expected behavior controlled by the parent entity.