trade-show-competitor-radar

trade-show-competitor-radar is a skill for Claude Code from LensmorOfficial/trade-show-skills. It costs 102 tokens per session (1,696 once invoked), scanned A, original, MIT.

A guide for turning observations made at a trade show into organized competitor notes. A trade show is an industry event where companies display products, meet customers, and announce updates.

In plain words
What is it for?
Use it to record competitor booth visits, brochure text, product announcements, pricing clues, and overheard messages during or just after an event.
Why use it?
It separates direct observations and printed evidence from unverified comments, so sales, product, and leadership teams can judge the information more reliably.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: built for openclaw.

Good fit Use it to record competitor booth visits, brochure text, product announcements, pricing clues, and overheard messages during or just after an event.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lensmorofficial/trade-show-skills/trade-show-competitor-radar
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add LensmorOfficial/trade-show-skills --skill trade-show-competitor-radar
Clone the repo
git clone --depth 1 https://github.com/LensmorOfficial/trade-show-skills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for trade-show-competitor-radar

README.md
[![agentmods](https://agentmods.dev/badge/skills/lensmorofficial/trade-show-skills/trade-show-competitor-radar/github.svg)](https://agentmods.dev/skills/lensmorofficial/trade-show-skills/trade-show-competitor-radar)
Your own site
<a href="https://agentmods.dev/skills/lensmorofficial/trade-show-skills/trade-show-competitor-radar"><img src="https://agentmods.dev/badge/skills/lensmorofficial/trade-show-skills/trade-show-competitor-radar/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for trade-show-competitor-radar

Your own site · 80×15
<a href="https://agentmods.dev/skills/lensmorofficial/trade-show-skills/trade-show-competitor-radar"><img src="https://agentmods.dev/badge/skills/lensmorofficial/trade-show-skills/trade-show-competitor-radar.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,696 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00102 $0.01696
Opus 5 $0.00051 $0.00848
Sonnet 5 $0.00020 $0.00339
Haiku 4.5 $0.00010 $0.00170

Measured 13d ago against content hash db07256f81d8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

trade-show-competitor-radar scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

trade-show-competitor-radar/SKILL.md · 139 lines

How it starts

The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Competitor Radar

Turn raw show-floor observations — typed notes, brochure text, overheard messaging, product announcement snippets — into structured competitive intelligence that your team can actually act on.

When this skill triggers:

  • Use it during the show or right after booth visits while the observations are still fresh
  • Use it for field-intel that needs explicit evidence tags before it reaches sales, product, or leadership
  • Do not use it for pre-show public research; use pre-show-competitor-analysis for that

Workflow

Step 1: Structure Field Notes

Accept input in any form:

  • Free-text observation notes ("Their booth was huge, new product launch, aggressive pricing signage")
  • Brochure or collateral text (pasted or transcribed)
  • Product announcement snippets (press release, in-show announcement, banner copy)
  • Pricing clues (signage text, overhead conversations, quoted figures)
  • Overheard conversations or show-floor gossip (label these clearly as unverified)

From the input, extract:

  • Competitor name
  • Show name / date (ask if not provided — context matters for the report)
  • Source type for each data point: direct observation, printed material, overheard, or inferred

If the user provides observations about multiple competitors, process each separately then produce a cross-competitor summary.

Step 2: Separate Observation from Inference

This is the most important step. Every fact must be tagged:

Tag Meaning Example
[OBS] Directly observed or read verbatim "Banner copy read: 'Now 40% faster'"
[INF] Reasonably inferred from observable signals "Heavy foot traffic suggests strong interest from [segment]"
[HEARD] Overheard or reported second-hand — treat as unverified "Sales rep told a visitor their price starts at €X"
[EST] Estimated numerical value — not measured directly "Booth footprint est. 200 sqm"
[UNK] Cannot determine from available evidence

Read the full file on GitHub · 139 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 13d ago First seen · 139 lines · 102 tokens per session scan A db07256f81d8

Subscribe to this mod's changes

trade-show-competitor-radar is a skill published in the GitHub repository LensmorOfficial/trade-show-skills (48 stars, last pushed 1mo ago), licensed MIT. It adds 102 tokens to every session and 1,696 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.