Salesforce Metadata Discovery

Before you create metadata, change it, or write code that references it, know what already exists in the org. This skill picks the tool for each question. Metadata grounding finds metadata by meaning when you do not know its name. It needs Salesforce Catalog and a connected grounding server, and many orgs and setups have neither. Every other route works with the sf CLI alone.

Skip discovery when the request only changes local files and adds no new references to org metadata.

Check What You Have

Do this once per session, before the first lookup.

1. The CLI and its org. Run sf org display --json to see the default org and its id. If no org is authenticated, ask the user to run sf org login web and wait. If you cannot run commands at all, read references/h360-routes.md.
2. Grounding servers. Note whether the Metadata Grounding MCP (tools search_metadata, query_metadata, describe_metadata) or the Salesforce MCP is connected. The Salesforce MCP is shown in Setup today as the Headless360 (H360) MCP Server. Its tools are describe, dispatch, and dispatch_readonly, which are different from the Metadata Grounding MCP tools.
3. One org. Grounding identifiers start with the 18-character org id. If it differs from the id in sf org display, tell the user and ask which org to use before you combine results.

Route by Intent