lsc-surveys
Skill10 starsChanged 29 days agoApache-2.0View on GitHub
Guides Life Sciences Cloud (LSC) Surveys configuration and usage. Use when user asks about surveys in LSC, survey launch during visits, survey responses, survey sharing with territory, survey locking on mobile, SurveyResponse/SurveySubject objects, or Survey object configuration.
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-territory-alignmentSkill
- lsc-troubleshootSkill
- lsc-user-managementSkill
- lsc-visit-managementSkill
- salesforce-querySkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- Distinctive: line 8
Always call MCP tools to get sourced documentation: Do not answer from general knowledge alone.
- Distinctive: line 23
Always include the citation line from the tool response in your answer.
- Distinctive: line 29
When the user asks about configuring or enabling Surveys, ask them which mode they prefer:
- Distinctive: line 34
Default to guided setup when connected to an org, or documentation mode if no org is connected.
- Very specific: line 78
DO NOT: use run_soql for Admin Console settings — use list_admin_settings
- Very specific: line 79
DO NOT: use run_soql for mobile cache — use check_mobile_cache_status()
≈ “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
How to Answer Survey Questions
Always call MCP tools to get sourced documentation. Do not answer from general knowledge alone.
| User asks about... | Call this tool |
| Survey concepts, setup, best practices | get_lsc_module_docs({ module: "surveys" }) |
| Specific survey topic (sharing, launch points, etc.) | search_lsc_knowledge({ query: "<topic>" }) |
| Admin Console survey settings | list_admin_settings({ category: "Surveys" }) |
| Trigger handler status | list_trigger_handlers() |
| Object fields and relationships | describe_sobject({ sobject: "Survey" }) |
| Survey data in the org | run_soql({ query: "SELECT ... FROM Survey ..." }) |
| Survey responses | run_soql({ query: "SELECT ... FROM SurveyResponse ..." }) |
| Survey context records | run_soql({ query: "SELECT ... FROM SurveySubject ..." }) |
| Mobile cache status | check_mobile_cache_status() |
| Validation / audit | audit_mobile_config({ group: "survey-config-check" }) |
Always include the citation line from the tool response in your answer.
Configuration Mode
When the user asks about configuring or enabling Surveys, ask them which mode they prefer:
- Show me the documentation — call
get_lsc_module_docs({ module: "surveys" })and present the relevant sections - Walk me through it — configure it directly in their org step-by-step (guided setup below)
Default to guided setup when connected to an org, or documentation mode if no org is connected.
Guided Setup Workflow
Step 1: Check Current State
list_trigger_handlers()
list_admin_settings({ category: "Surveys" })Step 2: Report Findings
Present a summary table of what's configured vs what's missing/disabled.
Step 3: Propose Changes
For each issue found, propose the fix and wait for user confirmation.
Step 4: Apply Changes (with user confirmation)
toggle_trigger_handler({ handlerName: "SurveyTriggerHandler", active: true })
update_admin_setting({ recordId: "...", fields: { ... } })Step 5: Verify
Re-run checks from Step 1 to confirm everything is configured correctly.
Tool Usage Rules
Correct Object Names
| Correct | Wrong (NEVER use) |
Survey | Survey__c, Survey__mdt, LSCSurvey__c, FeedbackForm__c |
SurveyVersion | — |
SurveyPage | — |
SurveyQuestion | — |
SurveyQuestionChoice | — |
SurveyResponse | SurveyResponse__c, SurveyAnswer__c, SurveyResult__c |
SurveyQuestionResponse | SurveyQuestionResponse__c |
SurveySubject | SurveySubject__c, SurveyContext__c |
SurveyInvitation | — |
SurveyShare | SurveySharing__c, SurveyAccess__c |
Tool Restrictions
- DO NOT use
run_soqlfor Admin Console settings — uselist_admin_settings - DO NOT use
run_soqlfor mobile cache — usecheck_mobile_cache_status() - DO NOT suggest OmniStudio/FlexCard/OmniScript for mobile — NOT available on LSC Mobile iPad app
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.

