Skip to content
Back to skills

Salesforce Crm Query

ASecurity

List objects, describe schema, run SOQL queries

  • 9 stars
  • 0 votes
  • 0 copies
  • 5 views
  • Added May 26, 2026
databasesapi

Works with

  • api
  • mcp

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add djinilabs/helpmaton --skill salesforce-crm-query --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Salesforce Crm Query?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Salesforce Crm Query
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/djinilabs-salesforce-crm-query/badge)](https://www.skillsdirectory.com/skills/djinilabs-salesforce-crm-query)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
id: salesforce-crm-query
name: Salesforce CRM Query
description: List objects, describe schema, run SOQL queries
role: sales
requiredTools:
  - type: mcpService
    serviceType: salesforce
---

## Salesforce CRM Query

When querying Salesforce data:

- Use **salesforce_list_objects** (tool name may have a suffix if multiple Salesforce servers exist) to discover standard and custom objects in the org.
- Use **salesforce_describe_object** to get fields and relationships for an object before querying.
- Use **salesforce_query** to run SOQL queries (read-only); build queries from the described schema.
- Follow a discovery-first workflow: list objects -> describe object -> query. All tools are read-only.
- Summarize records clearly; cite object and key fields; avoid dumping raw result sets unless asked.

## Step-by-step instructions

1. When the user asks about "accounts", "contacts", or an object name: if unsure of the exact API name, call **salesforce_list_objects** to find it.
2. Before running a query: call **salesforce_describe_object** for that object to get field names and types so the SOQL query uses valid fields.
3. Call **salesforce_query** with a SOQL string (e.g. SELECT Id, Name FROM Account LIMIT 10); use only fields from the describe result.
4. Summarize the returned records (count, key fields); for large result sets, summarize and offer to narrow.
5. Salesforce uses instance_url from the token; the tools use the correct instance automatically.

## Examples of inputs and outputs

- **Input**: "List recent accounts."  
  **Output**: Short list of Account records (Id, Name, and other requested fields) from **salesforce_query** with a SOQL like SELECT Id, Name FROM Account ORDER BY CreatedDate DESC LIMIT 10.

- **Input**: "What fields does the Contact object have?"  
  **Output**: List of field names and types from **salesforce_describe_object** for Contact; summarize key fields (e.g. Name, Email, AccountId).

## Common edge cases

- **Object not found**: Say "Object [name] not found" and suggest listing objects or checking the API name (e.g. custom objects have __c).
- **Invalid SOQL**: If the query fails, check field names against **salesforce_describe_object** and retry; report the error to the user.
- **Large result set**: SOQL has limits; summarize the first page and mention limits; do not assume all records were returned.
- **API/OAuth error**: Report that Salesforce returned an error and suggest reconnecting or retrying; ensure instance_url is used (handled by the integration).

## Tool usage for specific purposes

- **salesforce_list_objects**: Use when the user asks about "objects" or when you need to resolve an object API name.
- **salesforce_describe_object**: Use before building a SOQL query to get valid field names and types.
- **salesforce_query**: Use to run read-only SOQL; always use fields from describe; include LIMIT and ORDER BY as appropriate.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.