- Home
- Skills
- Agents & Orchestration
- Salesforce Org Health Check
Works with the AI Agents you already use
Salesforce Org Health Check
Automated Salesforce health and security audits via SF CLI with prioritized findings and remediation reports.
$12
Salesforce Org Health Check
Example session with this skill installed
Run a health check on my 'dev-hub' org. Focus on security and limits. Identify any users who haven't logged in for 90 days.
- Read your context and instructions
- Compiled the salesforce org health
I have completed the health check for the Salesforce org 'dev-hub' (Sandbox on instance CS192). The audit focused on security and resource limits as requested.
Salesforce Org Health Report: dev-hub
Scorecard
| Area | Status | Findings |
|---|---|---|
| Security | Action | 2 HIGH, 1 MEDIUM |
| Limits | OK | 0 HIGH, 0 MEDIUM |
| Licenses | Watch | 3 MEDIUM |
| Apex Jobs | OK | 0 HIGH |
Top Findings
- HIGH: Excessive Admin Permissions
- Finding: 5 non-admin users have 'Modify All Data' assigned via Permission Sets.
- Fix: Review and remove 'Modify All Data' from non-system-administrator profiles.
- HIGH: Dormant Users
- Finding: 12 users have not logged in for over 90 days.
- Fix: Deactivate users
jdoe.dev,asmith.dev, and 10 others to secure access and reclaim licenses.
- MEDIUM: API Limit Usage
- Finding: Daily API Requests are at 78% of the 100,000 limit.
- Fix: Investigate the 'Integration User' login patterns to optimize batch sizes.
Details: Security & Access
Modify All Data: Found 8 total users. (Capped list: admin.user, integration.user, manager.one, dev.lead, qa.tester).
- Setup Audit Trail: No unauthorized configuration changes detected in the last 7 days.
- Login History: Total logins in last 90 days: 1,450. No suspicious IP ranges detected.
Details: Org Limits
- Data Storage: 45% used (2.2 GB / 5.0 GB)
- File Storage: 12% used (2.4 GB / 20.0 GB)
- Streaming API Events: 5% used
2 high-severity findings: see Top findings.
Next steps
- Run
sf org open --target-org dev-hubto navigate to the User list and begin deactivating dormant accounts. - Review the Permission Set assignments for the 5 users flagged with 'Modify All Data'.
- Re-run this health check in 30 days to monitor API limit trends.
Connects securely to your tools. The creator never sees your data.
About this skill
Salesforce orgs accumulate technical debt and security risks silently. This skill identifies hidden vulnerabilities and resource bottlenecks by running a comprehensive audit against your active Salesforce environment. It provides a prioritized report of limits, security gaps, and Apex failures without manual SOQL execution.
What it does
- Limits Monitoring Checks org limits and identifies resources nearing capacity.
- Security Audit Flags users with excessive permissions like "Modify All Data" and reviews login history patterns.
- Tech Debt Identification Locates dormant users, unused licenses, and failing asynchronous Apex jobs.
- License Optimization Analyzes license usage to identify potential cost savings from inactive accounts.
- Operational Health Reviews the Setup Audit Trail and Salesforce Trust incidents for systemic issues.
How it works
- Org Selection The skill identifies the target org via the Salesforce CLI, confirming whether it is a Sandbox or Production environment.
- Read-Only Execution It runs a series of predefined queries and
sfcommands covering twelve specific health areas. - Severity Scoring Results are categorized into High, Medium, and Low severity based on built-in logic or user-defined thresholds.
- Report Generation It compiles a Markdown report with a scorecard, detailed findings, and specific remediation steps.
Frameworks & tools
Salesforce CLI (sf), SOQL, Salesforce Tooling API, and Salesforce REST API.
Why this beats prompting it yourself
Writing individual SOQL queries for every health metric is time-consuming and error-prone. This skill automates the data collection, applies severity logic, and formats a professional audit report in seconds while strictly adhering to read-only security practices.
Use cases
- Pre-deployment Audits Ensure the org has enough limit headroom before a major release.
- Security Reviews Quickly identify admins or users with elevated permissions that should be revoked.
- License Cleanup Find users who have not logged in for 60+ days to reclaim expensive seats.
- Troubleshooting Investigate recurring Apex job failures or deployment bottlenecks.
Known limitations
Requires an authenticated Salesforce CLI session. Cannot perform write actions or automated fixes. High-volume login history and user lists are capped at 20 rows for readability.
Requires Salesforce CLI (sf) installed and an active authenticated session. Read-only access only; cannot apply fixes. Event Monitoring log checks require specific Salesforce edition features.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 11 days ago
Requires
Permissions
Allowed Hosts
File Scopes
Salesforce: Runs read-only SOQL queries and reads org limits through your existing Salesforce CLI login, to check limits, licenses, Apex jobs, deployments, security settings, admin access, and the setup audit trail. It never creates, updates, or deletes records, deploys metadata, runs Apex, or prints access tokens. Results depend on the logged-in user's permissions; checks it can't run are listed as skipped. api.status.salesforce.com: Public Salesforce status API, no login needed. Used to report active incidents and upcoming maintenance on your org's instance. Files: Writes the report (org-health-*.md) only when you ask for a file. Data: Query results stay in your agent session. Reports name people by name and username only, never emails, IP addresses, or login locations.