trend-spotter
Use when the user asks to "find trending topics", "what trends should my brand jump on", or "time a campaign around a cultural moment"; produces a ranked trend report with brand-fit scores, format calls (rising/peak/declining), a cultural calendar, and go/skip recommendations. Not for finding the creators to run those trends — use influencer-discovery; not for building the brand posting calendar from a go verdict — use social-calendar-builder. 热点趋势洞察/借势营销
aaron-he-zhu · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add aaron-he-zhu/aaron-marketing-skills --skill trend-spotter技能说明
name: trend-spotter slug: trend-spotter displayName: "Trend Spotter · 趋势侦察" summary: "排名化趋势报告:品牌契合评分、rising/peak/declining 判断与 go/skip 建议" description: 'Use when the user asks to "find trending topics", "what trends should my brand jump on", or "time a campaign around a cultural moment"; produces a ranked trend report with brand-fit scores, format calls (rising/peak/declining), a cultural calendar, and go/skip recommendations. Not for finding the creators to run those trends — use influencer-discovery; not for building the brand posting calendar from a go verdict — use social-calendar-builder. 热点趋势洞察/借势营销' version: "20.2.0" license: Apache-2.0 compatibility: "Claude Code and compatible agent-skill hosts" homepage: "https://github.com/aaron-he-zhu/aaron-marketing-skills" when_to_use: "Use when planning campaign timing and themes, deciding whether to join a hashtag, sound, or challenge, scouting trending content formats on a platform, mapping upcoming cultural moments to lead times, or checking which trends competitors have adopted or missed. Auto-activate when the request is about what is trending, what to post around, or when to act." argument-hint: " [platform] [time horizon]" metadata: {"author": "aaron-he-zhu", "version": "20.2.0", "discipline": "influencer", "phase": "scout", "geo-relevance": "low", "hermes": {"tags": ["marketing", "influencer", "scout"], "category": "influencer"}, "openclaw": {"emoji": "📣", "homepage": "https://github.com/aaron-he-zhu/aaron-marketing-skills"}}
Trend Spotter
This skill helps you identify and capitalize on trends that matter to your audience. It monitors social conversations, emerging topics, viral content formats, and cultural moments to inform influencer campaign timing and content strategy.
Quick Start
Shortest invocation:
What trends are relevant for [brand/industry] right now?
Common scenario — analyze one specific trend before committing:
Should [brand] participate in [trend/challenge]? Score the brand fit and give a go/skip call.
Skill Contract
- Reads: brand/industry, target platforms, audience, geographic focus, time horizon, content categories; prior audience and niche findings from
memory/influencer/if present. - Writes: return the trend report inline by default; save it to
memory/influencer/trend-spotter/YYYY-MM-DD-<topic>.mdonly with exact authorization for that WARM path. - Promotes: only with separate exact authorization, promote durable facts (top trends to act on now, trends to avoid, next review date) to
memory/hot-cache.md. - Done when:
- Every named current trend, volume/growth/status claim, cultural moment, and competitor-adoption claim has a dated source ref plus the requested platform, geography, observation window, metric definition, and momentum comparison.
- Each candidate with complete current evidence for that exact scope has a brand-fit score and a go / caution / skip call; RSS/title overlap alone remains a
Proxy candidatewithscore_state: NOT_SCORED. - The report names the top 3 trends, watch list, and avoid list only when current evidence supports them; otherwise it returns
NEEDS_INPUTwith an exact query/collection plan.
- Primary next skill: influencer-discovery — find the creators who can execute the chosen trends.
Handoff Summary
Emit the standard shape from skill-contract.md §Handoff Summary Format.
Data Sources
The intake and query plan work with no live integration. A report about what is current does not: it requires dated user-supplied evidence, a public fetch, or a live connector result for the requested platform, geography, and horizon. Brand inputs alone support search terms and evaluation criteria, not trend names, counts, growth, rising/peak/declining calls, or go/skip recommendations. Without current evidence, return NEEDS_INPUT and the exact queries/fields to collect. Where a tool supplies the read, use a ~~ connector placeholder:
~~social platform analytics— trending hashtags, sounds, and view counts per platform.~~trend database— emerging topics, challenge participation, and growth rates.~~social listening— cultural conversations and sentiment around a topic.~~competitor tracking— which trends rival brands have adopted and how they performed.
No connector is required to produce a useful query plan. A named current-trend report requires the source records above. See CONNECTORS.md for the free/keyless recipe per category.
For a keyless way to discover topics worth measuring, run the multi-source candidate scout — Google Trends RSS + Hacker News + Reddit + YouTube upload titles via the bundled stdlib rss_monitor.py (no new dependency): references/trend-scout-recipe.md. RSS/title overlap is only a Proxy candidate and stays NOT_SCORED; it does not establish a platform trend, view-count outlier, lifecycle state, or act-now recommendation. This is the Tier-1 candidate recipe behind ~~trend database (Google Trends RSS).
Keyless news pulse (Tavily): python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/tavily.py" search "<vertical or candidate trend>" --topic news --time-range w --limit 10 adds recency-filtered discovery refs. Agreement with an RSS title may raise query priority, but it remains a Proxy candidate/NOT_SCORED; news overlap does not prove momentum on TikTok, Reels, YouTube, or another requested platform.
Keyless source-specific sharpeners: python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/pageviews.py" "<Topic_Article>" --granularity daily --days 30 measures Wikipedia page attention, and the Hacker News Algolia API (https://hn.algolia.com/api/v1/search?query=<topic>, keyless) measures HN points/comments. Those values are Measured only for their named source and window. Treat them as Proxy for