Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

lynqu-card-studio

Sterne4

Forks0

Aktualisiert18. Juni 2026 um 13:50

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.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

Gravisun

Gravisun/lynqu-ai-toolkit

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Dienstleistungsvertriebsmitarbeiter (außer Werbung, Versicherung, Finanzdienstleistungen und Reisen)Verkaufsberufe·SOC 41-3091

SKILL.md

readonly

name

lynqu-card-studio

description

Lynqu Card Studio

The doorway. A great card is how the relationship starts — this skill builds and tunes them by conversation, and tells you how they're performing.

When to use this

Creating a first card, or a card for a new role/event/persona.
Editing contact info, links, services, template, or palette.
Checking a card's engagement (views, scans, shares, saves).

Prerequisites

Lynqu MCP connected. Personal users: /mcp/me. Teams: /mcp/v2. See ../../docs/mcp/connect.md.
AI-tier plan for write tools.

Workflow

See what exists. Call list-cards and get-card on the relevant card so you build on, not over, what's there. The server exposes a card schema resource — consult it for valid fields/shapes.
Gather the essentials. Name, title, company, the contact channels to show (email, phone, website), social links, and any services. For a team card, confirm whose card it is.
Create or update.
- New card → create-card with the gathered fields.
- Changes → update-card (links, services, template, palette). Make changes incrementally and read back the result so the user can confirm.
Style it. Set the template and color palette to match brand. Describe the look in words and apply via update-card; confirm with the user.
Measure. Use get-card-stats for a specific card and get-dashboard-summary for the bigger picture — views, scans, shares, saves, engagement — and suggest tweaks (e.g. "your scan→save rate is low; tighten the headline").

Tools used

list-cards, get-card, create-card, update-card, get-card-stats, get-dashboard-summary.

Guardrails

Don't overwrite blindly. Read the card first; apply targeted updates.
Confirm contact details with the user — a card is public-facing; wrong info is worse than missing info.
Personal vs. org scope matters: the personal server only sees the signed-in user's cards. For team cards, use the org server.

Example

"Create a digital business card for me as 'Head of Partnerships at Acme', include my work email and LinkedIn, add 'Partnership programs' as a service, use a clean dark template with a purple palette, then show me how my existing card has been performing this month."

Mehr aus diesem Repository

gleiches Repository

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

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

description

Lynqu Card Studio

The doorway. A great card is how the relationship starts — this skill builds and tunes them by conversation, and tells you how they're performing.

When to use this

Creating a first card, or a card for a new role/event/persona.
Editing contact info, links, services, template, or palette.
Checking a card's engagement (views, scans, shares, saves).

Prerequisites

Lynqu MCP connected. Personal users: /mcp/me. Teams: /mcp/v2. See ../../docs/mcp/connect.md.
AI-tier plan for write tools.

Workflow

See what exists. Call list-cards and get-card on the relevant card so you build on, not over, what's there. The server exposes a card schema resource — consult it for valid fields/shapes.
Gather the essentials. Name, title, company, the contact channels to show (email, phone, website), social links, and any services. For a team card, confirm whose card it is.
Create or update.
- New card → create-card with the gathered fields.
- Changes → update-card (links, services, template, palette). Make changes incrementally and read back the result so the user can confirm.
Style it. Set the template and color palette to match brand. Describe the look in words and apply via update-card; confirm with the user.
Measure. Use get-card-stats for a specific card and get-dashboard-summary for the bigger picture — views, scans, shares, saves, engagement — and suggest tweaks (e.g. "your scan→save rate is low; tighten the headline").

Tools used

list-cards, get-card, create-card, update-card, get-card-stats, get-dashboard-summary.

Guardrails

Don't overwrite blindly. Read the card first; apply targeted updates.
Confirm contact details with the user — a card is public-facing; wrong info is worse than missing info.
Personal vs. org scope matters: the personal server only sees the signed-in user's cards. For team cards, use the org server.

Example

"Create a digital business card for me as 'Head of Partnerships at Acme', include my work email and LinkedIn, add 'Partnership programs' as a service, use a clean dark template with a purple palette, then show me how my existing card has been performing this month."