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:

Critical guard: Do not convert inferences into facts in the output. "They claim 40% faster" is an [OBS] from banner copy. "They are 40% faster" is a fabrication. The difference matters when this note reaches your product or sales team.

Pricing information especially must carry source tags — never report a price as confirmed unless you saw a published price list or official quote.

Step 3: Summarize Positioning and Threat

Produce a structured intel note:

CODEBLOCK0

Step 4: Create Internal Battlecard Note

After the per-competitor notes, produce an Internal Action Note:

CODEBLOCK1

Tone guidance: Field-intel style, not marketing report style. "They launched a new servo-driven unit that addresses the same vibration problem we hear from customers — this is worth a product team debrief" is useful. "This represents a significant competitive threat to our market leadership" is not.

Output Footer

End every output with:

Quality Checks

Before delivering results:

• - Every price, speed claim, or product feature must carry a source tag ([OBS], [INF], [HEARD], [EST], or [UNK]) — no naked facts
• Threat level must be justified with specific observations, not impressions
• "High" threat requires at least two concrete, observed signals
• Numerical estimates (booth size, foot traffic count) must use [EST]; never present a guess as a measured fact
• Do not include personal opinions about design or aesthetics unless the user specifically asks
• If observations are sparse (e.g., only booth size and general messaging), the output should reflect that thinness rather than padding with inferences
• If the same competitor was observed across multiple sessions, aggregate rather than duplicate
• For multi-day shows, include at least one actionable counter-move the booth team can use the next day