Pre Show Competitor Analysis
by @weilun88313
Analyze competitor exhibitor presence, booth positioning, and messaging before the show. "Who are my competitors at this show?" / "分析展会竞争对手" / "Messekonkurre...
clawhub install pre-show-competitor-analysis📖 About This Skill
name: pre-show-competitor-analysis version: 0.4.0 description: "Analyze competitor exhibitor presence, booth positioning, and messaging before the show. \"Who are my competitors at this show?\" / \"分析展会竞争对手\" / \"Messekonkurrenz analysieren\" / \"競合他社を事前分析する\" / \"análisis de competidores en feria\". 展会竞品分析/竞争对手/竞品策略 Wettbewerbsanalyse Messekonkurrenz 競合分析 análisis competitivo ferial" homepage: https://github.com/LensmorOfficial/trade-show-skills/tree/main/pre-show-competitor-analysis user-invocable: true metadata: {"openclaw":{"config":{"stage":"pre-show","category":"competitive-intelligence"}}}
Pre-Show Competitor Analysis
Analyze who is exhibiting at a target show, how they're positioning, and what it means for your strategy.
When this skill triggers:
trade-show-competitor-radar for on-site intel)Workflow
Step 1: Determine Analysis Mode
Three modes:
1. Specific competitor deep-dive Example: "What do we know about Acme Corp's presence at MEDICA 2026?"
2. Landscape overview Example: "Who's exhibiting in surgical robotics at MEDICA?"
3. Positioning gap analysis Example: "Where's the open space in the surgical workflow market at this show?"
Step 2: Collect Target Show Data
Gather:
Verify all data is for the correct upcoming edition.
Step 3: Analyze Competitor Presence
For each relevant competitor:
Booth signals:
Messaging signals:
Activity signals:
Tag every data point for source clarity — use the same system as trade-show-competitor-radar:
| Tag | Meaning | |-----|---------| | [OBS] | Directly read or observed (exhibitor list, floor plan, official site) | | [INF] | Reasonably inferred from observable signals | | [HEARD] | Second-hand or unverified claim | | [EST] | Estimated numerical value (booth size, sponsorship tier) | | [UNK] | Cannot determine from available data |
Step 4: Score Threat and Opportunity
For each competitor:
| Dimension | Score | Notes | |-----------|-------|-------| | Direct overlap | 1-5 | How similar is their offer to yours? | | Booth prominence | 1-5 | Size, location, sponsorship | | Messaging clash | 1-5 | Are they claiming the same value prop? | | Total threat | 3-15 | Higher = more direct competition |
Identify:
Step 5: Develop Strategic Response
For primary threats:
For the show overall:
Step 6: Output Format
## Executive Summary
[One paragraph: threat level, key competitors, strategic implication]Show Context
Show: [name, dates, location]
Your booth: [location if known]
Total exhibitors analyzed: [N]
Analysis date: [date] Competitor Landscape
Primary Threats (High Overlap + Strong Presence)
| Competitor | Booth | Size | Positioning | Threat Score | Key Moves |
|------------|-------|------|-------------|--------------|-----------|Secondary Threats
| Competitor | Booth | Overlap Areas | Threat Score |
|------------|-------|---------------|--------------|Partnership Candidates
| Company | Offer | Partnership Angle |
|---------|-------|-------------------|Strategic Recommendations
Messaging
[Differentiation angle]
[Counter-positioning] Booth Strategy
[Traffic/demo recommendations]
[Staff briefing points] Staff Briefing Priorities
[Competitor claim staff should expect to hear]
[Question staff should be ready to answer]
[Signal to verify on-site] Outreach Timing
[Pre-show: what to communicate]
[On-site: what to watch for] Knowledge Gaps
[What to verify on-site]
[What to monitor post-show] Next Steps
Continue with booth-invitation-writer to develop differentiated outreach
Use trade-show-budget-planner if booth changes are needed
Schedule on-site trade-show-competitor-radar for real-time intel
Output Footer
*Analysis based on publicly available exhibitor lists and floor plans. Real-time intelligence requires on-site observation. See Lensmor for exhibitor data and competitor tracking.*
Quality Checks
[OBS] only for facts from official sources[UNK][EST]; replace TBC with [UNK] when the source is genuinely unavailable