Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

lynqu-sales-followup

Estrelas4

Forks0

Atualizado18 de junho de 2026 às 13:50

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).

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

Gravisun

Gravisun/lynqu-ai-toolkit

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Representantes de vendas de serviços (exceto publicidade, seguros, serviços financeiros e viagens)Vendas e Ocupações Afins·SOC 41-3091

SKILL.md

readonly

name	lynqu-sales-followup
description	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).

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-now is 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 to create-followup-template (HTML with mustache tokens).
Select the leads. list-leads (filter by tag/stage/campaign/owner) and get-lead for 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-now per approved lead (it goes through the CAN-SPAM-compliant pipeline). Record the touch with add-lead-note, and advance the stage with update-lead-stage if 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-2026 in 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."

Mais deste repositório

mesmo repositório

lynqu-card-studio

Gravisun/lynqu-ai-toolkit

Create and update Lynqu digital business cards conversationally — contact info, social links, services, template, and color palette — and check how a card is performing. Use for "make me a digital business card", editing a card, setting up team cards, or checking card views/scans/shares. Works on the personal server (/mcp/me) and the org server (/mcp/v2). Requires the Lynqu MCP server connected.

2026-06-184

lynqu-event-blitz

Gravisun/lynqu-ai-toolkit

Run a complete event lead-capture workflow in Lynqu end-to-end — set up the event and campaign, capture booth/conference leads, tag and attribute them, then kick off follow-up. Use for conference, trade show, or booth lead capture, "set up our event in Lynqu", event ROI/attribution, or post-event processing. Requires the Lynqu MCP server connected (https://api.lynqu.com/mcp/v2).

2026-06-184

lynqu-lead-capture

Gravisun/lynqu-ai-toolkit

Capture new leads into Lynqu — from scanned badges, business cards, event lists, or a paste of names — then dedupe against existing contacts, tag them, and route them into the right pipeline. Use for lead capture, importing contacts, "add these people as leads", post-event data entry, or turning a list into a working pipeline. Requires the Lynqu MCP server connected (https://api.lynqu.com/mcp/v2).

2026-06-184

lynqu-lead-management

Gravisun/lynqu-ai-toolkit

Keep the Lynqu sales pipeline clean and moving — advance leads through stages, assign owners, score and tag, run bulk hygiene, and surface stalled deals. Use for pipeline management, lead routing, "tidy up my pipeline", reassigning leads, moving deals between stages, or weekly pipeline grooming. Requires the Lynqu MCP server connected (https://api.lynqu.com/mcp/v2).

2026-06-184

lynqu-lead-research

Gravisun/lynqu-ai-toolkit

Find and qualify target accounts and decision-makers before an event or outbound campaign, then create them as leads in Lynqu. Use for AI lead research, lead generation, prospecting, building a target account list, or "who should we talk to" — especially before a conference, trade show, or campaign. Requires the Lynqu MCP server connected (https://api.lynqu.com/mcp/v2).

2026-06-184

lynqu-pipeline-report

Gravisun/lynqu-ai-toolkit

Generate a pipeline and performance report from Lynqu — what moved, what's stalling, campaign and event ROI, card engagement, and who needs attention. Use for weekly pipeline review, sales reporting, "how's the pipeline looking", campaign performance, lead/card analytics, or a stand-up summary. Read-only. Requires the Lynqu MCP server connected (https://api.lynqu.com/mcp/v2).

2026-06-184

name	lynqu-sales-followup
description	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).

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-now is 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 to create-followup-template (HTML with mustache tokens).
Select the leads. list-leads (filter by tag/stage/campaign/owner) and get-lead for 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-now per approved lead (it goes through the CAN-SPAM-compliant pipeline). Record the touch with add-lead-note, and advance the stage with update-lead-stage if 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-2026 in 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."