lsc-briefings
Skill10 starsChanged 29 days agoApache-2.0View on GitHub
Guides Briefings (Daily Podcasts) configuration and troubleshooting. Use when user asks about Briefings, Field Insights, Daily Podcasts, audio briefings, Kokoro TTS, PresentationContent, podcast text generation, or on-device audio.
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-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
- salesforce-querySkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 6 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
6
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 Briefings configuration, 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.
- Distinctive: line 81
Do NOT search by perm set label — admins can name them anything
- Distinctive: line 115
Ask the user which end user(s) will receive Briefings — never auto-assign
- Very specific: line 132
Create LifeSciConfigRecord with LifeSciConfigCategoryId pointing to the "DbSchema" category, Type, IsActive=false
- Very specific: line 133
Create LifeSciConfigFieldValue records for: SObject (DataType=OBJECT, ObjectValue), Type (DataType=PICKLIST, PicklistValue), OneWaySync …
- Very specific: line 134
Create Status field value: FieldName=Status, DataType=PICKLIST, PicklistValue=Valid — REQUIRED for the record to show as Valid in Admin …
- Very specific: line 162
Create parent LifeSciMobileMetadataRecord with IntegrationStatus=New, Status=New
- Very specific: line 163
Create child LifeSciMobileMetadataRecord with ParentMobileMetadataRecId=<parentId>, ProfileId=<profileId>, IntegrationStatus=New, Status=New
- Very specific: line 164
Update BOTH parent and child to Status=ValidationCompleted
- Distinctive: line 175
No iOS native TTS fallback — Kokoro only
≈ “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 Briefings Questions
Always call MCP tools to get sourced documentation. Do not answer from general knowledge alone.
| User asks about... | Call this tool |
| Briefings overview, setup steps, how it works | search_lsc_knowledge({ query: "Briefings Daily Podcasts setup" }) |
| Briefings documentation | get_lsc_module_docs({ module: "briefings" }) |
| Check if Briefings is configured | check_briefings_config() |
| Check a specific user's access | check_briefings_config({ username: "user@org.com" }) |
| DB Schema / mobile cache for Briefings | list_db_schema({ filter: "PresentationContent" }) |
| Mobile cache status | check_mobile_cache_status() |
| Permission sets for Briefings | list_permission_sets() |
| Troubleshoot why Briefings isn't working | check_briefings_config() then diagnose_lsc_issue({ symptom: "<error>" }) |
Configuration Mode
When the user asks about Briefings configuration, ask them which mode they prefer:
- Show me the documentation — call
search_lsc_knowledge({ query: "Briefings setup" })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: Run Comprehensive Check
check_briefings_config()Step 2: Report Findings
Present the diagnostic results. Highlight FAIL items that need attention.
Step 3: Fix Issues
For each issue found, use the appropriate tool:
| Issue | Fix With |
| Briefings toggle OFF | Guide user to Setup → Life Sciences for Customer Engagement Setup → Configure Briefings → Toggle ON |
| Missing permission sets | assign_permission_set({ label: "...", usernames: [...] }) |
| Missing Briefings permission (PermissionsStoriesUser/PermissionsStoriesAdmin) | Guide user through clone + enable "Use Briefings" or "Manage Briefings" system permission |
| Account Summarization not configured | Guide to Setup → Configure Account Summarization |
| No Content Definition | Guide to Configure Briefings → Manage Assignments |
| Scheduling flow not cloned | Guide through clone + activate flow |
| Missing DB Schema configs | create_db_schema({ objectName: "PresentationContent" }) etc. |
| Stale mobile cache | generate_mobile_metadata_cache({ profileNames: [...] }) |
Step 4: Verify
Re-run check_briefings_config() to confirm all issues are resolved.
Key Technical Details
Correct Object Names
PresentationContent— generated briefing recordsPrstContentDefinition— content definition (NOTPresentationContentDefinition)PrstCntntDefAssignment— profile assignments (NOTPresentationContentDefinitionAssignment)PrstCntntUsageSummary— usage tracking (NOTPresentationContentUsageSummary)PrvdAccountTerritorySummary— account summarization output
System Permissions (queryable via boolean fields on PermissionSet)
The feature shipped as Briefings in production (262). The API/XML names use the legacy Stories naming — they were not renamed when the feature was rebranded. Both are correct.
| UI Label (Setup) | SOQL field on PermissionSet | XML <name> in metadata | Who needs it |
| Manage Briefings | PermissionsStoriesAdmin | StoriesAdmin | Admins |
| Use Briefings | PermissionsStoriesUser | StoriesUser | End users (reps) |
- Query:
SELECT Id, Label FROM PermissionSet WHERE PermissionsStoriesAdmin = true AND IsCustom = true - Query:
SELECT Id, Label FROM PermissionSet WHERE PermissionsStoriesUser = true AND IsCustom = true - Do NOT search by perm set label — admins can name them anything
Programmatic Creation of Cloned Permission Sets
Cloned perm sets can be created via metadata deploy (sf project deploy start). Do NOT include a <license> element — it causes deploy failures.
Admin perm set (StoriesAdmin):
<?xml version="1.0" encoding="UTF-8"?>
<PermissionSet xmlns="http://soap.sforce.com/2006/04/metadata">
<label>Life Sciences Commercial Admin - Briefings</label>
<hasActivationRequired>false</hasActivationRequired>
<userPermissions>
<enabled>true</enabled>
<name>StoriesAdmin</name>
</userPermissions>
</PermissionSet>- Auto-assign to the currently authenticated admin user (the user running this configurator)
End user perm set (StoriesUser):
<?xml version="1.0" encoding="UTF-8"?>
<PermissionSet xmlns="http://soap.sforce.com/2006/04/metadata">
<label>Life Sciences [Role] - Briefings</label>
<hasActivationRequired>false</hasActivationRequired>
<userPermissions>
<enabled>true</enabled>
<name>StoriesUser</name>
</userPermissions>
</PermissionSet>Determining which base role to name the cloned set after:
- Ask the user which end user(s) will receive Briefings — never auto-assign
- Query those users' profiles:
SELECT Id, Profile.Name FROM User WHERE Username = '<username>' - Map profile to role name for the label:
| End User Profile | Base Perm Set (reference) | Suggested Cloned Label |
| Field Sales Representative | LifeSciencesFieldSalesRepresentative | "Life Sciences Field Sales Rep - Briefings" |
| Key Account Manager | LifeSciencesKeyAccountManager | "Life Sciences KAM - Briefings" |
| Medical Science Liaison | LifeSciencesFieldMedical | "Life Sciences MSL - Briefings" |
Assignment rules:
- Admin perm set → assign to current authenticated user (auto, no need to ask)
- End user perm set → always ask user for specific username(s) — never guess or auto-assign based on profile
Required DB Schema Records
These can be created programmatically via the Tooling API (v67+). Use LifeSciConfigRecord and LifeSciConfigFieldValue objects. Each record requires:
- Create
LifeSciConfigRecordwithLifeSciConfigCategoryIdpointing to the "DbSchema" category,Type,IsActive=false - Create
LifeSciConfigFieldValuerecords for:SObject(DataType=OBJECT, ObjectValue),Type(DataType=PICKLIST, PicklistValue),OneWaySync(DataType=BOOLEAN, HasBooleanValue=true for Unidirectional, false for Bidirectional),WhereSoql(DataType=LONGTEXT, LongTextValue) - Create
Statusfield value:FieldName=Status,DataType=PICKLIST,PicklistValue=Valid— REQUIRED for the record to show as Valid in Admin Console - Update
LifeSciConfigRecord.IsActive = true
| Config Name | Object | Type | Sync | WHERE Clause |
DbSchema_PresentationContent | PresentationContent | DATA | Unidirectional | (EffectiveStartDate = NULL OR EffectiveStartDate <= TODAY) AND EffectiveEndDate >= TODAY AND (TargetUserId = '{USER.ID}' OR TargetUserId = NULL) AND (TerritoryId = '{USER.TERRITORYID}' OR TerritoryId = NULL) |
DbSchema_PrstCntntUsageSummary | PrstCntntUsageSummary | DATA | Bidirectional | UserId = '{USER.ID}' AND PresentationContentId IN (SELECT Id FROM PresentationContent WHERE (EffectiveStartDate = NULL OR EffectiveStartDate <= TODAY) AND (EffectiveEndDate >= TODAY OR EffectiveEndDate = NULL) AND (TargetUserId = '{USER.ID}' OR TargetUserId = NULL) AND (TerritoryId = '{USER.TERRITORYID}' OR TerritoryId = NULL)) |
DbSchema_PrstCntntDefAssignment | PrstCntntDefAssignment | CONFIGURATION | Unidirectional | IsActive = true |
DbSchema_PrstContentDefinition | PrstContentDefinition | CONFIGURATION | Bidirectional | (none) |
Briefings Icon Visibility (Two Conditions)
The Briefings icon appears in the mobile app ONLY when BOTH:
- User's profile is in an active
PrstCntntDefAssignment - User has read access to
PresentationContentobject
Key Flows
| Flow ApiName | Type | Expected State |
SchdDlyBriefingsOfPrvdAcct | Original scheduling template (managed) | Should exist, NOT active |
| (admin's clone — any name) | Cloned scheduling flow | Should be ACTIVE with Daily frequency |
GenDailyBriefingsText | Text generation flow (managed) | Should exist, ACTIVE |
| Generate Provider Account Territory Summary | Account Summarization | Should exist, ACTIVE |
Important: The scheduling flow clone can have any label/ApiName the admin chooses. Do NOT search for it by name. Verify the pipeline outcome (PresentationContent records being generated) instead.
Metadata Cache Generation (Programmatic)
To generate the mobile metadata cache via API:
- Create parent
LifeSciMobileMetadataRecordwithIntegrationStatus=New,Status=New - Create child
LifeSciMobileMetadataRecordwithParentMobileMetadataRecId=<parentId>,ProfileId=<profileId>,IntegrationStatus=New,Status=New - Update BOTH parent and child to
Status=ValidationCompleted - POST to
/services/data/v67.0/connect/life-sciences/commercial/metadata/actions/generatewith body:{"parentMetadataRecordId":"<parentId>","apiVersion":"67.0","prefix":"lsc4ce"} - Poll parent record until
Status=Active(takes 2-5 minutes, poll every 15s)
The endpoint returns {"message":"Task enqueued for metadata cache generation."} on success. Status transitions: New → Loading → Processing → Active.
Limitations (262 GA)
- English only — Kokoro TTS uses English pronunciation exclusively
- 3,000 character limit per briefing
- Daily frequency only — current day's visits only
- Playlist not dynamically updated for same-day visit changes
- No iOS native TTS fallback — Kokoro only
Common Issues
| Symptom | Most Likely Cause |
| Briefings icon not showing | PermissionsStoriesUser not enabled in any assigned perm set, OR profile not in Content Definition Assignment, OR no read access to PresentationContent |
| No audio playing | Scheduled flow hasn't run, or no PresentationContent records generated |
| "sObject type PresentationContent is not supported" | Briefings toggle is OFF OR admin user lacks StoriesAdmin permission. Verify with secondary check: SELECT Id FROM FlowDefinitionView WHERE Label LIKE '%Briefings%' — if flows exist, toggle is ON and the issue is permissions |
| Flow not found | Managed package (lsc4ce) not installed or wrong version |
| Briefings flows missing | Briefings toggle was recently enabled — flows appear after toggle ON |
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.

