With the Elements MCP (Model Context Protocol) server connected, you can ask your AI assistant questions about your Salesforce Org in plain language, inside the tools you already use. Elements skills turn each request into the right Elements action, so you get an answer instead of digging through screens. This article lists the 15 Elements skills available today, with an example prompt for each.

You don't need special commands: each skill recognizes the kind of question you're asking. If your assistant has the Elements skills installed, you can also call a skill by name, using the slash form shown with each example (or $ in Codex, for example $elements-spaces).

Ask your assistant which Elements Space it's using, switch it to another Space, or create a new Space for a project.

"What Space are you working in right now? Switch to the Acme Corp space." Or directly: /elements-spaces switch to Acme Corp
​

Ask about a specific object, field, flow, trigger or Apex class: what it is, what it depends on, and what it does.

"What does the LoyaltyPointsFlow do, and what does it depend on?" Or directly: /elements-metadata LoyaltyPointsFlow
​

Ask which Profiles, Permission Sets, Permission Set Groups or Groups can read or edit a field or object, and how many users each one reaches.

"Who can edit the Credit Limit field on Account, and how many people does each permission reach?" Or directly: /elements-access Credit Limit on Account
​

Ask for a filtered list of metadata that matches specific criteria, and save it as a named, reusable view.

"List every screen flow still on an old API version, and save that as a view called 'Flows to upgrade.'" Or directly: /elements-metadata-query screen flows on old API versions
​

Ask for a full health check of your org (structure, automation, technical debt, compliance and governance) in one pass, with a ranked summary of where to look first.

"Run a health check on my org and tell me where to look first." Or directly: /elements-org-diagnostic
​

Ask what changed in your org over a period, broken down by metadata type, with unusual spikes and bursts of automation changes flagged.

"What changed in my org this week, and was anything unusual?" Or directly: /elements-change-briefing last 7 days
​

Ask for a ranked list of what to fix or remove first, based on risk, how many other components depend on each item, and how recently it changed.

"What should I clean up first, and why?" Or directly: /elements-tech-debt
​

Ask your assistant to scan your whole Org for places where an Agentforce agent would pay off, ranked with the evidence behind each.

"Scan my Org and tell me the top few places we should use an Agentforce agent." Or directly: /elements-agent-opportunities
​

Ask what it would take to uninstall a managed package. Elements inventories the package's components, finds what depends on them, separates real blockers from references that disappear with the package, and returns a step-by-step removal plan, from resolving blockers through a sandbox dry run to checks after removal. Elements only plans the removal; you do the uninstall.

"What would it take to remove the Consensus package from our org?" Or directly: /elements-package-uninstall Consensus
​

Ask for a view across every Salesforce org in your Space. Elements lists the orgs, asks you to confirm them, runs the same query against each, and produces a self-contained HTML report you can send to someone with no Elements access. Every number traces back to the data that produced it, and each org shows when it last synced, so an org that has stopped syncing is flagged rather than averaged in. An inventory report is included, and you can describe the report you want. Each run saves a dated snapshot, so running it again later shows a trend.

This skill needs an AI assistant that can run Python, because a script builds the report, which keeps the numbers reproducible.

"Give me an overview of our Salesforce orgs." Or directly: /elements-multi-org-analytics
​

Ask your assistant to set up MetaFields, the custom fields your Space uses to classify Salesforce metadata, connect dependent picklists, populate values in bulk, and check the result. Narrowing a MetaField or removing options can remove values already set, so your assistant counts what would be affected first.

"Set up a retention-priority MetaField for our objects, classify them, and verify the result." Or directly: /elements-metafields classify our objects by retention priority
​

Ask for the process behind a lifecycle object such as Opportunity, Case or Lead. Your assistant builds it from the org's actual record types, lifecycle fields and automations rather than a generic template, with one diagram per record type.

"Show me the Case process." Or directly: /elements-org-to-process Case
​

Ask how best to add or change Salesforce automation, objects, fields or record types. The Decision Engine inventories what already exists and recommends approaches. Once you pick one, it analyzes the impact and drafts a delivery backlog of requirements and user stories, which stay drafts for you to review.

"We want Cases auto-assigned by region. What's the best way to build it and what would it affect?" Or directly: /elements-decision-engine
​

Ask your assistant to turn a description, transcript or images into a UPN (Universal Process Notation) process map, or to read and edit an existing diagram. Edited diagrams are saved as drafts for you to review and release in Elements.

"Turn this onboarding call transcript into a process map, then add an approval step before go-live." Or directly: /elements-diagrams

Ask your assistant to list the user stories in a Space, or to generate stories from the activities on a process map, each with a headline, description and acceptance criteria.

"Generate user stories from the activities on this onboarding diagram." Or directly: /elements-stories

Playbooks are separate plugins that run a complete Salesforce process end to end, such as removing unused Apex. See What is an MCP playbook? to learn how they work and how to install one. Elements adds new skills and playbooks as they ship.

Your assistant can't use an Elements skill when the tools behind it aren't available in your authorized Spaces, because of their plan, licences or your role. Tools that none of your Spaces makes available are hidden entirely. After a licensing change, start a new conversation so your assistant picks up the updated tool list.

Elements skills can't change your Salesforce org. They read the metadata Elements has synced, and anything they create, such as a view, MetaField value, diagram or user story, stays inside Elements.