← ClaudeAtlas

week-aheadlisted

Plan an AE's sales week across their whole Salesforce pipeline and deliver it as a Slack canvas DM. TRIGGER when: the user asks for a 'week ahead', a Monday-morning pipeline plan, a per-deal action plan across their open opportunities, or a sales planning brief built from Org62/Salesforce + Gmail + Slack. Works for any AE (self or on behalf of another), in any language, and can run as a visible /workflows fan-out. DO NOT TRIGGER when: the user wants a single-deal brief only (no whole-book scope), or wants to actually execute actions (this is read-only/planning only).
eprouveze/claude-skills · ★ 0 · AI & Automation · score 74
Install: claude install-skill eprouveze/claude-skills
# week-ahead: AE pipeline planner → Slack canvas Plan the week across **one AE's** active Salesforce pipeline and deliver it as a **Slack canvas DM**. For each open opportunity the skill gathers context from **Org62 (Salesforce) + Gmail + Slack + Google Drive** (and any sibling deal a next-step cross-links to), separates **agreed / recommended / CRM-hygiene** actions with *who·when·why·how*, and assembles a scannable canvas with links so every claim is one click from its source. **Generic by design:** any AE (run as yourself or on behalf of another), any fiscal window, **any canvas language** (auto-detected by default). It is a **planning brief, not an executor** — read-only on all data sources; it only writes its own canvas, the self-DM, and channel-map updates. ## Files in this skill - **`context.md`** — the full spec. **Read it first, every run.** SOQL queries, Org62 custom-field cheat-sheet, the four-source gather pattern, channel-map logic, language handling, action framework, canvas formatting rules, and the read-only contract. - **`week-ahead.workflow.js`** — the workflow version (visible `/workflows` fan-out). Launch via the `Workflow` tool. - **`channel-map.example.json`** — template for the opp Id → Slack channel(s) cache. Copy it to `channel-map.json` (which is **gitignored** — it holds real channel IDs + account names = customer data) and let the run append channels it resolves. Never commit the populated `channel-map.json` to a public repo. - **`prompt