salesforce-query
Skill10 starsChanged 29 days agoApache-2.0View on GitHub
Helps construct and execute SOQL queries against Life Sciences Cloud (LSC) orgs. Use when user needs to query data, check configurations, or explore the LSC data model in their Salesforce org.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- amyfilsinger/team-skillstheir own version, first seen Apr 23, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- amyfilsinger/team-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository39 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- roz-uiSkill
- lsc-account-managementSkill
- lsc-activity-planSkill
- lsc-agentforceSkill
- lsc-app-alertsSkill
- lsc-briefingsSkill
- lsc-calendar-tot-routineSkill
- lsc-config-migrationSkill
- lsc-consent-managementSkill
- lsc-custom-scriptsSkill
- lsc-data-migrationSkill
- lsc-data-modelSkill
- lsc-db-schemaSkill
- lsc-demo-data-loadingSkill
- lsc-events-managementSkill
- lsc-field-emailSkill
- lsc-health-checkSkill
- lsc-home-page-configurationSkill
- lsc-implementation-reviewSkill
- lsc-implementationSkill
- lsc-integration-patternsSkill
- lsc-intelligent-contentSkill
- lsc-key-account-managementSkill
- lsc-lists-filtersSkill
- lsc-mobile-app-settingsSkill
- lsc-mobile-validationSkill
- lsc-next-bestSkill
- lsc-performance-validationSkill
- lsc-product-managementSkill
- lsc-provider-engagement-complianceSkill
- lsc-quick-actions-configurationSkill
- lsc-reporting-analyticsSkill
- lsc-sample-managementSkill
- lsc-surveysSkill
- lsc-territory-alignmentSkill
- lsc-troubleshootSkill
- lsc-user-managementSkill
- lsc-visit-managementSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 66
NEVER use
run_soqlfor compact layouts: Use retrieve_metadata to fetch compact layout metadata, or use the Tooling API with a query like: - Distinctive: line 74
Start with small LIMIT values to test queries
- Very specific: line 75
Use describe_sobject liberally - don't assume field names
- Distinctive: line 77
Check the Admin Console documentation for feature-specific object relationships
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
For LSC-specific query guidance, call search_lsc_knowledge({ query: "<topic>" }) to get sourced documentation about the relevant objects and fields.
Salesforce Query Assistant for LSC
You help users query and explore their LSC Salesforce orgs.
Before Querying
- Check setup status with
check_lsc_setupto ensure:- Salesforce CLI is installed
- User is authenticated to an org
- Target org is set
- If not set up, guide through:
- Installing SF CLI with
install_sf_cli - Authenticating:
sf org login web --alias my-lsc-org - Setting target with
set_target_org
- Installing SF CLI with
Important: Discover Object Names First
LSC object API names vary by implementation and package version. Always use describe_sobject to verify object and field names before writing queries.
Common objects to explore:
Account- HCPs and HCOs (often PersonAccount)Visitor similar - Visit recordsProduct2- Products- Territory-related objects
Query Workflow
- Ask user what data they need
- Use
describe_sobjectto find the correct object and field names - Build the query using discovered field names
- Execute with
run_soql - Iterate if needed
Example Workflow
User: "Show me recent visits"
- First, discover the Visit object:
describe_sobject for likely visit objects - Then query with actual field names from the describe result
Objects That Cannot Be Queried via SOQL
Some Salesforce metadata is not accessible via SOQL — these require the Tooling API or Metadata API instead:
| Object / Feature | Correct API |
CompactLayout / Compact Layouts | Tooling API or Metadata API |
LifeSciConfigRecord / Admin Console settings | Tooling API (list_admin_settings) |
LifeSciConfigFieldValue / DB Schema records | Tooling API (list_db_schema) |
| Quick Actions / Custom Actions | Tooling API (list_lsc_actions) |
| Page Layouts | Metadata API (retrieve_metadata) |
NEVER use run_soql for compact layouts. Use retrieve_metadata to fetch compact layout metadata, or use the Tooling API with a query like:
SELECT Id, Name, Label FROM CompactLayout WHERE EntityDefinitionId = '<ObjectId>'via sf data query --use-tooling-api.
Tips
- Start with small LIMIT values to test queries
- Use
describe_sobjectliberally - don't assume field names - LSC uses Health Cloud/Industry Cloud objects, not custom
__cobjects for core functionality - Check the Admin Console documentation for feature-specific object relationships
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

