Comprehensive SaaS market research skill for identifying Existential Data Points (EDPs) — the critical metrics that transform a solution from nice-to-have to must-have. Use this skill whenever the user asks to research a SaaS market, identify outbound plays, find pain points for a category, analyze a vertical, or discover urgency triggers for outbound campaigns. Trigger on phrases like "research the [X] market", "find EDPs for [X]", "outbound play for [category]", "analyze [SaaS] market", "what's the pain in [vertical]", or any request to understand a SaaS category for sales/growth purposes. ALWAYS use this skill when the user is doing market research for outbound or sales enablement.
Debugs n8n workflow errors from error messages, screenshots, or both. Use this skill whenever the user shares an n8n error, a broken workflow, an unexpected output, or asks why a workflow is not working — even if they just paste an error message, say "it's broken", "it's not working", or "why does this fail". Covers all node types, API errors, expression errors, credential issues, data mapping problems, and logic bugs.
Builds production-ready n8n workflows as directly importable JSON, following market best practices. Use this skill whenever the user wants to create, improve, or refactor an n8n workflow — even if they just say "automate this", "build a flow", "connect these tools", or "how would I do this in n8n". Also trigger when the user shares a diagram, screenshot, or text description of an automation they want to build. Covers outreach automation, CRM sync, webhook/API integrations, and lead enrichment workflows with tools like lemlist, Clay, HubSpot, Salesforce, Slack, and Notion.
Discover 3–5 high-quality, complementary B2B data sources with strong buying intent signals for a specific industry, solution, or target market. Use when asked "find data sources for [vertical]", "where can I find companies that [characteristic]", "how do I build a list of [target]", "best sources for [industry] leads", "alternatives to LinkedIn for prospecting", "where to find companies with [signal]", or "data sources for [use case]". Do NOT use for individual contact data, email verification, or CRM/tool functionality questions.
Transform product descriptions and feature lists into compelling, outcome-focused offers for cold outreach. Use when asked "how to frame my offer", "what should I say in cold emails", "how to pitch my product", "make my offer clearer", "value proposition for outreach", "how do I explain what we do", "turn features into benefits", or "write a one-liner for my product". Use after ICP and persona are defined, before writing outreach copy.
Analyze and benchmark outbound campaign performance against real lemlist data from 244K+ campaigns and 249M+ emails. Use when asked "are my stats good", "is my reply rate good", "why am I not getting replies", "is my open rate normal", "how do I compare to benchmarks", "my campaign is underperforming", "what's a good reply rate", "is X% good for cold email", "my LinkedIn acceptance rate is low", "how many emails should I send per day", "my deliverability is bad", "analyze my campaign stats", or any question involving outreach metrics, rates, or performance. Always use this skill before giving any opinion on whether a stat is good or bad. This skill gives instant verdicts with real data — not vague "it depends" answers.
Designs high-performance outbound sequences based on ICP, available channels, and empirical lemlist data from hundreds of thousands of campaigns. Use this skill whenever the user wants to build, design, or optimize an outbound sequence, campaign, or cadence — whether they say "create a sequence", "build a campaign", "what steps should I use", "how should I structure my outreach", or "help me reach out to X". Also trigger when the user mentions an ICP + a goal (e.g. "I want to book meetings with VP Sales at Series B SaaS"). Always use this skill before any sequence is written.
Identify and prioritize evidence-based pain points a target company likely faces, based on growth signals, tech stack, hiring activity, and industry context. Use when asked "what are [company]'s pain points", "research pain points for [company]", "why would [company] buy", "what problems does [company] face", "qualify this lead", "account research for [company]", "help me personalize outreach to [company]", or "what signals should I mention in my email to [company]".
Translates an ICP and persona definition into a step-by-step guide for configuring lemlist's people database search to find the right contacts. Use when asked "find me contacts", "who do I search for in lemlist", "how do I find the right person to email", "build a contact list in lemlist", "search for [role] in lemlist", or after list-builder routes to contact-level targeting. Produces a pedagogical, step-by-step filter guide tailored to the ICP and persona.
Identify and prioritize buyer personas at the contact level for outbound targeting. Use when asked "who should I email", "define buyer persona", "what role to target", "who is the decision maker", "who has this pain", "which title to reach out to", "should I target VPs or Directors", or "contact-level targeting". Use AFTER ICP is defined (ICP = which companies, Persona = which person at those companies).
Analyzes sales call transcripts to produce deep, structured persona intelligence reports. Use this skill whenever the user wants to understand their buyers better, extract insights from call recordings, build persona profiles, or analyze patterns across discovery calls — even if they just say "analyze my calls", "what are my buyers saying", "build a persona", "extract insights from transcripts", or share transcripts via CSV, MCP (Claap, Modjo, Gong, Chorus), or raw text paste. Always produces a full persona report with goals, pains, objections, feature requests, verbatims, buying signals, and strategic recommendations.
Runs a full sales pipeline analysis and renders an interactive visual dashboard. Use this skill whenever the user shares deal data (CSV, HubSpot, Salesforce) and wants to analyze their pipeline — even if they just say "analyze my pipeline", "how's my pipeline looking", "show me my deals", "forecast this month", or "who's my top rep". Covers pipeline value, stage conversion, stuck deals, forecast, rep performance, and sales velocity. Always produces an interactive visual artifact as output.
Transforms any rough, vague, or underperforming prompt into a production-ready, optimized prompt for Claude. Use this skill whenever the user wants to improve a prompt, says "make this prompt better", "optimize this", "my prompt isn't working", "write me a prompt for X", or shares any instruction they want Claude to follow reliably. Covers system prompts, user prompts, and agent/workflow prompts. Always produces the optimized prompt + a clear explanation of every choice made.
Analyze cold outreach replies and craft the right response based on a relationship-first philosophy. Use when asked "how to reply to this", "they said X what do I say", "handle this objection", "got a response from a prospect", "interested reply", "not interested reply", "next step after reply", "competitor objection", "pricing question", or "how do I respond to this email/LinkedIn message". Always use this skill before writing any reply to a prospect.
Builds polished, professional .pptx slide decks from a source document (PDF, Word, text). Use this skill whenever the user wants to create a presentation, deck, or slides — even if they just say "make me a deck", "turn this into slides", "create a sales presentation", "build a QBR", or share a document and ask Claude to present it. Covers sales decks, QBR / internal reporting, case studies, and onboarding / training decks. Always produces a downloadable .pptx file as output.
Buying trigger analysis skill for outbound sales teams. Identifies and interprets trigger events (funding, hiring, tool changes, job changes, LinkedIn activity, M&A, etc.) to help time outreach and sharpen messaging. Works in two modes: (1) Strategic — given an ICP, recommends the best triggers to activate and the right messaging angle for each; (2) Tactical — given a specific company or signal, explains how to exploit it right now. ALWAYS use this skill when the user mentions signals, triggers, buying intent, "right time to reach out", timing outreach, "they just raised", "they just hired", "they changed jobs", job postings, funding rounds, tech stack changes, LinkedIn activity, or any event-based prospecting. Use it even if the user just says "when should I reach out to X".
Extract and organize all value propositions from a company website or materials into a structured inventory, categorized by type and mapped to personas and outreach channels. Use when asked "list my value props", "what value do we provide", "extract our benefits", "summarize our value propositions", "what should I highlight in outreach", "organize our messaging", or "what do we offer customers". Use to inform offer framing, email copy, and sales enablement.
Scrapes structured data from any website and exports it to a clean CSV file. Use this skill whenever the user provides a URL and wants to extract specific information from it — even if they just say "scrape this site", "extract all the contacts from this page", "get me the pricing from this URL", "pull all the job listings", or "grab the data from this website into a CSV". Handles single pages, paginated results, sitemaps, and multi-page scraping. Always produces a downloadable CSV file as output.
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.