sf-soql

Describe the target object, fields, filters, and sort or limit needs in plain English, and the Skill generates the simplest correct SOQL. It selects the right shape—subquery, dot-notation traversal, aggregate, or semi-join—based on the relationship direction and data volume.

Add an indexed field such as Id, Name, OwnerId, CreatedDate, or RecordTypeId to the WHERE clause so the filter returns under 10% of records. Avoid leading wildcards, negative operators, null checks, and formula fields in filters, which force full table scans.

Yes. Use sf data query with the --use-tooling-api and --plan flags, or call the REST explain endpoint via sf api request. The Skill's validation hook can also run live query plan analysis automatically when an org is connected.

This error occurs when code accesses a field that was not included in the SELECT clause, including parent relationship fields like Account.Name. The fix is to add every accessed field—direct, relationship, or dynamic—to the query before use.

Use SOSL for text search across multiple objects or fields, such as finding a term in Accounts, Contacts, and Leads simultaneously. Use SOQL when querying a single object with structured filters, relationships, or aggregates.

Synchronous transactions allow 100 SOQL queries and 50,000 retrieved records; asynchronous contexts allow 200 queries. Additional limits include 2,000 maximum OFFSET, 20 subqueries, and 5 levels of parent relationship traversal.