lsc-field-email

Files (1)

• SKILL.md

SKILL.md (first lines)

## How to Answer Field Email Questions

**Always call MCP tools to get sourced documentation.** Do not answer from general knowledge alone.

| User asks about... | Call this tool |
|---------------------|---------------|
| Field email concepts, lifecycle, best practices | `get_lsc_module_docs({ module: "field-email" })` |
| Specific email topic (fragments, consent, Mustache, etc.) | `search_lsc_knowledge({ query: "<topic>" })` |
| Admin Console email settings | `list_admin_settings({ category: "FieldEmail" })` |
| Trigger handler status | `list_trigger_handlers()` |
| Object fields and relationships | `describe_sobject({ sobject: "LifeSciEmailTemplate" })` |
| Email data in the org | `run_soql({ query: "SELECT ... FROM LifeSciEmailTemplate ..." })` |
| Mobile cache status | `check_mobile_cache_status()` |
| Validation / audit | `audit_mobile_config({ group: "email-config-check" })` |

---

## Configuration Mode

When the user asks about configuring Field Email features, **ask them which mode they prefer**:

1. **Show me the documentation** — call `get_lsc_module_docs({ module: "field-email" })` and present the relevant sections
2. **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: "FieldEmail" })
```

#### 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: "EmailTriggerHandler", active: true })
update_admin_setting({ recordId: "...", fields: { ... } })
```

#### Step 5: Verify
Re-run the checks from Step 1 to confirm everything is configured correctly.

---

## Tool Usage Rules

### Correct Object Names
| Correct | Wrong (NEVER use) |
|---------|-------------------|
| `LifeSciEmailTemplate` | `EmailTemplate__c`, `LifeSciEmailTemplate__c` |
| `CommSubscription` | `CommunicationSubscription`, `CommunicationSubscription__c`, `ConsentTopic__c` |
| `CommSubscriptionChannelType` | `CommunicationSubscriptionChannelType` |
| `CommSubscriptionConsent` | `CommunicationSubscriptionConsent`, `Consent__c`, `EmailConsent__c` |
| `ContactPointEmail` | — |
| `LifeScienceEmail` (sent emails and the send queue — `Status` New / Retry until sent) | `LifeSciEmailQueue`, `LifeSciEmailJob`, `EmailQueue__c`, `EmailJob__c` |
| `LifeScienceEmailFragment` (fragment content) | `LifeSciEmailFragment`, `EmailFragment__c` |
| `LifeSciEmailTmplFragment` / `LifeSciEmailTmplRelaFrgmt` (template ↔ fragment links) | — |
| `LifeSciEmailTemplateShare` (template sharing to territories) | — |
| `DataUsePurpose` | — |

There is no email attachment object (`LifeSciEmailAttachment` doesn't exist). Sending runs as the scheduled Apex job `EmailQueueSendSchedulable`.

### Tool Restrictions
- **DO NOT** use `run_soql` for Admin Console settings — use `list_admin_settings`
- **DO NOT** use `run_soql` for mobile cache — use `check_mobile_cache_status()`
- **DO NOT** use `run_soql` for `LifeSciConfigRecord` — it requires Tooling API
- **DO NOT** suggest OmniStudio/FlexCard/OmniScript for mobile — NOT available on LSC Mobile iPad app

From SalesforceLabs/lsc-for-claude, Apache-2.0.

More from SalesforceLabs/lsc-for-claude