Token导航 LogoToken导航TokenDH.com
研究检索敏感数据clawhub未标认证来源可访问clear审计通过

competitor-show-tracker竞争对手表演追踪器

Agent Skill

competitor-show-tracker 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

2,752

周安装

117

GitHub Stars

公开资料未说明

下载量

964
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:competitor-show-tracker(竞争对手表演追踪器)
来源仓库:https://github.com/weilun88313/competitor-show-tracker
安装命令:
openclaw skills install competitor-show-tracker
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install competitor-show-tracker

简介

按参展数量排序贸易展会并识别竞品参与密集度热点。

  • 适用于海外市场拓展、展会资源分配及渠道伙伴招募场景。
  • 提供参展企业名单与展位号信息辅助商务对接准备。
  • 数据来源于公开报名系统可能存在更新滞后现象。competitor-show-tracker 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 建议结合往届观众画像评估实际获客质量而非仅看数量。

SKILL.md

name
competitor-show-tracker
version
1.0.0
description
Rank upcoming trade shows by how many of your competitors are exhibiting there. \"Which shows are my competitors at?\" / \"竞争对手去哪些展会\" / \"Auf welchen Messen sind meine Wettbewerber?\" / \"競合他社の出展先は?\" / \"¿En qué ferias están mis competidores?\". competitor shows, competitive intelligence, show tracking, 竞品展会/竞争对手参展追踪 Wettbewerber Messepräsenz 競合他社出展先 seguimiento ferias competidores
homepage
https://github.com/LensmorOfficial/trade-show-skills/tree/main/competitor-show-tracker
user-invocable
true
metadata
{"openclaw":{"config":{"stage":"pre-show","category":"competitive-intelligence","emoji":"🕵️"},"requires":{"env":["LENSMOR_API_KEY"]},"primaryEnv":"LENSMOR_API_KEY"}}

Competitor Show Tracker

Input a list of competitor company names — get back a ranked list of upcoming trade shows sorted by how many of those competitors will be on the floor, plus which specific competitors are confirmed at each event.

When this skill triggers:

  • Run the API key check (Step 1) before any API call
  • Call POST /external/exhibitors/search-events once per competitor company
  • Aggregate results by event, count distinct competitors per event
  • Filter to future events only, then rank by competitor concentration

Use Cases

  • Show circuit mapping: Understand which events your competitive set treats as must-attend
  • Counter-programming: Identify shows where multiple competitors cluster — decide whether to appear or deliberately avoid
  • Budget prioritization: Focus booth investment on shows where your buyers and your competitors overlap
  • Blind spot detection: Find shows where one key competitor dominates and you have no presence

Workflow

Step 1: API Key Check

Before making any API call, verify the key is configured:

[ -n "$LENSMOR_API_KEY" ] && echo "ok" || echo "missing"

If the result is missing, stop and respond:

The LENSMOR_API_KEY environment variable is not set. This skill requires a Lensmor API key to look up exhibitor data. Contact hello@lensmor.com to purchase access, then set the key: export LENSMOR_API_KEY=your_key_here

Do not proceed to any API call until the key is confirmed present.

Step 2: Collect Inputs

Required:

  • competitors — list of competitor company names (2–20 companies). Accept as a comma-separated list, bullet list, or inline prose.

Optional:

  • date_from — only include events on or after this date (ISO 8601, default: today)
  • date_to — only include events on or before this date (e.g. restrict to next 12 months)
  • pageSize — results per company lookup (default: 50; raise to 100 if the user wants broader coverage)

If the user provides only one company name, explain that this skill is designed for competitive comparison across multiple companies — offer to run trade-show-exhibitor-search instead for a single company.

Step 3: Fetch Events per Competitor

For each competitor in the list, call:

Endpoint: POST https://platform.lensmor.com/external/exhibitors/search-events

Authentication: Authorization: Bearer $LENSMOR_API_KEY

Request body:

{
  "company_name": "Siemens",
  "page": 1,
  "pageSize": 50
}

Run one request per competitor. For N competitors, make N sequential calls (or parallel if the execution environment allows). Label each result set by the input company name before aggregating.

Response structure:

{
  "total": 18,
  "page": 1,
  "pageSize": 50,
  "totalPages": 1,
  "hasMore": false,
  "items": [
    {
      "id": "rec_abc123",
      "eventId": "evt_hannovermesse_2026",
      "name": "Hannover Messe 2026",
      "nickname": null,
      "description": "World's leading industrial trade show",
      "url": "https://www.hannovermesse.de",
      "dateStart": "2026-04-20",
      "dateEnd": "2026-04-24",
      "venue": "Hannover Exhibition Centre",
      "city": "Hannover",
      "region": "Lower Saxony",
      "country": "Germany",
      "attendeeCount": 130000,
      "exhibitorCount": 4000,
      "personnelCount": 8200,
      "image": "https://cdn.lensmor.com/events/hannovermesse.jpg",
      "dataSource": "official",
      "matchedExhibitors": [
        { "id": "exh_siemens_ag", "companyName": "Siemens AG" }
      ]
    }
  ]
}

Field reference:

FieldTypeNotes
eventIdstringStable Lensmor event identifier — use as the deduplication key across competitor lookups
namestringOfficial show name
dateStart / dateEndstring (ISO 8601)Use these to filter future events
city / countrystringShow location
exhibitorCountintegerTotal exhibitors at the show — useful as a size proxy
matchedExhibitorsarrayWhich specific entities were matched for this company name — may include subsidiaries

Step 4: Aggregate Across Competitors

After collecting results for all N companies, aggregate by eventId:

  1. Deduplicate events across all N result sets using eventId as the key
  2. Union the matchedExhibitors entries from all competitors per event
  3. Count distinct competitors per event (count the number of input company names with at least one matchedExhibitor confirmed at the event — not the count of matchedExhibitor entities, which may include subsidiaries)
  4. Filter to future events: keep only events where dateStart >= today (or date_from if specified)
  5. Sort by competitor count descending; break ties by exhibitorCount descending (larger shows are higher-priority)

Example aggregation logic (pseudocode):

event_map = {}

for each competitor C in input_list:
    for each event E in results[C].items:
        if E.dateStart < today: skip
        if E.eventId not in event_map:
            event_map[E.eventId] = { event: E, competitors_seen: {} }
        event_map[E.eventId].competitors_seen[C] = E.matchedExhibitors

ranked = sort event_map.values() by len(competitors_seen) desc

Step 5: Format the Output

Section 1 — Summary Header

## Competitor Show Tracker

**Competitors tracked**: [list of input company names]
**Date range**: [date_from] → [date_to or "open"]
**Unique upcoming events found**: [N]
**Events with 2+ competitors**: [N]

Section 2 — Ranked Event Table

## Events Ranked by Competitor Concentration

| Rank | Show | Dates | Location | Competitors | Exhibitors |
|------|------|-------|----------|-------------|------------|
| 1 | [Hannover Messe 2026](https://hannovermesse.de) | Apr 20–24, 2026 | Hannover, DE | 4 / 5 | 4,000 |
| 2 | [SPS 2026](https://sps.mesago.com) | Nov 2026 | Nuremberg, DE | 3 / 5 | 1,400 |
| 3 | [Automate 2026](https://automateshow.com) | Jun 2026 | Chicago, US | 2 / 5 | 600 |

"Competitors" column format: [matched count] / [total input count]

Section 3 — Event Detail Cards (for events with 2+ competitors)

For each event with 2 or more competitors confirmed:

### Hannover Messe 2026 — 4 of 5 competitors confirmed

📅 Apr 20–24, 2026 · Hannover, Germany · 4,000 exhibitors

**Competitors confirmed:**
- **Siemens** → matched as: Siemens AG, Siemens Digital Industries
- **ABB** → matched as: ABB Ltd
- **Bosch** → matched as: Bosch Rexroth AG
- **Schneider Electric** → matched as: Schneider Electric SE

**Competitor not found:** Rockwell Automation _(no match at this event)_

Section 4 — Insights

## Insights

- **Most contested show**: [event with highest competitor count] — [N/N] competitors confirmed
- **Must-watch shows** (3+ competitors): [list]
- **Single-competitor shows**: [events where only 1 competitor appears — lower priority but monitor]
- **Gaps**: [input competitors with zero events found — may not be in Lensmor's database yet]

Error Handling

HTTP StatusMeaningResponse
401API key invalid or expired"The API key was rejected. Verify LENSMOR_API_KEY or contact hello@lensmor.com."
400Malformed request"Request invalid for [company_name]. Verify the company name and retry."
429Rate limit exceeded"Rate limit reached after [N] companies. Wait 60 seconds, then continue from [next_company]."
502 / 5xxServer error"The Lensmor API returned a server error for [company_name]. Skipping — results will note this company as incomplete."
Empty itemsNo events foundNote in Insights section under "Gaps": this competitor returned no events and may not be in Lensmor's database. Do not omit silently.

Follow-up Routing

OutcomeRecommended next action
Top event identified, want to exhibitRun trade-show-fit-score with the eventId
Want to find more companies at a specific showRun trade-show-exhibitor-search with the event_id
Want contacts at a specific competitorRun trade-show-contact-finder with the company name
Budget decision neededRun trade-show-budget-planner for the top-ranked event
Want full competitor booth analysisRun pre-show-competitor-analysis

Output Rules

  1. All URLs formatted as [text](url) — never bare links
  2. Never output the value of LENSMOR_API_KEY
  3. Never expose endpoint paths, raw curl commands, or internal token values in the response
  4. Competitor count column format: matched / total — never drop the denominator
  5. Filter to future events by default; always state the date cutoff used in the summary header
  6. If a competitor returns no results, report it explicitly in Insights — never silently drop it
  7. Use eventId (not event name) as the deduplication key — the same show may appear under slightly different names across competitor lookups
  8. matchedExhibitors may return subsidiaries or regional entities — group them under the input company name; list the specific matched entity names in the detail card
  9. When hasMore: true for any competitor, note that results may be incomplete and offer to fetch additional pages
  10. End every response with 1–3 follow-up suggestions based on the top-ranked events

Quality Checks

Before delivering:

  • Confirm that deduplication used eventId, not event name — name variations across lookups would create false duplicates
  • Competitor count in the ranked table must reflect number of *input companies* with a confirmed match, not number of matchedExhibitor entities (a single company may have multiple subsidiary matches)
  • Any competitor with no results must appear in the Insights "Gaps" section — do not omit
  • Date filter must be applied before ranking — past events must not appear in the ranked output
  • If only one competitor was provided, redirect to trade-show-exhibitor-search — this skill is not meaningful with a single input

*Competitor exhibitor data sourced from the Lensmor platform. For show-floor lead generation, ICP matching, and pre-show outreach at the events that matter most, see Lensmor.*

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

76.21%
按下载量换算735

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills