sales-salesloft
Salesloft platform help — config, Rhythm, Conversations, Deals, Forecast, Analytics, Drift, integrations, admin, API. Use when Salesloft settings aren't configured right, Rhythm signals feel noisy or unhelpful, Analytics dashboards don't show what you need, Drift chatbots aren't converting, or Salesloft integrations are broken. Do NOT use for building cadences (use /sales-cadence), reviewing calls (use /sales-call-review), inspecting deals (use /sales-deal-inspect), or forecasting (use /sales-forecast).
What this skill does
# Salesloft Platform Help
Help the user with Salesloft platform questions — from configuration and Rhythm signals through Analytics dashboards, Drift chatbots, and integrations.
## Step 1 — Gather context
If `references/learnings.md` exists, read it first for accumulated knowledge.
Ask the user:
1. **What area of Salesloft do you need help with?**
- A) Cadence — multi-channel outbound sequences (hand off: `/sales-cadence {your question}`)
- B) Rhythm — AI-prioritized daily workflow and signals
- C) Conversations — call recording, transcription, coaching (for call reviews, hand off: `/sales-call-review {your question}`)
- D) Deals — pipeline visibility and deal management (for deal analysis, hand off: `/sales-deal-inspect {your question}`)
- E) Forecast — revenue forecasting and pipeline coverage (hand off: `/sales-forecast {your question}`)
- F) Analytics — reporting, dashboards, team performance
- G) Drift — chatbots, live chat, conversational marketing
- H) Admin — user management, settings, permissions, SSO
- I) Integrations — CRM sync, API, webhooks, third-party tools
- J) Something else — describe it
2. **What's your role?**
- A) Sales rep / AE / BDR
- B) Sales manager / team lead
- C) RevOps / Sales Ops
- D) Admin / IT
- E) Other
3. **What are you trying to accomplish?** (describe your specific goal or question)
Note: If the user needs one of the specialized skills (Cadence, call review, deal inspection, forecasting), route them there with a brief explanation of why that skill is a better fit.
## Step 2 — Route or answer directly
If the request maps to a specialized skill, route:
- Cadence/sequence building → `/sales-cadence`
- Call review/coaching → `/sales-call-review`
- Deal health/risk analysis → `/sales-deal-inspect`
- Revenue forecasting → `/sales-forecast`
Otherwise, answer directly from platform knowledge using the reference below.
## Step 3 — Salesloft platform reference
Provide module-by-module guidance based on the user's area:
### Rhythm
- **What it is**: AI-powered workflow engine that prioritizes daily seller actions based on buyer signals
- **Key concepts**: Rhythm signals, plays, focus zone, signal prioritization, Rhythm sidebar
- **Common configs**: Signal weighting, play creation, automation rules, Rhythm integration with Cadence
- **Metrics**: Signal-to-action rate, tasks completed, pipeline influenced by Rhythm
- **Best practices**: Trust the AI prioritization, customize signal weights for your sales motion, review Rhythm analytics weekly
### Analytics
- **What it is**: Built-in reporting and dashboards for team and individual performance
- **Key concepts**: Standard reports, custom reports, dashboard builder, team analytics, activity metrics
- **Common reports**: Activity leaderboard, cadence performance, pipeline creation, conversion rates, call metrics
- **Common configs**: Custom report builder, scheduled reports, export settings, team vs. individual views
- **Best practices**: Set up weekly automated reports, track leading indicators (activities) not just lagging (revenue), benchmark reps against team averages
### Drift (Conversational Marketing)
- **What concepts**: Chatbots, playbooks, live chat, meeting scheduling, site visitor identification
- **Common configs**: Bot playbook builder, routing rules, meeting calendar integration, ABM targeting, Fastlane for qualified leads
- **Metrics**: Conversations started, meetings booked via chat, bot deflection rate, response time
- **Best practices**: Use ABM targeting for high-value accounts, keep bot flows under 4 steps, always offer human handoff, A/B test opening messages
### Admin & Settings
- **User management**: Roles, permissions, teams, hierarchies
- **CRM sync**: Salesforce/HubSpot sync settings, field mapping, conflict resolution, sync frequency
- **SSO**: SAML configuration, provisioning
- **Data management**: Import/export, duplicate management, data hygiene
- **Common issues**: Sync conflicts, permission errors, API rate limits
### Salesloft data model
Core entities in the Salesloft platform — understand these to navigate the UI, build reports, and work with the API:
| Entity | What it represents | Key relationships |
|---|---|---|
| **Person** | An individual prospect or contact | Belongs to an Account, can be enrolled in Cadences |
| **Account** | A company or organization | Has many People, can have Cadences targeting it |
| **Cadence** | A multi-step outbound sequence | Has Cadence Memberships (enrollments) |
| **Cadence Membership** | A Person's enrollment in a Cadence | Links Person to Cadence with step/status tracking |
| **User** | A Salesloft user (rep, manager, admin) | Owns People, Accounts, Cadences |
| **Contact** | A person record synced from CRM | Maps to Person in Salesloft |
| **Email** | A sent email tracked in Salesloft | Linked to Person, Cadence step, and User |
| **Call** | A logged or recorded call | Linked to Person and User, feeds Conversations |
| **Note** | A note attached to a Person or Account | Created by User |
| **Team Meeting** | A scheduled meeting | Linked to People and Users |
| **Do Not Contact** | An opt-out record | Blocks a Person from receiving outreach |
### Integrations & API
- **Native integrations**: Salesforce, HubSpot, Slack, LinkedIn Sales Navigator, Drift, calendar sync
- **API basics**: REST API, authentication (OAuth 2.0), rate limits, common endpoints
- **Webhooks**: Available events, payload structure, retry logic
- **Common use cases**: CRM sync customization, custom reporting, workflow automation, datan enrichment
### Salesloft API reference
For detailed API documentation including endpoints, rate limits, webhooks, and automation patterns, consult `references/api-reference.md`.
**Quick reference**: Base URL `https://api.salesloft.com/v2`, OAuth 2.0 auth, 600 req/min rate limit. Full docs: https://developers.salesloft.com/
### Using Membrane for direct Salesloft access
If you want Claude to interact with Salesloft directly (list people, get cadences, create records), install the Membrane Salesloft skill:
```bash
npx skills add membranedev/application-skills --skill salesloft
```
This gives Claude hands-on API access through pre-built actions with authentication and error handling built in. Use it when you need to:
- Pull live data from Salesloft (people, accounts, cadences, emails, calls)
- Create or update records without leaving the terminal
- Automate workflows that touch Salesloft data
The Membrane skill handles auth, pagination, and rate limits automatically — prefer it over raw API calls when possible.
### Conversations
- **What it is**: Call recording, transcription, and conversation intelligence
- **Key concepts**: Call recording, AI transcription, talk-to-listen ratio, topic detection, coaching playlists
- **Common configs**: Recording consent settings, transcription language, keyword tracking, coaching playlist setup
- **Best practices**: Create coaching playlists by topic/methodology, review calls with highest/lowest scores, use topic detection for competitive intel
### Deals
- **What it is**: Pipeline visibility and deal management with CRM sync
- **Key concepts**: Deal board, deal health scores, pipeline views, deal gaps, activity timeline
- **Common configs**: Deal stage mapping, health score criteria, pipeline views, required fields per stage
- **Best practices**: Review deal board weekly, address gaps flagged by health scores, ensure CRM sync is bidirectional
### Forecast
- **What it is**: Revenue forecasting with rollup, submission, and AI-assisted predictions
- **Key concepts**: Forecast categories (commit/best case/pipeline/omit), rollup hierarchy, submission workflow, AI forecast
- **Common configs**: Category definitions, submission cadence, rollup rules, override permissions
- **Best practices**: Submit forecasts weekly, use AI forecast as a benchmark, document override reasons
## Step 4 — Actionable guidanceRelated in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.