Loading...
Loading...
Found 1,832 Skills
Use when building a new multi-stage ICM procedure or converting a monolithic runner skill into a staged workflow.
When the user wants to improve their persistent but respectful outreach that keeps deals moving. Also use when the user mentions "following up," "staying on top of deals," "persistent outreach," "keeping deals alive," "not letting deals fall through," or "consistent follow-up."
Data Cloud 360° view of a single Agentforce session. TRIGGER when user asks to trace, inspect, summarize, or describe a specific Agentforce session by session id (Agent Session UUID `019d…` or MessagingSession id `0Mw…`). Also triggers on session discovery — find/list/search sessions by time, agent, channel, outcome, or conversation text — when the user has no session id yet. DO NOT TRIGGER for design-time architecture questions (use agentforce-architecture-analyze instead) or for runtime perf/latency/SLO questions that require platform telemetry beyond Data Cloud.
Deal health scoring + next-best-action for every open deal. Pulls HubSpot deals, CRM activity history, and engagement data to flag stalled deals, predict close probability, and recommend specific recovery actions. Runs daily at 7am CST or on-demand. Use when: 'deal health', 'pipeline review', 'stalled deals', 'deal momentum', 'which deals need attention', 'morning brief', 'SOD'.
When the user wants to improve their ability to prioritize high-value activities and prospects in sales. Also use when the user mentions "managing time," "prioritizing prospects," "focus on selling," "too many tasks," "sales productivity," or "making time for selling."
When the user wants to plan a new territory launch, account expansion, or sales campaign kickoff. Also use when the user mentions "territory planning," "account launch," "sales campaign," "market entry," "new segment," "expansion strategy," "account blitz," or "pipeline generation campaign." This skill covers structured approaches to launching into new accounts, territories, or market segments.
Harden the test surface after `/cook` — map changed behavior to tests, find weak assertions and missing boundaries, and add focused hardening tests. Use when the user wants the tests strengthened before review or shipping — phrases like "press the changes", "harden this", "check coverage", "strengthen the tests", "are the tests good enough", "press before /age", "/press". Use even when the user wants to "tighten things up" before review. Do NOT use to add broad new behavior — only corrective fixes that hardening tests force.
Create VFX authoring and integration rules that preserve readability, style fit, and performance.