lsc-consent-management
Skill10 starsChanged 29 days agoApache-2.0View on GitHub
Guides Life Sciences Cloud (LSC) Consent Management configuration for web and mobile apps. Use when user asks about consent capture, communication subscriptions, opt-in, opt-out, engagement channel types, compliance statements for consent, digital signatures, consent history, contact point consent, or CommunicationSubscription/CommSubscriptionConsent objects.
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-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
- salesforce-querySkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
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 25
When the user asks about configuring Consent Management features, ask them which mode they prefer:
- Distinctive: line 30
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()
- Very specific: line 81
No consent-specific config check tool exists — use list_admin_settings and SOQL queries to check consent state
≈ “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 Consent Management Questions
Always call MCP tools to get sourced documentation. Do not answer from general knowledge alone.
| User asks about... | Call this tool |
| Consent concepts, lifecycle, best practices | get_lsc_module_docs({ module: "consent-management" }) |
| Specific consent topic (digital signatures, compliance snapshots, etc.) | search_lsc_knowledge({ query: "<topic>" }) |
| Admin Console consent settings | list_admin_settings({ category: "ConsentManagement" }) |
| Trigger handler status | list_trigger_handlers() |
| Object fields and relationships | describe_sobject({ sobject: "CommSubscriptionConsent" }) |
| Consent data in the org | run_soql({ query: "SELECT ... FROM CommSubscriptionConsent ..." }) |
| Mobile cache status | check_mobile_cache_status() |
| Validation / audit | audit_mobile_config({ group: "consent-config-check" }) |
Configuration Mode
When the user asks about configuring Consent Management features, ask them which mode they prefer:
- Show me the documentation — call
get_lsc_module_docs({ module: "consent-management" })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: "ConsentManagement" })
run_soql({ query: "SELECT Id, Name, Status FROM CommunicationSubscription WHERE Status = 'Active'" })
run_soql({ query: "SELECT Id, Name, ContactPointType, IsActive FROM EngagementChannelType WHERE IsActive = true" })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: "ConsentTriggerHandler", active: true })
update_admin_setting({ recordId: "...", fields: { ... } })Step 5: Verify
Re-run the queries from Step 1 to confirm everything is configured correctly.
Tool Usage Rules
Correct Object Names
| Correct | Wrong (NEVER use) |
CommunicationSubscription | Subscription__c, ConsentSubscription__c |
CommSubscriptionConsent | CommunicationSubscriptionConsent, ConsentRecord__c, Consent__c |
CommunicationSubscriptionChannelType | Channel__c, ConsentChannel__c |
CommunicationSubscriptionComplianceSnapshot | ConsentSnapshot__c, ConsentCompliance__c |
EngagementChannelType | ConsentChannelType__c |
DataUsePurpose | — |
ComplianceStatementDef | — |
DigitalSignature | — |
ContactPointEmail | — |
ContactPointPhone | — |
ContactPointAddress | — |
ContactPointSocial | — |
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
- No consent-specific config check tool exists — use
list_admin_settingsand SOQL queries to check consent state
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.

