Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jaganpro avatar

Sf Soql

  • 34 installs
  • 423 repo stars
  • Updated April 27, 2026
  • jaganpro/claude-code-sfskills

This is a copy of sf-soql by jaganpro - installs and ranking accrue to the original listing.

Helps with ai & agent building tasks.

About

sf-soql is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

  • sf-soql
  • AI & Agent Building
  • AI-coding skill

Sf Soql by the numbers

  • 34 all-time installs (skills.sh)
  • Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jaganpro/claude-code-sfskills --skill sf-soql

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs34
repo stars423
Last updatedApril 27, 2026
Repositoryjaganpro/claude-code-sfskills

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

sf-soql: Salesforce SOQL Query Expert

Use this skill when the user needs SOQL/SOSL authoring or optimization: natural-language-to-query generation, relationship queries, aggregates, query-plan analysis, and performance/safety improvements for Salesforce queries.

When This Skill Owns the Task

Use sf-soql when the work involves:

  • .soql files
  • query generation from natural language
  • relationship queries and aggregate queries
  • query optimization and selectivity analysis
  • SOQL/SOSL syntax and governor-aware design

Delegate elsewhere when the user is:

  • performing bulk data operations → sf-data
  • embedding query logic inside broader Apex implementation → sf-apex
  • debugging via logs rather than query shape → sf-debug

---

Required Context to Gather First

Ask for or infer:

  • target object(s)
  • fields needed
  • filter criteria
  • sort / limit requirements
  • whether the query is for display, automation, reporting-like analysis, or Apex usage
  • whether performance / selectivity is already a concern

---

Recommended Workflow

1. Generate the simplest correct query

Prefer:

  • only needed fields
  • clear WHERE criteria
  • reasonable LIMIT when appropriate
  • relationship depth only as deep as necessary

2. Choose the right query shape

NeedDefault pattern
parent data from childchild-to-parent traversal
child rows from parentsubquery
counts / rollupsaggregate query
records with / without related rowssemi-join / anti-join
text search across objectsSOSL

3. Optimize for selectivity and safety

Check:

  • indexed / selective filters
  • no unnecessary fields
  • no avoidable wildcard or scan-heavy patterns
  • security enforcement expectations

4. Validate execution path if needed

If the user wants runtime verification, hand off execution to:

  • sf-data

---

High-Signal Rules

  • never use SELECT * style thinking; query only required fields
  • do not query inside loops in Apex contexts
  • prefer filtering in SOQL rather than post-filtering in Apex
  • use aggregates for counts and grouped summaries instead of loading unnecessary records
  • evaluate wildcard usage carefully; leading wildcards often defeat indexes
  • account for security mode / field access requirements when queries move into Apex

---

Output Format

When finishing, report in this order: 1. Query purpose 2. Final SOQL/SOSL 3. Why this shape was chosen 4. Optimization or security notes 5. Execution suggestion if needed

Suggested shape:

Query goal: <summary>
Query: <soql or sosl>
Design: <relationship / aggregate / filter choices>
Notes: <selectivity, limits, security, governor awareness>
Next step: <run in sf-data or embed in Apex>

---

Cross-Skill Integration

NeedDelegate toReason
run the query against an orgsf-dataexecution and export
embed the query in services/selectorssf-apeximplementation context
analyze slow-query symptoms from logssf-debugruntime evidence
wire query-backed UIsf-lwcfrontend integration

---

Reference Map

Start here

  • references/soql-syntax-reference.md
  • references/query-optimization.md
  • references/cli-commands.md

Specialized guidance

  • references/soql-reference.md
  • references/anti-patterns.md
  • references/selector-patterns.md
  • references/field-coverage-rules.md
  • assets/

---

Score Guide

ScoreMeaning
90+production-optimized query
80–89good query with minor improvements possible
70–79functional but performance concerns remain
< 70needs revision before production use

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.