Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

lynqu-lead-management

Estrelas4

Forks0

Atualizado18 de junho de 2026 às 13:50

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

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-lead-management
description	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).

Lynqu Lead Management

The pipeline only tells the truth if it's maintained. This skill grooms it: right stage, right owner, right tags, no rot.

When to use this

Weekly pipeline grooming / hygiene.
Reassigning leads after a territory or staffing change.
Bulk-moving or re-tagging a set of leads.
Finding and unsticking stalled deals.

Prerequisites

Lynqu MCP connected (/mcp/v2). See ../../docs/mcp/connect.md.
AI-tier plan. Note: assign-lead and move-lead-environment need manager+; stage moves and notes are employee-level.

Workflow

Map the pipeline. Call list-lead-environments and get-pipeline-stages to learn the tabs and columns. Call list-team-members to get owners (and both user_id / organization_user_id).
Pull the working set. list-leads filtered to the scope the user cares about (an environment, an owner, a stage, a tag). get-lead for detail and the activity timeline where needed.
Diagnose. Identify: leads with no owner, leads stalled in a stage past a threshold (use timeline timestamps), mis-staged leads, missing tags/score. Present findings as a short list before changing anything.
Act, with confirmation.
- Advance/correct stage → update-lead-stage.
- Assign/reassign owner → assign-lead (uses user_id).
- Move to a different kanban tab → move-lead-environment.
- Re-tag / set temperature / score in batches → bulk-update-leads (≤ 100 per call).
- Log context → add-lead-note.
Report. Summarize what changed and what needs a human decision (e.g. "3 deals stalled 21+ days in Demo — recommend follow-up or close-lost").

Tools used

list-lead-environments, get-pipeline-stages, list-team-members, list-leads, get-lead, update-lead-stage, assign-lead, move-lead-environment, bulk-update-leads, add-lead-note.

Guardrails

Confirm bulk actions with a count and a sample before executing.
Use the right identifier: assign-lead takes user_id, not organization_user_id — list-team-members gives you both.
bulk-update-leads is capped at 100 — chunk and report progress.
Don't auto-close deals; flag close-lost candidates for human sign-off.

Example

"Groom the Inbound pipeline: list anything unassigned, round-robin it across the active SDRs, flag deals stuck in Qualified for 14+ days, and bulk-set temperature to cold for anything untouched in 30 days."

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

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

Lynqu Lead Management

The pipeline only tells the truth if it's maintained. This skill grooms it: right stage, right owner, right tags, no rot.

When to use this

Weekly pipeline grooming / hygiene.
Reassigning leads after a territory or staffing change.
Bulk-moving or re-tagging a set of leads.
Finding and unsticking stalled deals.

Prerequisites

Lynqu MCP connected (/mcp/v2). See ../../docs/mcp/connect.md.
AI-tier plan. Note: assign-lead and move-lead-environment need manager+; stage moves and notes are employee-level.

Workflow

Map the pipeline. Call list-lead-environments and get-pipeline-stages to learn the tabs and columns. Call list-team-members to get owners (and both user_id / organization_user_id).
Pull the working set. list-leads filtered to the scope the user cares about (an environment, an owner, a stage, a tag). get-lead for detail and the activity timeline where needed.
Diagnose. Identify: leads with no owner, leads stalled in a stage past a threshold (use timeline timestamps), mis-staged leads, missing tags/score. Present findings as a short list before changing anything.
Act, with confirmation.
- Advance/correct stage → update-lead-stage.
- Assign/reassign owner → assign-lead (uses user_id).
- Move to a different kanban tab → move-lead-environment.
- Re-tag / set temperature / score in batches → bulk-update-leads (≤ 100 per call).
- Log context → add-lead-note.
Report. Summarize what changed and what needs a human decision (e.g. "3 deals stalled 21+ days in Demo — recommend follow-up or close-lost").

Tools used

list-lead-environments, get-pipeline-stages, list-team-members, list-leads, get-lead, update-lead-stage, assign-lead, move-lead-environment, bulk-update-leads, add-lead-note.

Guardrails

Confirm bulk actions with a count and a sample before executing.
Use the right identifier: assign-lead takes user_id, not organization_user_id — list-team-members gives you both.
bulk-update-leads is capped at 100 — chunk and report progress.
Don't auto-close deals; flag close-lost candidates for human sign-off.

Example

"Groom the Inbound pipeline: list anything unassigned, round-robin it across the active SDRs, flag deals stuck in Qualified for 14+ days, and bulk-set temperature to cold for anything untouched in 30 days."