Token导航 LogoToken导航

Agent Skill · 研究检索

sales-lemlist(销售列表)

sales-lemlist 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

sales-lemlist 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 40,294。

总安装 1,304周安装 56GitHub Stars 13下载 457核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:sales-lemlist(销售列表)
来源仓库:https://github.com/sales-skills/sales
仓库路径:skills/sales-lemlist
安装命令:
npx skills add https://github.com/sales-skills/sales --skill sales-lemlist
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/sales-skills/sales --skill sales-lemlist

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

sales-lemlist 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于基于关键词或任务场景的信息检索需求。通过 npx skills add 命令从 GitHub 仓库安装并使用。安装前应评估权限范围、维护状态及潜在的网络或执行操作。

可查阅原始 README 进一步确认功能细节。

来源仓库内路径:skills/sales-lemlist

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/sales-skills/sales --skill sales-lemlist;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

sales-lemlist 怎么安装?

在终端执行 npx skills add https://github.com/sales-skills/sales --skill sales-lemlist。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

sales-lemlist 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

sales-lemlist 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

sales-lemlist 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

sales-lemlist 用的人多吗?

公开数据是累计安装 1,304 次,近一周安装 56 次,下载 457 次,GitHub 13 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

sales-lemlist 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
sales-lemlist

销售列表 · 本页

1,30413需要联网未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Lemlist Platform Help

Help the user with Lemlist platform questions — from multichannel sequence setup and Lemwarm through lead management, enrichment, AI personalization, LinkedIn automation, unified inbox, API, and integrations.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated knowledge.

Ask the user:

  1. What area of Lemlist do you need help with?

- A) Sequences — creating, managing, or optimizing multichannel sequences (for strategy, hand off: /sales-cadence {your question}) - B) Lead database — finding prospects with People Database, filters, intent signals - C) Enrichment — waterfall enrichment for emails and phone numbers - D) Lemwarm — warmup, deliverability score, sender reputation - E) Unified inbox — managing replies across channels - F) LinkedIn — automated LinkedIn steps, connection requests, messages - G) Calls — in-app dialer, call steps in sequences - H) WhatsApp — WhatsApp messaging steps (add-on) - I) AI personalization — dynamic variables, AI-generated content - J) Integrations — HubSpot, Salesforce, Pipedrive, Zapier, Make - K) API & Webhooks — automation, lead import, campaign management - L) Admin — billing, plan features, team settings - M) Something else — describe it

  1. What's your role?

- A) Sales rep / AE / BDR - B) Sales manager / team lead - C) RevOps / Sales Ops - D) Agency owner / account manager - E) Admin / IT - F) Founder / solo seller - G) Other

  1. What are you trying to accomplish? (describe your specific goal or question)

If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.

Note: If the user needs a specialized skill, 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:

  • List building / prospecting → /sales-prospect-list
  • Contact enrichment outside Lemlist → /sales-enrich
  • Cadence strategy / sequence design → /sales-cadence
  • Cross-platform deliverability → /sales-deliverability
  • Tool integration architecture → /sales-integration

Otherwise, answer directly from platform knowledge using the reference below.

Step 3 — Lemlist platform reference

Provide module-by-module guidance based on the user's area:

Sequences (Multichannel Campaigns)

  • What it is: A sequence in Lemlist is a multichannel outreach campaign — email steps, LinkedIn actions, phone calls, and WhatsApp messages on an automated schedule
  • Key concepts: Sequence = multichannel campaign, steps = touchpoints across channels, leads = enrolled contacts
  • Channels available: Email, LinkedIn (connection requests, profile visits, messages), phone (in-app dialer), WhatsApp (paid add-on at $20/seat/month)
  • A/B testing: Test subject lines, email body content, and entire step variants
  • Lead statuses: interested, not interested, contacted, not contacted
  • Best practices: Keep initial emails under 125 words, mix channels (don't do 3+ email steps in a row), use AI personalization for Level 3+ at scale

Lead Database (People Database)

  • What it is: Built-in B2B lead database with 600M+ contacts and smart filtering
  • Key features: Search by title, seniority, industry, company size, location, tech stack
  • Intent signals: Identifies prospects actively researching relevant topics (newer feature)
  • Credit model: Pay per lead revealed — credits deducted on export/use
  • Pre-verification: Leads from People Database are verified before delivery
  • Best practices: Use filters to narrow before revealing — don't burn credits on broad searches

Enrichment

  • What it is: Built-in waterfall enrichment — find verified emails and phone numbers for your leads
  • How it works: Lemlist tries multiple data providers in sequence (waterfall) to maximize match rates
  • Email finder: Find professional email addresses from name + company
  • Phone finder: Find direct/mobile phone numbers
  • Verification: Emails are verified before delivery to reduce bounce rates
  • Best practices: Enrich leads before adding to sequences — don't send to unverified addresses

Lemwarm (Deliverability)

  • What it is: Built-in email warmup tool included with every Lemlist seat at no extra cost
  • How it works: Sends automated warmup emails to a premium network of 10,000+ real users, generating real opens and replies to build sender reputation
  • Deliverability score: Score out of 100 showing inbox placement quality (target 90+)
  • Warmup settings: Configure emails/day (recommended 30/day for accounts <6 months, 40/day for older) and ramp-up increment
  • Warmup timeline: Minimum 3-5 weeks before adding cold outbound
  • Inbox rotation: Distribute sends across multiple email accounts connected to a sequence
  • Best practices: Enable Lemwarm on every connected email account immediately. Keep warmup running even during active campaigns — it maintains reputation.

Unified Inbox

  • What it is: Single view for all replies across email, LinkedIn, and other channels
  • Key features: Reply tracking, conversation threads, label conversations, draft responses
  • Channel aggregation: See email replies, LinkedIn messages, and WhatsApp responses in one place
  • Best practices: Check unified inbox daily, respond within 1 hour for best conversion

LinkedIn Automation

  • What it is: Automated LinkedIn steps within sequences — profile visits, connection requests, and messages
  • Step types: Visit profile, send connection request (with note, under 300 chars), send message (to existing connections)
  • Limits: LinkedIn has daily action limits — Lemlist respects these but monitor your LinkedIn account for warnings
  • Plan requirement: Multichannel Expert plan ($99/user/month) required for LinkedIn steps
  • Best practices: Always visit profile before sending connection request. Keep connection request notes casual and non-salesy. Don't exceed 20-30 connection requests/day.

Calls (In-App Dialer)

  • What it is: Built-in calling within Lemlist sequences — add phone steps alongside email and LinkedIn
  • Key features: Click-to-call from lead record, call logging within sequence activity
  • Plan requirement: Multichannel Expert plan required
  • Best practices: Place call steps within 24 hours of an email step — reference the email in your opener

WhatsApp

  • What it is: WhatsApp messaging steps within sequences (paid add-on at $20/seat/month)
  • How it works: Add WhatsApp steps to multichannel sequences alongside email, LinkedIn, and calls
  • Requirement: WhatsApp Business account + Lemlist WhatsApp add-on
  • Best practices: Use WhatsApp for warm follow-ups after email/LinkedIn engagement, not cold first-touch

AI Personalization

  • What it is: AI-powered content generation that pulls data from LinkedIn profiles, company websites, and other sources to create personalized outreach at scale
  • How it works: Configure AI variables that research each lead and generate custom snippets (icebreakers, pain points, company references)
  • Dynamic variables: Standard merge fields ({{firstName}}, {{companyName}}) plus AI-generated custom variables
  • Best for: Level 3-4 personalization at scale (100+ prospects) — finding specific talking points per lead
  • Not for: Simple {{firstName}} personalization — just use standard variables for that

Lemlist data model

Core entities — understand these to navigate the UI and work with the API:

EntityWhat it representsKey relationships
Campaign/SequenceA multichannel outreach sequenceHas Steps, has Leads, uses Email Accounts
LeadA contact enrolled in a sequenceBelongs to a Campaign, has activity tracking
ContactA person in your databaseCan be enrolled in multiple Campaigns
CompanyAn organizationHas Contacts, has firmographic data
Email AccountA connected sending mailboxUsed by Campaigns, has Lemwarm status
StepA touchpoint in a sequence (email, LinkedIn, call, WhatsApp)Belongs to a Campaign
ScheduleSending window and timezone configAssociated with Campaigns

API & Integrations

For detailed API documentation including all endpoints, authentication, rate limits, and webhook event payloads, consult references/lemlist-api-reference.md.

Quick reference: Base URL https://api.lemlist.com/api, Basic auth (:apiKey base64-encoded) or Bearer token, rate limit 20 requests per 2 seconds. Key capabilities: campaign CRUD, lead management, sequence steps, enrichment, Lemwarm control, People Database search, inbox/messaging, webhooks.

Always reference references/lemlist-api-reference.md when answering API questions — point the user to it for the full endpoint catalog, request/response schemas, and rate limit details.

Native integrations

  • CRM: HubSpot (native — push leads, sync activity), Salesforce (native — 2-way sync), Pipedrive (native)
  • Enrichment: Apollo, Clay, Clearout, Uplead, Lusha, Pharow
  • Automation: Zapier (triggers for opens, clicks, replies; actions for adding leads), Make, n8n, Pabbly, Relay.app
  • Calling: Aircall, Ringover, Trellus
  • Communication: Slack, WhatsApp (add-on)
  • Data: Airtable, Google Sheets
  • Intent: Snitcher, Lonescale, Phantombuster, Trigify, Albacross
  • Chrome extension: LinkedIn prospecting

Step 4 — Actionable guidance

Based on the user's specific question:

  1. Step-by-step instructions — numbered steps to accomplish their goal in Lemlist
  2. Configuration recommendations — specific settings to change, with navigation paths
  3. Common pitfalls — what can go wrong and how to avoid it
  4. Verification — how to confirm the change worked
  5. For API questions — always include a pointer: "For the full endpoint catalog, request/response schemas, and rate limits, see references/lemlist-api-reference.md."

Gotchas

*Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.*

  • Don't confuse Lemlist's per-seat pricing with unlimited-mailbox tools. Lemlist charges per user/month and limits sending accounts (5 per user on highest plan, $9 per additional inbox). Unlike Instantly or Smartlead which offer unlimited mailboxes on flat-fee plans, Lemlist costs scale with team size and mailbox count. Always check the user's plan before recommending adding more sender accounts.
  • Don't use "campaign" interchangeably with "sequence." Lemlist calls them "sequences" in the UI and "campaigns" in the API. This inconsistency confuses users. Use "sequence" when discussing the UI and "campaign" when discussing the API. If the user says "campaign," clarify which they mean.
  • Don't assume LinkedIn steps are available. LinkedIn automation requires the Multichannel Expert plan ($99/user/month). The Email Pro plan ($69/user/month) is email-only. Ask about the user's plan before building multichannel sequences with LinkedIn steps.
  • Don't skip Lemwarm setup. Lemwarm is free with every seat — there's no reason not to enable it. New accounts without Lemwarm warmup will land in spam. Enable it immediately on every connected email account with at least 30 emails/day warmup volume.
  • Don't ignore LinkedIn daily limits. Lemlist automates LinkedIn actions but LinkedIn still enforces daily limits. Exceeding ~20-30 connection requests/day or ~50-80 profile visits/day risks LinkedIn account restrictions. Claude tends to suggest aggressive LinkedIn step volumes that exceed safe limits.
  • Self-improving: If you discover something not covered here, append it to references/learnings.md with today's date.

Step 5 — Related skills

  • /sales-cadence — Design outbound cadence strategy (platform-agnostic, works with Lemlist sequences)
  • /sales-deliverability — Cross-platform email deliverability — SPF/DKIM/DMARC, warmup, inbox placement
  • /sales-prospect-list — Build prospect lists to import into Lemlist
  • /sales-enrich — Enrich contacts with emails/phones outside of Lemlist's built-in enrichment
  • /sales-integration — Connect Lemlist to other tools via webhooks, Zapier, or API
  • /sales-mailshake — Mailshake platform help (if using Mailshake instead of Lemlist)
  • /sales-smartlead — Smartlead platform help (if using Smartlead instead of Lemlist)
  • /sales-apollo — Apollo.io platform help (if using Apollo instead of Lemlist)
  • /sales-salesloft — Salesloft platform help (if using Salesloft instead of Lemlist)
  • /sales-do — Not sure which skill to use? The router matches any sales objective to the right skill.

Examples

Example 1: Multichannel sequence setup

User says: "How do I create a multichannel sequence in Lemlist with email and LinkedIn?" Skill does:

  1. Confirms user is on Multichannel Expert plan (LinkedIn requires it)
  2. Walks through creating a sequence with email step 1, LinkedIn profile visit day 1, LinkedIn connection request day 2, email follow-up day 4
  3. Explains LinkedIn step configuration — connection request note under 300 chars, daily limit awareness
  4. Recommends enabling Lemwarm on all connected email accounts before launching
  5. Suggests A/B testing subject lines on the first email step Result: User has a multichannel sequence with email + LinkedIn steps ready to launch after warmup

Example 2: Lemwarm setup and deliverability check

User says: "I just connected 3 new email accounts to Lemlist. How do I warm them up?" Skill does:

  1. Walks through enabling Lemwarm on each email account — Warm up section, set to 30 emails/day with gradual ramp-up
  2. Explains the deliverability score (target 90+) and where to monitor it
  3. Stresses minimum 3-5 weeks warmup before adding to sequence rotation
  4. Recommends verifying SPF/DKIM/DMARC and setting up a custom tracking domain
  5. Points to /sales-deliverability for full domain auth framework Result: User has Lemwarm running on all 3 accounts with monitoring plan

Example 3: API lead import and sequence enrollment

User says: "I want to use the Lemlist API to add leads from our CRM to a sequence" Skill does:

  1. Points to references/lemlist-api-reference.md for full API docs
  2. Explains the POST /campaigns/{id}/leads endpoint — email required, custom fields for personalization variables
  3. Shows authentication method (Basic auth with API key)
  4. Warns about rate limits (20 requests per 2 seconds) and recommends batching
  5. Suggests setting up webhooks for reply and interest events to sync back to CRM Result: User knows the endpoint, auth method, required fields, and how to build a bidirectional sync

Troubleshooting

Low open rates

Symptom: Sequence open rates below 30% Cause: Insufficient warmup, missing domain authentication, poor sender reputation, or weak subject lines Solution: Check Lemwarm deliverability score on all email accounts — target 90+ before sequence sends. Verify SPF/DKIM/DMARC in your DNS. Set up a custom tracking domain. A/B test subject lines. See /sales-deliverability for a full diagnosis framework.

LinkedIn steps not executing

Symptom: LinkedIn steps in sequence show as skipped or failed Cause: LinkedIn connection expired, daily limits hit, or user on Email Pro plan (no LinkedIn access) Solution: Verify plan is Multichannel Expert ($99/user/month). Re-authenticate LinkedIn connection in Lemlist settings. Check if daily LinkedIn action limits were exceeded — reduce volume to 20-30 connection requests/day. Verify the lead has a LinkedIn URL in their profile.

Enrichment returning low match rates

Symptom: Waterfall enrichment finding emails for less than 50% of leads Cause: Leads are in niche industries, use uncommon domains, or have limited public data Solution: Ensure you're providing name + company (minimum for email lookup). Try supplementing with external enrichment tools (Clay, Apollo, Lusha) via /sales-enrich. For senior executives with low match rates, consider LinkedIn-first outreach instead of email.

平台分布

Codex

31.98%
按下载量换算146

Claude

31.51%
按下载量换算144

Cursor

18.84%
按下载量换算86

Gemini CLI

9.62%
按下载量换算44

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills