Loading...
Loading...
Found 213 Skills
Winn.ai platform help — real-time AI sales assistant with playbook adherence tracking, automated CRM updates, and live coaching. Use when setting up Winn.ai playbook templates for MEDDIC or BANT or SPICED, CRM fields not populating after sales calls in Salesforce or HubSpot, Winn.ai not tracking talking points during calls, choosing between Winn.ai and Gong or Sybill or Fathom for real-time guidance, understanding Winn.ai Pro vs Enterprise pricing and feature gating, configuring AI meeting prep briefs or follow-up emails, or Winn.ai Chrome extension not working during Zoom or Teams calls. Do NOT use for picking between note-takers generally (use /sales-note-taker) or reviewing a single call for coaching (use /sales-call-review).
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).
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).
Jamie platform help — bot-free AI meeting note-taker, REST API with personal and workspace keys, webhook automations, CRM sync to HubSpot/Salesforce/Attio, MCP server for Claude/ChatGPT/Cursor. Use when setting up Jamie for a sales team, connecting Jamie webhooks to Make.com or a custom endpoint, pulling meeting transcripts and summaries via Jamie API, syncing Jamie action items to Asana or CRM, troubleshooting Jamie not recording or missing speakers, comparing Jamie pricing tiers, or configuring Jamie speaker recognition. Do NOT use for choosing between note-takers (use /sales-note-taker) or reviewing a specific call for coaching (use /sales-call-review).
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).
Read.ai platform help — meeting intelligence with engagement/sentiment analytics, Search Copilot across meetings/email/chat, Ada digital twin, REST API (beta) + MCP Server (`api.read.ai/mcp/`), OAuth auth, webhook automations (`meeting_end` events with HMAC signing), CRM sync to Salesforce/HubSpot, Zapier/n8n workflows, 20+ language transcription. Use when setting up Read.ai webhooks or API integration, connecting Read.ai transcripts to a CRM or data warehouse, configuring Read.ai engagement analytics for a sales team, comparing Read.ai pricing tiers, troubleshooting Read.ai auto-joining meetings without permission, or setting up the Read.ai MCP server with Claude or Cursor. Do NOT use for picking between note-takers (use /sales-note-taker) or reviewing a specific call for coaching (use /sales-call-review).
Evaluate and respond to inbound PostHog sales leads from Salesforce. Use this skill when any PostHog TAE needs to triage an inbound lead — deciding whether to qualify for a call, route to self-serve, or disqualify — and then draft an appropriate response email. Checks Vitally for existing account context before qualifying. Triggers on "respond to this lead", "triage this inbound", "write a response to this lead", "disposition this lead", "evaluate this Salesforce lead", or any request involving an inbound sales inquiry that needs qualification and a reply. Also trigger when a TAE pastes or describes lead details and asks what to do with them.
Connect SaaS data (HubSpot, Stripe, Salesforce, GitHub, Slack, etc.) to Wren Engine for SQL analysis. Guides the user through the full flow: install dlt, pick a SaaS source, set up credentials, run the data pipeline into DuckDB, then auto-generate a Wren semantic project from the loaded data. Use this skill whenever the user mentions: connecting SaaS data, importing data from an API, dlt pipelines, loading HubSpot/Stripe/Salesforce/GitHub/Slack data, querying SaaS data with SQL, or setting up a new data source from a REST API. Also trigger when the user already has a dlt-produced DuckDB file and wants to create a Wren project from it.
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.
Primary Apex authoring skill for class generation, refactoring, and review. ALWAYS ACTIVATE when the user mentions Apex, .cls, triggers, or asks to create/refactor a class (service, selector, domain, batch, queueable, schedulable, invocable, DTO, utility, interface, abstract, exception, REST resource). Use this skill for requests involving SObject CRUD, mapping collections, fetching related records, scheduled jobs, batch jobs, trigger design, @AuraEnabled controllers, @RestResource endpoints, custom REST APIs, or code review of existing Apex.
Cross-cutting OmniStudio analysis skill for namespace detection, dependency visualization, and impact analysis across OmniScripts, FlexCards, Integration Procedures, and Data Mappers. TRIGGER when: user asks about OmniStudio dependencies, wants namespace detection (Core vs vlocity_cmt vs vlocity_ins), needs impact analysis, or requests dependency diagrams. DO NOT TRIGGER when: authoring OmniScripts (use sf-omniscript), building FlexCards (use sf-flexcard), creating Integration Procedures (use sf-integration-procedure), or configuring Data Mappers (use sf-datamapper).