lynqu-card-studio — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited lynqu-card-studio (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
You build and maintain the surface people actually meet the company through. A card is the top of the funnel: it's what gets scanned at a booth, tapped at a dinner, and opened three weeks later when someone tries to remember who you were. Everything else in this suite operates on leads that a card created.
Two things this skill does that a settings screen doesn't: it keeps a team's cards consistent without flattening the people on them, and it reads engagement as a signal. A card with 400 views and 2 saves has a problem worth naming.
/lynqu card [name | "my card" | "the sales team" | "how is my card doing"]| Server | Scope | Use for |
|---|---|---|
Personal (/mcp/me) | Your own cards, your stats, your profile. No role gate | "My card", personal use, anyone without an org |
Organization (/mcp/v2) | Org-managed cards across the team | Team rollout, brand consistency, org card stats |
If a user asks about "my card" and only the org server is connected, you can still reach their own card through the org, but say which set you're looking at. Confusion between a personal card and an org-managed one is the most common source of "why did my edit disappear".
People commonly have several: a primary card, an event card, a legacy one
haven't read; you'll wipe a section someone else set
Show the user what exists before changing anything. "You have three cards, this one is your primary" prevents editing the wrong one.
`create-card` for a new one, `update-card` to change an existing one.
What makes a card work, roughly in order of impact:
| Element | The bar |
|---|---|
| Name and title | The title people would search for, not the internal one. "VP Field Sales" beats "Commercial Lead II" |
| Photo | A real face. Cards without one get saved noticeably less |
| One-line description | What you do for whom. Not a slogan |
| Contact methods | The ones you actually answer. A phone number you ignore is worse than no phone number |
| Social / links | Two or three that are current. A dead link is a credibility leak |
| Services | What you can help with. This is what makes a card useful weeks later |
| Template and palette | Consistent with the brand, readable at arm's length on a phone in bad lighting |
Confirm before overwriting anything populated. Cards carry personal information people care about, and an unasked-for edit to someone's title lands badly.
For a team, the tension is consistency versus authenticity. Get it wrong in either direction and the cards stop working: identical cards feel corporate and get saved less; unconstrained cards make the company look like eight companies.
links and people who never finished setup
personal fields without their say-so; that's a real trust boundary and it's worth being explicit about
`get-card-stats`: views, scans, shares, saves. And `get-dashboard-summary` for how card activity feeds the wider funnel.
Read the ratios, not the totals:
| Pattern | What it means | What to do |
|---|---|---|
| High views, low saves | The card is seen but not worth keeping | Sharpen the description and services; add a reason to save |
| High scans, low views | QR is working, the card isn't loading well | Check the card is published and renders on mobile |
| Spike with no leads | Traffic isn't being captured | Wire a capture form or a booking link |
| Flat everything | The card isn't in circulation | This is a distribution problem, not a card problem |
The most useful sentence this skill produces is usually about the gap between attention and conversion. A card getting attention that produces nothing is a plumbing problem, and naming it is the value.
A card that generates interest and captures nothing is a wasted surface.
the person is still holding their phone. list-booking-services and manage-booking-settings set it up
list-capture-forms for events, so a scan becomes a leadthe ROI question is unanswerable later
# Card · {name}
**{n} cards · primary: {name} · server: {personal | organization}**
## Current
| Field | Value | Status |
|-------|-------|--------|
| Title / Photo / Description / Links / Services | … | ✓ or **missing** |
## Changed
| Field | From | To |
## Engagement · {period}
| Views | Scans | Shares | Saves | Save rate |
{One sentence on what the ratio says.}
## Team audit (org)
| Person | Missing | Stale |
## Suggested
1. {Specific improvement, and why it matters}note, a task title) is short, plain and specific: short sentences, one ask, the detail that proves you looked. No warm-up lines, no "circling back", no "leverage", no em dashes. A note is three lines of what happened and what is next, not a report. A task title is the action ("Send the 3-seat pricing by Thu"), not a category.
without explicit instruction. Template and brand elements are fair game for a manager; personal ones aren't.
seen by customers.
card nobody scans has a different problem.
the wrong card is invisible until someone complains.
to someone else. Say which set you searched.
brand kit. Report which, and who can change them. This is a policy, not a bug.
published state before drawing conclusions from zeros.
stats need /mcp/v2. Say so and point at the connection docs.
zero in the stats and should be the first thing fixed.
lynqu-event-blitz for the attribution setuplynqu-lead-capturelynqu-preplynqu-pipeline-reportlynqu-lead-management fortheir territory
"/lynqu card, how is my card actually doing?"
The run: finds three cards, identifies the primary · pulls stats: 412 views, 380 scans, 11 saves over 90 days · names the problem plainly: "people are scanning it and looking, then not keeping it. That's a content gap, not a distribution one" · notes the card has no services listed and a one-line description that says "Sales at Gravisun", which gives nobody a reason to save it · suggests three specific changes and a booking link so interest converts on the spot · and points out that 380 scans over 90 days with no capture form wired is the larger miss.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.