← ClaudeAtlas

competitor-radarlisted

Structure competitor booth observations from a trade show into a field-intel note and battlecard-ready summary.
rubyt5673/trade-show-skills · ★ 1 · AI & Automation · score 73
Install: claude install-skill rubyt5673/trade-show-skills
# 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. ## 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