Lynqu sales followup
Open-source Claude Skills + MCP for AI lead capture, lead research, sales follow-up & pipeline management — run Lynqu from Claude, ChatGPT & Cursor.
npx -y skills add Gravisun/lynqu-ai-toolkit --skill lynqu-sales-followupAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Draft and send on-brand sales follow-up emails to Lynqu leads using your follow-up templates, and log them to the lead timeline. Use for sales follow-up, post-event outreach, "follow up with these leads", nurture sequences, or "what should I say to this prospect". Requires the Lynqu MCP server connected (https://api.lynqu.com/mcp/v2).
SKILL.md
3.0 KB, as published. Nobody here has run it
Lynqu Sales Follow-up
The money is in the follow-up. This skill turns "I met 40 people" into timely, personalized, on-brand outreach — sent through Lynqu's compliant pipeline and logged against each lead.
When to use this
- Post-event follow-up to freshly captured leads.
- Re-engaging stalled deals.
- Drafting a personalized note for a specific prospect.
Prerequisites
- Lynqu MCP connected (
/mcp/v2). See../../docs/mcp/connect.md. - AI-tier plan.
send-followup-nowis employee-level; creating new templates needs manager+.
Workflow
- Find the right template. Call
list-followup-templates. Match the situation (post-event, demo recap, re-engage). If nothing fits and the user is manager+, offer tocreate-followup-template(HTML with mustache tokens). - Select the leads.
list-leads(filter by tag/stage/campaign/owner) andget-leadfor the personalization details — name, company, where you met, what they cared about (read the activity timeline). - Personalize. Draft per-lead copy that fills the template tokens. Keep it short, specific, and honest. Do not reference when the interaction happened ("yesterday", "last night") — it's stale by send time and reads as surveillance. Lead with relevance, not a timestamp.
- Review before send. Show the user the drafts (or a representative sample for a batch) and get explicit approval. Sending email is outward-facing and not reversible.
- Send & log. Call
send-followup-nowper approved lead (it goes through the CAN-SPAM-compliant pipeline). Record the touch withadd-lead-note, and advance the stage withupdate-lead-stageif the follow-up implies progress. - Suggest cadence. Recommend the next touch timing and flag who to follow up with again, but don't schedule sends the user hasn't approved.
Tools used
list-followup-templates, create-followup-template, list-leads,
get-lead, send-followup-now, add-lead-note, update-lead-stage.
Guardrails
- Always get explicit approval before sending. Sending is irreversible and represents the user's brand.
- No timestamps of the prospect's action in the copy (stale + creepy).
- Don't invent claims about the product or the prior conversation — ground personalization in the lead's actual timeline.
- Respect unsubscribes/compliance — sends route through Lynqu's compliant pipeline; never try to bypass it.
Example
"Draft post-event follow-ups for everyone tagged
SaaStr-2026in the Warm stage using the 'Event recap' template, personalize from each lead's notes, show me the drafts, and after I approve, send and log them."