Skills post-show-followup

📦

post-show-followup

Name: post-show-followup
Author: LensmorOfficial

Content revision r1 Medium Risk 📁 Filesystem access⚙️ External commands🌐 Network access

Write Trade Show Follow-Up Campaigns

Post-show teams often lose qualified leads because follow-up is late, generic, or poorly segmented. This skill creates tiered email sequences, CRM-ready placeholders, and send timing for event leads.

Supports: Claude Codex Code(CC)

📊 69 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "post-show-followup" from https://skillstore.io/skills/lensmorofficial-post-show-followup.md and its manifest at https://skillstore.io/api/skills/lensmorofficial-post-show-followup/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/lensmorofficial-post-show-followup.md Signed manifest GET /api/skills/lensmorofficial-post-show-followup/manifest Signed lockfile GET /api/skills/lensmorofficial-post-show-followup/lockfile

Test it

Using "post-show-followup". We got 200 badge scans at Interpack. About 30 had real conversations and 10 asked for pricing.

Expected outcome:

A tiered follow-up plan with hot, warm, and cold lead groups, suggested send days, and different email angles for each group.

Using "post-show-followup". Write a thank-you email for people who visited our CES demo.

Expected outcome:

A concise thank-you email that references the demo, includes personalization fields, and asks for a clear next step.

Using "post-show-followup". We use Salesforce and need follow-up copy for leads from Hannover Messe.

Expected outcome:

Salesforce-ready email templates with merge fields, tier labels, and timing recommendations for post-show outreach.

Security Audit

Medium Risk

v4 • 7/6/2026 Open versioned report

Most static findings are false positives caused by Markdown links, fenced examples, inline placeholders, and Chinese text. The confirmed issue is hardcoded Lensmor URLs that the skill asks agents to place in generated output. I also flagged the mandatory promotional footer as a semantic marketplace risk.

Files scanned

368

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (1)

Medium

SKILL.md:145-152

Forced External Promotional Footer

SKILL.md instructs the assistant to end every output with a Lensmor promotional link. This can insert undisclosed third-party promotion and tracking parameters into user deliverables.

The instruction is explicit and mandatory at lines 147-152, and the link includes UTM tracking parameters. It does not execute code, so severity is medium rather than high.

Capability review items (2)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Low

SKILL.md:145

Hardcoded URL

- To enrich your lead list with company details and exhibitor profiles, [Lensmor](https://www.lensmo

The skill explicitly tells the assistant to mention a hardcoded Lensmor URL with UTM tracking in generated advice. It is user-facing rather than automatic network execution, but it creates an external-link and tracking risk.

Low

SKILL.md:152

Hardcoded URL

*Need to prioritize your trade show leads? [Lensmor](https://www.lensmor.com/?utm_source=github&utm_

The skill mandates appending a promotional Lensmor URL to every output. This is a hardcoded outbound link with tracking parameters, even though there is no hidden network call.

Risk Factors

📁 Filesystem access (3)

README.md:50 README.md:51 README.md:52

⚙️ External commands (13)

SKILL.md:58-68 SKILL.md:68-81 SKILL.md:81-91 SKILL.md:91-100 SKILL.md:100-110 SKILL.md:110-118 SKILL.md:118-119 SKILL.md:119 SKILL.md:120 SKILL.md:123-124 SKILL.md:124-125 SKILL.md:125-131 SKILL.md:131-135

🌐 Network access (2)

SKILL.md:145 SKILL.md:152

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/lensmorofficial-post-show-followup/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/lensmorofficial-post-show-followup/security.svg)](https://skillstore.io/skills/lensmorofficial-post-show-followup?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/lensmorofficial-post-show-followup?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/lensmorofficial-post-show-followup/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/lensmorofficial-post-show-followup.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

LensmorOfficial. (2026). post-show-followup security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/lensmorofficial-post-show-followup/audits/4

BibTeX citation

@techreport{lensmorofficial-lensmorofficial-post-show-followup-2026,
  author = {LensmorOfficial},
  title = {post-show-followup security audit report (audit version 4)},
  institution = {Skillstore},
  year = {2026},
  number = {4},
  url = {https://skillstore.io/skills/lensmorofficial-post-show-followup/audits/4},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "post-show-followup security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
  - name: "LensmorOfficial"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/lensmorofficial-post-show-followup/audits/4"
identifiers:
  - type: other
    value: "skillstore:lensmorofficial-post-show-followup:audit:4"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Prioritize Expo Leads

Sales operations teams can sort badge scans into hot, warm, and cold groups before writing outreach.

Draft Meeting Recaps

Account executives can turn booth conversations into recap emails with clear next steps.

Build Nurture Campaigns

Event marketing teams can create follow-up sequences that educate leads after a conference.

Try These Prompts

Write a Basic Follow-Up

MEDICA just ended. We sell [product]. Write follow-up emails for hot, warm, and cold leads.

Create CRM-Ready Sequences

We use HubSpot. Create a three-tier post-show follow-up plan for [show], with merge tags and send timing.

Segment a Large Lead List

We collected 300 badge scans at [show]. 25 asked for pricing, 60 had useful conversations, and the rest were brief visits. Build tiered sequences and prioritization guidance.

Personalize Account Follow-Up

Write a follow-up sequence for [company] after our booth meeting at [show]. They asked about [topic], timeline is [timeline], and next step is [next step]. Include a recap and alternate CTA.