Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

lynqu-lead-research

Étoiles4

Forks0

Mis à jour18 juin 2026 à 13:50

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

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

Gravisun

Gravisun/lynqu-ai-toolkit

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Représentants de vente de services (sauf publicité, assurance, services financiers et voyages)Vente et professions connexes·SOC 41-3091

SKILL.md

readonly

name	lynqu-lead-research
description	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).

Lynqu Lead Research

Turn a fuzzy "who should we go after?" into a ranked, qualified target list that lands directly in your Lynqu pipeline.

When to use this

Building a target account list for an event, campaign, or territory.
Researching companies/people you're about to meet.
Qualifying inbound interest against your ICP before working it.

Prerequisites

Lynqu MCP connected (org server /mcp/v2). See ../../docs/mcp/connect.md.
An AI-tier plan to run write tools.

Workflow

Anchor on the ICP. Ask the user (or infer from existing won leads) for: industry, company size, geography, role/title of the decision-maker, and the pain Lynqu solves for them. If they're unsure, pull signal from what's already working: call list-leads and get-lead on a few won leads to see common firmographics.
Understand the current book. Call get-org-summary and list-campaigns so you don't research accounts already in flight. Use search-contacts to check whether a candidate is already known.
Research candidates. Using your own web/search capabilities, assemble a shortlist. For each: company, why it fits the ICP, a named decision-maker, their role, a public profile link, and a growth/trigger signal (hiring, funding, expansion, attending the same event).
Score the fit (1–10). Rank on ICP match + buying signal. Show the user the ranked table and let them prune before anything is written.
Create leads for the keepers. For each approved candidate call create-lead with name, company, role, source ("research"), and a note capturing the fit rationale via add-lead-note. If researching for a specific campaign, attach-leads-to-campaign.
Hand off. Summarize what was created and suggest the next skill — usually lynqu-sales-followup for outreach or lynqu-lead-management to set stages and owners.

Tools used

get-org-summary, list-campaigns, search-contacts, list-leads, get-lead, create-lead, add-lead-note, attach-leads-to-campaign.

Guardrails

Never invent contact data. If you can't verify an email/phone, leave it blank and note "unverified" rather than guessing.
Confirm before writing. Show the ranked list and get a go-ahead before calling create-lead — research is cheap to redo, a polluted pipeline isn't.
Respect the role gate: attach-leads-to-campaign is employee-level, but campaign creation needs manager+.

Example

"Build me a list of 10 mid-market SaaS companies in the DACH region attending SaaStr Europe, find a VP of Sales or RevOps lead at each, score them for Lynqu, and create leads for anything 7+."

Plus depuis ce dépôt

même dépôt

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

lynqu-sales-followup

Gravisun/lynqu-ai-toolkit

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

2026-06-184

name	lynqu-lead-research
description	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).

Lynqu Lead Research

Turn a fuzzy "who should we go after?" into a ranked, qualified target list that lands directly in your Lynqu pipeline.

When to use this

Building a target account list for an event, campaign, or territory.
Researching companies/people you're about to meet.
Qualifying inbound interest against your ICP before working it.

Prerequisites

Lynqu MCP connected (org server /mcp/v2). See ../../docs/mcp/connect.md.
An AI-tier plan to run write tools.

Workflow

Anchor on the ICP. Ask the user (or infer from existing won leads) for: industry, company size, geography, role/title of the decision-maker, and the pain Lynqu solves for them. If they're unsure, pull signal from what's already working: call list-leads and get-lead on a few won leads to see common firmographics.
Understand the current book. Call get-org-summary and list-campaigns so you don't research accounts already in flight. Use search-contacts to check whether a candidate is already known.
Research candidates. Using your own web/search capabilities, assemble a shortlist. For each: company, why it fits the ICP, a named decision-maker, their role, a public profile link, and a growth/trigger signal (hiring, funding, expansion, attending the same event).
Score the fit (1–10). Rank on ICP match + buying signal. Show the user the ranked table and let them prune before anything is written.
Create leads for the keepers. For each approved candidate call create-lead with name, company, role, source ("research"), and a note capturing the fit rationale via add-lead-note. If researching for a specific campaign, attach-leads-to-campaign.
Hand off. Summarize what was created and suggest the next skill — usually lynqu-sales-followup for outreach or lynqu-lead-management to set stages and owners.

Tools used

get-org-summary, list-campaigns, search-contacts, list-leads, get-lead, create-lead, add-lead-note, attach-leads-to-campaign.

Guardrails

Never invent contact data. If you can't verify an email/phone, leave it blank and note "unverified" rather than guessing.
Confirm before writing. Show the ranked list and get a go-ahead before calling create-lead — research is cheap to redo, a polluted pipeline isn't.
Respect the role gate: attach-leads-to-campaign is employee-level, but campaign creation needs manager+.

Example

"Build me a list of 10 mid-market SaaS companies in the DACH region attending SaaStr Europe, find a VP of Sales or RevOps lead at each, score them for Lynqu, and create leads for anything 7+."