Loading...
Loading...
Found 158 Skills
Momentum platform help — AI revenue orchestration with automated CRM updates, Slack Deal Rooms, MEDDIC Autopilot, AI coaching, churn signals, and executive briefs. Use when Salesforce fields never get updated after calls, deal rooms in Slack are noisy or disorganized, MEDDIC tracking is inconsistent across reps, post-call action items aren't making it into the CRM, you need churn risk signals from customer conversations, or AI coaching scores don't match what you see on calls. Do NOT use for building outbound sequences (use /sales-cadence) or picking an AI note-taker (use /sales-note-taker).
Sprout Social platform help — Publishing, Smart Inbox, Analytics, Social Listening (add-on), Influencer Marketing, Employee Advocacy, AI Assist, API, Salesforce/HubSpot/Zendesk integrations. Use when Sprout Social posts aren't publishing on schedule, Smart Inbox is overwhelming and hard to triage, analytics reports don't show the metrics you need, social listening queries return too much noise, influencer campaigns in Sprout lack visibility, employee advocacy adoption is low, AI Assist suggestions feel off, CRM sync keeps disconnecting, or you're deciding between Sprout Social and Hootsuite/Buffer/Agorapulse. Do NOT use for social listening strategy across tools (use /sales-social-listening), influencer marketing strategy (use /sales-influencer-marketing), social media management strategy (use /sales-social-media-management), or employee advocacy strategy (use /sales-employee-advocacy).
Generates importable n8n workflow JSON files that sync data between Personize and 400+ apps. Produces ready-to-import workflows for batch sync, webhook ingestion, per-record AI enrichment, and data export — no code required. Use this skill whenever the user wants no-code integrations, visual workflows, n8n automation, or to connect Personize to HubSpot, Salesforce, Google Sheets, Slack, Postgres, or any app without writing code. Also trigger when they mention 'workflow automation', 'scheduled sync without code', 'visual pipeline', or 'connect Personize to [app]' and don't want to write TypeScript.
Siro platform help — AI field sales coaching via mobile recording, real-time Halftime mid-call coaching, automated CRM data capture, conversation analytics, follow-up draft generation. Use when setting up Siro for a field sales team, configuring Siro CRM integration with Salesforce or HubSpot via Merge, Siro recording quality or battery drain issues on job sites, building a custom integration with Siro's REST API and webhooks, comparing Siro vs Rilla vs SalesAsk for field sales coaching, or Siro coaching prompts feel too generic for your vertical. Do NOT use for virtual/video meeting note-taking (use /sales-note-taker) or building a coaching program (use /sales-coaching).
Planhat platform help — Health Scores, Agentic Automation, Revenue Management, CRM Sync, Enduser Tracking, Projects, NPS, REST API, MCP Server. Use when health scores aren't reflecting churn risk, CRM sync is overwriting fields or not pulling data, metrics take hours to build and formulas keep breaking, automation rules aren't triggering, revenue or license data doesn't match Salesforce, enduser tracking isn't capturing product usage, or the Planhat API returns unexpected errors. Do NOT use for general customer success strategy (use /sales-customer-success) or NPS/CSAT survey methodology (use /sales-customer-feedback).
Supernormal platform help — AI agent for agencies that turns meeting context into deliverables (pitch decks, briefs, emails, spreadsheets). Use when setting up Supernormal desktop app for bot-free recording, Supernormal AI agents not generating deliverables, Supernormal credits running out or credit system confusion, Supernormal bot joining Zoom calls uninvited, comparing Supernormal to Sembly or Fathom or Fireflies for agency work, Supernormal MCP integration, Supernormal Slack or CRM sync to HubSpot or Salesforce, or Supernormal transcription accuracy issues with accents. Do NOT use for choosing between AI note-takers (use /sales-note-taker) or general meeting transcript API integration (use /sales-note-taker).
Step-by-step guide for creating new internal MCP server integrations in Dust that connect to remote platforms (Jira, HubSpot, Salesforce, etc.). Use when adding a new MCP server, implementing a platform integration, or connecting Dust to a new external service.
People.ai (now Backstory) platform help — automatic activity capture, deal intelligence, pipeline health, revenue forecasting, MCP integration, Salesforce/Dynamics/Oracle CRM sync. Use when reps aren't logging activities and CRM data is stale, deals are slipping without warning and you need early risk signals, forecast accuracy is poor because it's based on gut not data, evaluating People.ai vs Gong vs Clari vs Revenue.io for revenue intelligence, activity data isn't tying back to pipeline or revenue outcomes, or you want to connect People.ai to AI agents via MCP. Do NOT use for conversation intelligence with call recording and transcription (use /sales-gong or /sales-note-taker), building outbound sequences (use /sales-cadence), or general CRM data cleanup strategy (use /sales-data-hygiene).
Cross-cutting OmniStudio analysis skill for namespace detection, dependency visualization, and impact analysis across OmniScripts, FlexCards, Integration Procedures, and Data Mappers. Use this skill to detect which OmniStudio namespace an org uses, build directed dependency graphs, perform impact analysis, and generate Mermaid diagrams of component relationships. TRIGGER when: user asks about OmniStudio dependencies, wants namespace detection (Core vs vlocity_cmt vs vlocity_ins), needs impact analysis, requests dependency diagrams, or asks which components are affected by a change. DO NOT TRIGGER when: authoring OmniScripts (use building-omnistudio-omniscript), building FlexCards (use building-omnistudio-flexcard), creating Integration Procedures (use building-omnistudio-integration-procedure), or configuring Data Mappers (use building-omnistudio-datamapper).
MUST activate when the project contains a uiBundles/*/src/ directory and the task involves adding or modifying a chat widget, chatbot, or conversational AI. Use this skill when the user asks to add, embed, integrate, configure, style, or remove an agent, chatbot, chat widget, conversation client, or AI assistant. Covers styling (colors, fonts, spacing, borders), layout (inline vs floating, width, height, dimensions), and props (agentId, agentLabel, headerEnabled, showHeaderIcon, showAvatar, styleTokens). Activate when files under uiBundles/*/src/ import AgentforceConversationClient or when adding any chat or agent functionality to a page. Never create a custom agent, chatbot, or chat widget component.
MUST activate when the user wants to build, create, or generate a React application, React app, web application, single-page application (SPA), or frontend application — even if no project files exist yet. MUST also activate when the project contains a uiBundles/*/src/ directory or sfdx-project.json and the prompt says create, build, construct, or generate a new app, site, or page from scratch — even if the prompt also describes visual styling. MUST also activate when the task spans more than one ui-bundle skill. Use this skill when building a complete app end-to-end. This is the orchestrator that coordinates scaffolding, features, data access, frontend UI, integrations, and deployment in the correct dependency order. Without it, phases execute out of order and the app breaks. Do NOT use for Lightning Experience apps with custom objects (use generating-lightning-app). Do NOT use for single-concern edits to an existing page (use building-ui-bundle-frontend).
OmniStudio Integration Procedure creation and validation with 110-point scoring. Use when building server-side process orchestrations that combine Data Mapper actions, Apex Remote Actions, HTTP callouts, and conditional logic. TRIGGER when: user creates Integration Procedures, adds Data Mapper steps, configures Remote Actions, or reviews existing IP configurations. DO NOT TRIGGER when: building OmniScripts (use sf-industry-commoncore-omniscript), creating Data Mappers directly (use sf-industry-commoncore-datamapper), or analyzing cross-component dependencies (use sf-industry-commoncore-omnistudio-analyze).