salesloft-core-workflow-b
Track SalesLoft activities, emails, calls, and analytics via the REST API. Use when reading email engagement data, logging call dispositions, or building sales activity dashboards. analytics". '
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill salesloft-core-workflow-b --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# SalesLoft Core Workflow B: Activities & Analytics ## Overview Track and analyze sales activities: emails sent/opened/clicked/replied, calls logged, and engagement metrics. Uses REST API v2 endpoints: `/activities/emails.json`, `/activities/calls.json`, `/action_details/sent_emails.json`. ## Prerequisites - Completed `salesloft-core-workflow-a` - People and cadences already configured ## Instruct
What does the salesloft-core-workflow-b skill do?
Track SalesLoft activities, emails, calls, and analytics via the REST API. Use when reading email engagement data, logging call dispositions, or building sales activity dashboards. analytics". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill salesloft-core-workflow-b --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.