org-health-assessment

Assess Salesforce org health across security, automation, permissions, licenses, and data volumes.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/jterratsdev/smart-deployment --skill org-health-assessment-jterratsdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: org-health-assessment
Source: https://github.com/jterratsdev/smart-deployment/tree/main/.setup-agents/skills/org-health-assessment
Command: npx skills add https://github.com/jterratsdev/smart-deployment --skill org-health-assessment-jterratsdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Auditing a Salesforce org manually is error-prone: partial metadata retrieves silently omit types, grep matches get mistaken for findings, and runtime data like licenses and data volumes never appear in metadata at all. This Skill enforces a grounded, two-pronged assessment method so every conclusion traces back to a full retrieve or an explicit org query. ## Core Features & Use Cases - Two-pronged grounding: Combines a full metadata retrieve (manifest generated from the org) with live read-only queries for licenses, limits, and large data volumes, with every gap explicitly declared. - Ten domain checklists: Covers security and identity, permission architecture, automation conflicts, data-model integrity, schema limits and headroom, license utilization, LDV, metadata governance, managed packages, and operational best practices. - Purpose-driven framing: Supports failed-implementation diagnostics, brownfield onboarding baselines, and pre-go-live readiness gates with the same criteria but different output framing. - Use Case: Before onboarding onto an unfamiliar Salesforce org, run the assessment to get a baseline of the automation order of execution, sharing model, permission architecture, and license headroom, with every number linked to the query that produced it. ## Quick Start Assess the health of my connected Salesforce org, starting with a full metadata retrieve and license usage queries, and report findings per domain with any coverage gaps declared.

Frequently Asked Questions about org-health-assessment

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

FAQPage Schema
How do I audit the health of a Salesforce org?

Run a full metadata retrieve generated from the org's own manifest, then run live read-only queries for licenses, limits, and record counts. Assess each domain (security, automation, permissions, data model, LDV) against minimum criteria and declare any coverage gaps explicitly.

How to check Salesforce license utilization and headroom?

Query UserLicense, PermissionSetLicenseAssign, and PackageLicense objects with sf data query to get used versus allocated counts per license type. Report results as used versus ceiling with headroom, always linked to the exact query that produced the numbers.

Why does a Salesforce metadata retrieve miss some metadata types?

A retrieve runs with the connected user's effective permissions and silently omits types that user cannot read, while still reporting success. Verify permissions like View Setup, Modify Metadata, and Author Apex up front, since System Administrator profile alone may not include required permission sets.

Can I detect Salesforce automation conflicts across Flows, Process Builder, and Apex triggers?

Yes, by building a per-object automation inventory across all tools from the retrieved metadata. Multiple active tools on the same object indicate conflict risk such as recursion, clobbered field updates, and unpredictable order of execution.

What are the limitations of grep-based Salesforce org analysis?

Grep only locates where a setting exists; it cannot read the setting's value or answer runtime questions like license usage and data volumes. A match is a locator, not a finding, so conclusions require reading retrieved values and running live org queries.