Skip to content

PranavNagrecha/AwesomeSalesforceSkills / skills/admin/einstein-discovery-setup

einstein-discovery-setup

Verified

Use this skill when an admin needs to create an Einstein Discovery story in CRM Analytics Studio, configure prediction definitions, deploy writeback fields, set up what-if analysis, or manage model refresh and activation. Trigger keywords: Einstein Discovery story, prediction definition, writeback field, CRM Analytics Studio, model refresh, what-if analysis, bulk scoring, prediction field, 1OR prefix. NOT for the Einstein Discovery Flow action or model-health monitoring in Model Manager — use admin/einstein-discovery-deployment. NOT for Einstein Prediction Builder, a separate product needing no CRM Analytics license — use agentforce/einstein-prediction-builder. NOT for programmatic scoring through the Connect REST API — use agentforce/einstein-discovery-development.

templates/einstein-discovery-setup-template.md

View on GitHub
# Einstein Discovery Setup — Work Template

Use this template when working on tasks in this area.

## Scope

**Skill:** `einstein-discovery-setup`

**Request summary:** (fill in what the user asked for)

## Context Gathered

Record the answers to the Before Starting questions from SKILL.md here.

- **CRM Analytics license confirmed?** Yes / No (check Setup > Company Information > Licenses)
- **Target object:** (e.g., Opportunity, Lead, Case, Contact)
- **Outcome variable and type:** (e.g., IsClosed — binary, or Amount — numeric/regression)
- **Analysis mode required:** Insights only / Insights and Predictions (writeback required?)
- **Existing writeback fields on target object:** (count — max allowed is 3)
- **Profiles/permission sets that need to see prediction scores:** (for FLS assignment)
- **Model refresh schedule needed?** Yes / No — if yes, frequency: ___

## Approach

Which pattern from SKILL.md applies? Why?

- [ ] End-to-End Story Deployment with Writeback (new story + writeback field + page layout)
- [ ] Model Refresh Activation After Scheduled Retraining (existing story, post-refresh steps)
- [ ] Other: ___

## Checklist

Copy the review checklist from SKILL.md and tick items as you complete them.

- [ ] CRM Analytics license confirmed in Setup > Company Information > Licenses
- [ ] Story created in Analytics Studio using the three-step wizard (not Setup menu)
- [ ] Leakage fields excluded from explanatory variables in Step 3 of the wizard
- [ ] "Insights and Predictions" selected (not "Insights only") if writeback scoring is required
- [ ] Prediction definition created and status is Enabled (1OR prefix ID: ___)
- [ ] Writeback field FLS assigned to relevant profiles and permission sets
- [ ] Writeback field added to page layout(s) where scores should appear
- [ ] Initial bulk scoring job triggered and writeback field values verified on sample records
- [ ] Model refresh schedule configured and documented
- [ ] Post-refresh activation step documented in admin runbook
- [ ] Writeback field count on target object confirmed to be 3 or fewer

## Story Configuration Summary

| Setting | Value |
|---|---|
| Target object | |
| Outcome variable | |
| Outcome type | Binary / Numeric |
| Analysis mode | Insights only / Insights and Predictions |
| Explanatory variables included | (list key fields) |
| Leakage fields excluded | (list excluded fields and reason) |
| Prediction definition ID (1OR) | |
| Writeback field API name | |
| Writeback field FLS assigned to | (list profiles/permission sets) |
| Model refresh schedule | |

## Notes

Record any deviations from the standard pattern and why.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall